Daily Log for #alfresco IRC Channel

Alfresco discussion and collaboration. Stick around a few hours after asking a question.

Official support for Enterprise subscribers: support.alfresco.com.

Joining the Channel:

Join in the conversation by getting an IRC client and connecting to #alfresco at Freenode. Our you can use the IRC web chat.

More information about the channel is in the wiki.

Getting Help

More help is available in this list of resources.

Daily Log for #alfresco

2019-08-30 07:00:12 GMT <alfresco-discord> <bhagyas> I saw pics from DevCon posted on @Francesco Corti 's linkedin, waiting until he gets to announce it here

2019-08-30 07:00:16 GMT <alfresco-discord> <bhagyas> ๐Ÿ˜‰

2019-08-30 07:12:40 GMT <alfresco-discord> <bhagyas> mistake

2019-08-30 07:12:41 GMT <alfresco-discord> <bhagyas> ๐Ÿ˜„

2019-08-30 07:44:14 GMT <alfresco-discord> <dgradecak> @angelborroy: when you say "Sharding has been improved", I honestly did not check what specifically Alfresco is doing with sharding but when you say this, does this mean there are "non solr standard" features?

2019-08-30 07:44:57 GMT <angelborroy> There are different Sharding methods with a Shard Web Console for Enterprise

2019-08-30 07:45:16 GMT <angelborroy> We were working on this, as there were different requests to improve this area

2019-08-30 07:45:35 GMT <angelborroy> On Search Services Community, there is no new feature from 1.3.x to 1.4.0

2019-08-30 07:46:15 GMT <alfresco-discord> <dgradecak> @AFaust I use MQs quite a lot but not yet Alfresco-AMQ, I am afraid of doing so honestly, because if Alfresco makes changes to it than it might not fit other use cases, so it is just fear on my side

2019-08-30 07:47:39 GMT <AFaust> The thing is, in this case I don't want to use AMQ at all, I just want to run Repository in a config where only an embedded message broker is used - no external AMQ at all.

2019-08-30 07:47:43 GMT <alfresco-discord> <dgradecak> thanks for the clarification @angel.borroy

2019-08-30 07:48:06 GMT <alfresco-discord> <dgradecak> embbeded within the repo you mean?

2019-08-30 07:48:17 GMT <AFaust> Customer is running on Windows, so we won't be using any Docker-based transformers anyhow, so no point in setting up AMQ when literally none of the features (async transformation, events gateway) will be used.

2019-08-30 07:48:21 GMT <AFaust> Yes..

2019-08-30 07:49:07 GMT <alfresco-discord> <dgradecak> well I did that but ages ago, while I was still embedding everything in the repo

2019-08-30 07:49:20 GMT <AFaust> bhagyas: The pics from DevCon were already announced on community.alfresco.com yesterday - if you mean the flickr album from Kristen...

2019-08-30 07:51:15 GMT <AFaust> Looks like the announcement is already gone again... I can only find it via the search, but it does not show up in the UI anymore.

2019-08-30 07:51:41 GMT <AFaust> Ah... it does - it is just hidden behind another, older announcement

2019-08-30 07:52:03 GMT <AFaust> So, https://www.flickr.com/photos/161110973@N04/albums/72157710589028541 has been announced properly...

2019-08-30 08:23:16 GMT <alfresco-discord> <dgradecak> @AFaust why are you considering embedding amq? actually what are you going to use it for exactly?

2019-08-30 08:24:07 GMT <AFaust> I am not considering embedding anything. I just am considering to use what is already there / embedded.

2019-08-30 08:24:40 GMT <AFaust> Already linked to it yesterday, but that is what I am referring to: https://github.com/Alfresco/alfresco-sdk/blob/master/archetypes/alfresco-allinone-archetype/src/main/resources/archetype-resources/__rootArtifactId__-platform-docker/src/main/docker/alfresco-global.properties#L82

2019-08-30 08:24:41 GMT <alfbot> Title:alfresco-sdk/alfresco-global.properties at master ยท Alfresco/alfresco-sdk ยท GitHub (at github.com)

2019-08-30 08:25:35 GMT <alfresco-discord> <dgradecak> well ok, but is there an embedded configuration for amq provided?

2019-08-30 08:26:34 GMT <alfresco-discord> <dgradecak> or that will launch it? did not check for jars etc ...

2019-08-30 08:27:20 GMT <alfresco-discord> <bhagyas> Yeah, apologies on that - removed my posts on that

2019-08-30 08:28:39 GMT <alfresco-discord> <dgradecak> I did not see your post from yesterday, so I am like a "parachutist"

2019-08-30 08:30:04 GMT <alfresco-discord> <dgradecak> now I see that I read it when asked about this. But still, are you planning to use that for tests or in production? just curious

2019-08-30 08:30:21 GMT <AFaust> If possible, production...

2019-08-30 08:30:58 GMT <AFaust> Again, for this customer, there would be absolutely no point in having a separate AMQ instance, as they will not be able to use any of the features that are based on AMQ

2019-08-30 08:31:38 GMT <alfresco-discord> <dgradecak> that is what was my question, what features are you planning to use ... so none, just not to disable it I guess

2019-08-30 08:32:47 GMT <alfresco-discord> <dgradecak> I did not yet check the size of alfresco messages, did anyone here use AMQ with alfresco in prod yet?

2019-08-30 08:32:51 GMT <AFaust> Well, there is one stupid mini feature that is independent of the async transformation feature which Alfresco moved towards the event-based behaviour model.

2019-08-30 08:33:02 GMT <alfresco-discord> <dgradecak> which one?

2019-08-30 08:33:12 GMT <AFaust> And without using the local, embedded broker, that mini feature would be broken

2019-08-30 08:33:34 GMT <AFaust> Regenerating / invalidating content renditions on content property update...

2019-08-30 08:33:35 GMT <alfresco-discord> <dgradecak> sounds great

2019-08-30 08:34:04 GMT <alfresco-discord> <dgradecak> really? hm ... will do my checks again next week than

2019-08-30 08:34:17 GMT <AFaust> Let me see if I can find that class again and link it

2019-08-30 08:34:24 GMT <alfresco-discord> <dgradecak> although they "swallow" exceptions? and not showing anything

2019-08-30 08:35:26 GMT <alfresco-discord> <dgradecak> I did not see any "error" while my tests without amq but with renditions, but I saw that there were no exception reports in some cases, just did not have time yet to go through all that correctly

2019-08-30 08:35:48 GMT <AFaust> It's not a matter of swallowing exceptions. There just won't be any logic triggered if the messaging / events subsystems are disabled (which I'd have to do without AMQ and without using the embedded broker)

2019-08-30 08:38:29 GMT <alfresco-discord> <dgradecak> woohoo

2019-08-30 08:38:44 GMT <alfresco-discord> <dgradecak> good to know indeed

2019-08-30 08:39:01 GMT <AFaust> https://github.com/Alfresco/alfresco-repository/blob/master/src/main/java/org/alfresco/repo/rendition2/RenditionEventProcessor.java

2019-08-30 08:39:02 GMT <alfbot> Title:alfresco-repository/RenditionEventProcessor.java at master ยท Alfresco/alfresco-repository ยท GitHub (at github.com)

2019-08-30 08:40:18 GMT <alfresco-discord> <dgradecak> ok that is in rendtion2 ... woof

2019-08-30 08:40:54 GMT <alfresco-discord> <dgradecak> so need to be a bit more careful when disabling it from now on

2019-08-30 08:42:17 GMT <alfresco-discord> <dgradecak> not sure at what point "legacy" transformers will use rendtion2 services only, but I guess you are talking about a regular share content update?

2019-08-30 08:42:27 GMT <alfresco-discord> <dgradecak> did you disable the legacy transformers also?

2019-08-30 08:46:21 GMT <AFaust> Well - you have to separate rendition2 service from legacy transformers a bit

2019-08-30 08:46:39 GMT <AFaust> There is no way (AFAIK) to disable the rendition2 service use - it is more or less hard-wired

2019-08-30 08:47:09 GMT <AFaust> But the legacy transformers can be / are tied into the rendition2 service framework.

2019-08-30 08:48:04 GMT <AFaust> So the only thing I don't want to use for this Enterprise customer (can't really, without Docker) is the use of the external / Docker-based T-Router / T-Engines...

2019-08-30 08:48:54 GMT <AFaust> But since this tiny tidbit of rendition2 framework requires the events / messaging subsystem, I have to make it work via the local / embedded broker.

2019-08-30 08:50:00 GMT <AFaust> And by the way, it is the other way around: "legacy" transformers don't use rendition2, rendition2 uses "legacy" transformers (if configured that way)

2019-08-30 08:50:07 GMT <alfresco-discord> <dgradecak> my questions was: if the behavior you have is through share right? as far as I saw if the legacy transfromers are used the new ones will not be

2019-08-30 08:50:14 GMT <AFaust> It's a bit like Soviet Russia that way...

2019-08-30 08:50:33 GMT <AFaust> The behaviour is in core Repository, so does not matter whether Share or not...

2019-08-30 08:50:45 GMT <alfresco-discord> <dgradecak> so that is why I asked if you "re-enable" legacy transformers, will the same behavior happen?

2019-08-30 08:51:17 GMT <AFaust> yes... because legacy transformers are the layer below rendition2, not above it.

2019-08-30 08:52:00 GMT <AFaust> Again... I already observed this behaviour in Community, which "only" has legacy transformers...

2019-08-30 08:52:21 GMT <alfresco-discord> <dgradecak> although they are planning to remove legacy, what I know is that the rendtion 2 is only used from the new rest apis

2019-08-30 08:52:53 GMT <alfresco-discord> <dgradecak> and the legacy "behaviors" are still the same "from share" without rendtion2 ... but that might be different in enterprise although

2019-08-30 08:53:11 GMT <alfresco-discord> <dgradecak> but I belive you studied it a bit more than I did

2019-08-30 08:56:48 GMT <AFaust> rendition2 is not only used from the new ReST APIs - it is also used by policies / behaviours which can be triggered by any interaction

2019-08-30 08:57:27 GMT <AFaust> It is also triggered from the ScriptNode API, which a lot of Share web scripts use

2019-08-30 08:59:39 GMT <AFaust> Of course I could really try to choose the extreme approach and also set renditionService2.enabled to false, but then again I might loose out on other improvements / bugfixes.

2019-08-30 09:00:07 GMT <AFaust> So that is why I want to go the route with the most minimalistic change - simply routing events via the local broker

2019-08-30 09:00:33 GMT <alfresco-discord> <dgradecak> sure, the way to go is rendition2 but this "half dev done" is sometimes frustrating

2019-08-30 09:02:11 GMT <AFaust> What frustrates me about this "we pipe the onContentUpdate handling through an event" is that it is extremely intransparent. The RenditionService2Impl implements the OnContentUpdatePolicy interface, so you expect it to be a properly bound behaviour.

2019-08-30 09:02:58 GMT <AFaust> But it is actually faked via the RenditionEventProcessor, which maps the broker message on to the API...

2019-08-30 09:03:08 GMT <alfresco-discord> <dgradecak> indeed, that is at most a "strange implementation"

2019-08-30 09:03:51 GMT <AFaust> It would have been cleaner if the event processor just processed the event itself and did not add to the public interface of the service a completely fabricated operation

2019-08-30 09:05:03 GMT <AFaust> And this fakery tricks almost all developers which rely on IDE call hierarchies / graphs to analyse + understand new code.

2019-08-30 09:05:36 GMT <AFaust> And the call hierarchy will blindly say "yes, sure, this operation is directly called by the ContentService via this policy interface"...

2019-08-30 09:07:02 GMT <AFaust> And worse yet... if you disable events / messages subsystem, there isn't event a warning in the logs anywhere that the event processor could not bind to anything, so you never know that you broke something...

2019-08-30 09:07:47 GMT <AFaust> ok .... enough venting for now, have to do some more code changes for that project before we continue setting up the new test environment this afternoon.

2019-08-30 09:09:28 GMT <alfresco-discord> <dgradecak> lunch time here ... ๐Ÿ˜‰ but indeed it is a bit a mess a this moment

2019-08-30 11:17:11 GMT <AFaust> Grml... why did I have to find one of the few pieces of code in Alfresco Share 6.1 that has never been adapted to properly handle CSRF (which was introduced in 4.2 or so)?

2019-08-30 11:48:28 GMT <alfresco-discord> <dgradecak> hopefully share is on its way out ๐Ÿ˜„

2019-08-30 11:51:13 GMT <AFaust> ....provided something that can replace it is available...

2019-08-30 11:54:27 GMT * AFaust is confused about that CSRF error, because CSRF should actually be disabled in my dev environment

2019-08-30 15:11:25 GMT <alfresco-discord> <angel.borroy> @digcat Finally I added HTTPs support to Alfresco Docker Installer

2019-08-30 15:11:40 GMT <alfresco-discord> <angel.borroy> https://github.com/Alfresco/alfresco-docker-installer

2019-08-30 15:11:41 GMT <alfbot> Title:GitHub - Alfresco/alfresco-docker-installer: Generator to build Docker Compose templates to deploy Alfresco Community (at github.com)

2019-08-30 15:12:17 GMT <alfresco-discord> <angel.borroy> Some people in the Community were also asking for a running sample, so I decided to provide the feature with a self-signed certificate

2019-08-30 15:29:58 GMT <alfresco-discord> <digcat> thats great work @angel.borroy will give it a whirl

End of Daily Log

The other logs are at http://esplins.org/hash_alfresco