Alfresco discussion and collaboration. Stick around a few hours after asking a question.
Official support for Enterprise subscribers: support.alfresco.com.
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.
More help is available in this list of resources.
2019-05-27 08:16:46 GMT <hi-ko> Is there a special reason why release tag for ALFRESCO_TAG=6.0.7-ga is no longer available in github?
2019-05-27 08:24:24 GMT <AFaust> What do you mean? https://github.com/Alfresco/acs-community-packaging/tree/acs-community-packaging-6.0.7-ga is there...
2019-05-27 08:24:25 GMT <alfbot> Title:GitHub - Alfresco/acs-community-packaging at acs-community-packaging-6.0.7-ga (at github.com)
2019-05-27 08:24:49 GMT <AFaust> It's just that they don't tag all the granular libs with the release version anymore...
2019-05-27 08:24:58 GMT <alfresco-discord> <yreg> hiko was it there before then taken away or did they simply reworded tag names ?
2019-05-27 08:26:55 GMT <hi-ko> sorry I meant https://github.com/Alfresco/acs-community-deployment/releases/tag/6.0.7-ga as mentioned on the release notes
2019-05-27 08:28:06 GMT <hi-ko> so it' just a doc bug ...?
2019-05-27 08:28:45 GMT <alfresco-discord> <yreg> those tags look like a real mess 😄
2019-05-27 08:30:35 GMT <hi-ko> ... lost in git reorg chaos ... :-(
2019-05-27 08:31:08 GMT <AFaust> I believe there never was a 6.0.7 GA tag in the deployment project. They started to count from 1.0.0 for their helm chart versions...
2019-05-27 08:31:53 GMT <AFaust> At least I cannot remember ever seeing such a tag when I was trying out the Kubernetes crap for the first time...
2019-05-27 08:32:31 GMT <Tichodroma> Up to Alfresco 5.2 unit tests could be annotated like this: https://bpaste.net/show/e382ffef8e10
2019-05-27 08:32:32 GMT <alfbot> Title:show at bpaste (at bpaste.net)
2019-05-27 08:33:02 GMT <Tichodroma> In 6.1 these types seem to be missing. What is the recommended way to implement unit tests that rely on a running repository?
2019-05-27 08:43:37 GMT <hi-ko> AFaust, angelborroy: I've seen you discussed already future/replacement of TransformService and RenditionService. What is the official recommendation to create previews/thumbnails in CE? I miss this in the 201901 GA release notes ...
2019-05-27 08:44:06 GMT <angelborroy> Currently it works as it worked before
2019-05-27 08:44:18 GMT <hi-ko> sure but how long ...?
2019-05-27 08:44:24 GMT <angelborroy> In 6.2 the new event oriented Transform Service will be shipped with Communit
2019-05-27 08:46:06 GMT <AFaust> To be fair, a small fraction of it already ships with 6.1 - that's the (stupid) reason that Active MQ is required. They use the event queue to handle the "refresh rendition on cm:content update" use case.
2019-05-27 08:46:13 GMT <hi-ko> and could be triggered by the same service mechanisms (maybe having other impls) or is this also history?
2019-05-27 08:47:26 GMT <hi-ko> AFaust: but if I disable the messaging subsystem the refresh also works as we are used before, right?
2019-05-27 08:47:43 GMT <AFaust> "Mostly".
2019-05-27 08:48:02 GMT <AFaust> You will not get updated thumbnails / previews when you upload a new version of a content.
2019-05-27 08:49:00 GMT <hi-ko> If I remember right, the previews/thumbnails still get updated on document save ...
2019-05-27 08:49:13 GMT <AFaust> Though to be fair, I have only looked at this from a code level and not actually reproduced the behaviour.
2019-05-27 08:49:30 GMT <AFaust> Maybe Share web scripts (still) have a special case in them for handling that, and it only affects other APIs..
2019-05-27 08:49:34 GMT <hi-ko> ... mayby hard coded in the aos or any other layer ...
2019-05-27 08:52:01 GMT <AFaust> I guess there is still the lazy client-side refresh handling based on the rendition timestamp vs. last modified date, so the only thing affected may be the pre-emptive rendition refresh.
2019-05-27 08:53:26 GMT <hi-ko> I think Alfresco is on the wood way how they use messages. message receiver shouldn't replay all messages to find out if a transaction has been rolled back. this has to be encapsulated on the sender side.
2019-05-27 08:54:16 GMT <hi-ko> at least the messages I see in 6.1. are not the way someone would implement messenging ...
2019-05-27 08:54:48 GMT <AFaust> Hehe... I don't know if all the non-Germans get the incorrect translation of "on the wood way"...
2019-05-27 08:56:11 GMT <hi-ko> never trust google translate ;-) s/on the wood way/on the wrong track/
2019-05-27 08:56:47 GMT <AFaust> Google translate is under all pig
2019-05-27 08:59:32 GMT <hi-ko> In our SmartTransformer we implemented a db based message queue to avoid yet another infra component for the external receivers and the way alfresco handles messages pushs to much internal logic to the receivers
2019-05-27 09:01:13 GMT <hi-ko> so we don't like to hook in there. Additionally it doesn't look like that Alfresco will open up the messaging for others since there is NO doc
2019-05-27 09:03:22 GMT <hi-ko> Which brings me back to my previous question: what is the official recommendation for TransformService and RenditionService since it is deprecated from the client perspective?
2019-05-27 09:03:56 GMT <angelborroy> This is how ACS 6.2 will work in Community
2019-05-27 09:03:57 GMT <angelborroy> https://github.com/Alfresco/SearchServices/blob/master/search-services/alfresco-search/doc/architecture/event-trackers/event-based-content-tracker-spike.md#how-the-new-transform-service-works
2019-05-27 09:03:58 GMT <alfbot> Title:SearchServices/event-based-content-tracker-spike.md at master · Alfresco/SearchServices · GitHub (at github.com)
2019-05-27 09:05:48 GMT <angelborroy> And this are current Transform Engines
2019-05-27 09:05:48 GMT <angelborroy> https://github.com/Alfresco/alfresco-transform-core
2019-05-27 09:05:49 GMT <alfbot> Title:GitHub - Alfresco/alfresco-transform-core (at github.com)
2019-05-27 09:05:58 GMT <angelborroy> As I said, this will be part of ACS Community 6.2
2019-05-27 09:06:03 GMT <angelborroy> (If nothing changes)
2019-05-27 09:13:57 GMT <hi-ko> angelborroy: thanks - I will reread this page which describes the implementation but not the consumer side and the client api, right?
2019-05-27 09:18:32 GMT <hi-ko> angelborroy: does this mean java api will be deprecated and we have to use the REST api to transfomr a document or to (re)generate a rendition?
2019-05-27 09:20:14 GMT <angelborroy> I think so
2019-05-27 09:20:25 GMT <angelborroy> But I’m not aware of the details
2019-05-27 09:21:00 GMT <hi-ko> On the other hand the Transform Engine looks somehow like a overkill. I don't see which problem you're going to address with this complexity
2019-05-27 09:21:26 GMT <angelborroy> Load Balancing
2019-05-27 09:21:44 GMT <hi-ko> this could be addressed by messaging ;-)
2019-05-27 09:21:50 GMT <angelborroy> You can deploy specialised services to deal with transformations
2019-05-27 09:22:04 GMT <angelborroy> It’s based in messaging, with queues for every different transformer
2019-05-27 09:22:09 GMT <hi-ko> that's what we are doing already ;-)
2019-05-27 09:22:21 GMT <angelborroy> So you’ll love it :D
2019-05-27 09:23:27 GMT <hi-ko> We would like but we need another abspraction for messages.
2019-05-27 09:23:47 GMT <angelborroy> They are including Camel
2019-05-27 09:23:59 GMT <angelborroy> So you can route the messages to your own service
2019-05-27 09:24:01 GMT <hi-ko> camel is just the technology
2019-05-27 09:24:22 GMT <angelborroy> Is a routing technology, right
2019-05-27 09:24:36 GMT <angelborroy> What allows to re-route the messages to different services
2019-05-27 09:24:41 GMT <hi-ko> I mean when to send which kind of message and which is the abstraction of the message content
2019-05-27 09:25:39 GMT <angelborroy> It’s still private, but there is an alfresco-transform-model
2019-05-27 09:26:07 GMT <angelborroy> Including JSON Oriented beans for Message Content
2019-05-27 09:26:34 GMT <angelborroy> Currently it includes a TransformRequest and a TransformReply
2019-05-27 09:27:34 GMT <hi-ko> so if you (alfresco) is encourages to consume these messages we need to get reliable details
2019-05-27 09:27:47 GMT <angelborroy> of course
2019-05-27 09:27:57 GMT <angelborroy> They will be shipped also with ACS 6.2 Community
2019-05-27 09:28:08 GMT <angelborroy> In fact, this is “secret” by now
2019-05-27 09:28:14 GMT <hi-ko> s/is encourages/is encouraging/
2019-05-27 09:28:29 GMT <angelborroy> Probably they’ll share the thing this week or next week
2019-05-27 09:28:48 GMT <angelborroy> I’ve been discussing internally to get this released
2019-05-27 09:28:53 GMT <hi-ko> looking forward to it. Thanks
2019-05-27 09:29:10 GMT <angelborroy> Probably I’ll try to build a sample OCR Transformer during next Global Virtual Hack-a-thon
2019-05-27 09:29:25 GMT <angelborroy> Just to have a sample on how to provide custom Transform Engines
2019-05-27 09:29:49 GMT <angelborroy> ACS 6.2 is planned for Sept/Oct
2019-05-27 09:30:22 GMT <angelborroy> btw
2019-05-27 09:30:40 GMT <angelborroy> I’m builiding Docker Compose templates internally to test different environments
2019-05-27 09:30:45 GMT <angelborroy> HTTP, SSL, Sharding…
2019-05-27 09:31:00 GMT <angelborroy> Any tool / mechanism to build dynamically this templates?
2019-05-27 09:31:21 GMT <angelborroy> I would like to have an input like: Community + SSL
2019-05-27 09:31:27 GMT <angelborroy> And to get the right Docker Compose
2019-05-27 09:32:11 GMT <hi-ko> One should write a docker decomposer to get back a one in all install for production ;-)
2019-05-27 09:33:14 GMT <AFaust> angelborroy: The only thing I feel is being left behind in all this transformer changes is the ability to have a (local) transformer which caches transformed content in a separate d:content property on the main node without the overhead of an extra rendition node. E.g. I have used such an approach to store OCRed content for faster re-indexing (e.g. my OCR transformer would only transform process the main content if I did not
2019-05-27 09:33:14 GMT <AFaust> already have content in my "cache" property)
2019-05-27 09:34:04 GMT <angelborroy> I’ve always wondered why Alfresco Repo does not store text extraction and so on
2019-05-27 09:34:18 GMT <angelborroy> This will save a lot of processing
2019-05-27 09:34:30 GMT <angelborroy> And the user can decide if I wants to use extra storage for that
2019-05-27 09:34:53 GMT <hi-ko> AFaust: but could be cached by the transformer service
2019-05-27 09:35:08 GMT <AFaust> I mean nowadays SOLR sort-of stores the text extractions in its cache. But if that is gone / corrupted, you are out of luck.
2019-05-27 09:35:19 GMT <angelborroy> Agree
2019-05-27 09:35:36 GMT <angelborroy> Probably you can extend default behaviour by adding your conditions
2019-05-27 09:35:49 GMT <AFaust> hi-ko: You mean your transformer service, right? Because AFAIK no component in Alfresco transformer service is doing that right now
2019-05-27 09:35:56 GMT <angelborroy> As transformation is based on a behaviour also for event oriented transformations
2019-05-27 09:37:02 GMT <angelborroy> I’ll try to point out that when I be allowed to start the event oriented tracker for SOLR
2019-05-27 09:37:08 GMT <hi-ko> AFaust: we already have that in our service but what I meant was that Alfresco could care about caching text extractions
2019-05-27 09:39:29 GMT <angelborroy> This seems interesting
2019-05-27 09:39:30 GMT <angelborroy> https://github.com/microsoft/generator-docker
2019-05-27 09:39:31 GMT <alfbot> Title:GitHub - microsoft/generator-docker: Yeoman generator for Docker (at github.com)
2019-05-27 09:39:45 GMT <angelborroy> Building Dockerfiles with yeoman
2019-05-27 09:40:00 GMT <Tichodroma> The pom.xml of acs-community-packaging-6.0.7-ga references alfresco-repository 6.55. https://github.com/Alfresco/acs-community-packaging/blob/2ba893ddf6fdba9fbc6da58e21788f6e89dcd9f7/pom.xml#L67
2019-05-27 09:40:01 GMT <alfbot> Title:acs-community-packaging/pom.xml at 2ba893ddf6fdba9fbc6da58e21788f6e89dcd9f7 · Alfresco/acs-community-packaging · GitHub (at github.com)
2019-05-27 09:40:18 GMT <Tichodroma> This tag does not exist in https://github.com/ecm4u/alfresco-repository
2019-05-27 09:40:19 GMT <alfbot> Title:GitHub - ecm4u/alfresco-repository: Metadata and content storage for Alfresco Content Services (Community and Enterprise) (at github.com)
2019-05-27 09:40:26 GMT <Tichodroma> Any hints where to look for it?
2019-05-27 09:40:27 GMT <AFaust> Sure, but from my perspective - as a "proper" microservice - the whole transformer service thingy should be stateless apart from "in-progress" transformations. I don't want to duplicate my entire storage tier to have long-term persistent transformation caches, as I only need that caching for very specific nodes (image only, where I cannot replace the main content with e.g. an OCRed PDF with hidden text layer)
2019-05-27 09:42:23 GMT <AFaust> Tichodroma: I guess GitHub has some limitations when it comes to number of tags + branches. I can see that tag only if I access it by direct URL: https://github.com/Alfresco/alfresco-repository/releases/tag/alfresco-repository-6.55
2019-05-27 09:42:24 GMT <alfbot> Title:Release alfresco-repository-6.55 · Alfresco/alfresco-repository · GitHub (at github.com)
2019-05-27 09:42:26 GMT <angelborroy> https://github.com/Alfresco/alfresco-repository/releases/tag/alfresco-repository-6.55
2019-05-27 09:42:42 GMT <angelborroy> AFaust is faster than me! :)
2019-05-27 09:42:48 GMT <AFaust> ...and more elaborate...
2019-05-27 09:43:14 GMT <hi-ko> AFaust: I don't agree and this is maybe the painpoint I have with the current state of Alfresco messaging. We reduced reindexing time from ~30 hrs to 5 hrs without any OCR involved
2019-05-27 09:43:16 GMT <angelborroy> And more handsome
2019-05-27 09:43:37 GMT <AFaust> Now you have lost me...
2019-05-27 09:43:51 GMT <angelborroy> Who lost you? hi-ko or me?
2019-05-27 09:44:00 GMT <angelborroy> I was just joking, you know me
2019-05-27 09:44:07 GMT <AFaust> You... I can never compete with your more southern complexion...
2019-05-27 09:44:32 GMT <Tichodroma> AFaust: +1
2019-05-27 09:58:57 GMT <hi-ko> AFaust: if the server checks if there is already a cached text it should not create a transform message. we could reduce the amount of transformations and transformer messages if we have a service in between taking care about transaction, cache, reusing other transformations, ...
2019-05-27 12:59:18 GMT <alfresco-discord> <Mark> Any known Maven tricks for using an amp as a code dependency? I'm trying to extend classes from the alfresco-rm amp source code.
2019-05-27 13:24:45 GMT <AFaust> There is no trick for that - you need to add the included JAR(s) as a dependency instead. Since those JAR(s) are typically not available as Maven artefacts themselves, you'll have to unpack and deploy them into your local Maven repository manually.
2019-05-27 13:25:21 GMT <alfresco-discord> <Mark> I figured, but it was worth a shot. Thanks!
2019-05-27 13:59:02 GMT <alfresco-discord> <binduwavell> @Mark I think you used to be able to add amps as deps with packaging set to amp and alfresco-maven plugin would do the right thing. @ohej did that get removed with the 3.x or 4.x refactor?
2019-05-27 14:08:31 GMT <alfresco-discord> <yreg> @Mark first you need to depend in your project on the jar, not the amp, and reference the right classifier (at least that was how it used to work) for being able to import and extend classes from an AMP
2019-05-27 14:10:52 GMT <alfresco-discord> <yreg> as for including the dependency amp in the project run by the SDK when you execute ./run.sh build_start you will need to adapt your Dockerfile(s) a bit, adding the amp inside the image and executing the Alfresco MMT tool to apply them, you might also want to use a maven-dependency-plugin to actually resolve amps and place them in a specific location ...
2019-05-27 14:13:27 GMT <alfresco-discord> <Mark> @yreg interesting! There is no packaging type jar for this module however. Or do I need to specify a classifier for that? Where do I look?
2019-05-27 14:13:58 GMT <alfresco-discord> <yreg> which module you want to depend on ?
2019-05-27 14:14:04 GMT <alfresco-discord> <yreg> RM CE ?
2019-05-27 14:15:41 GMT <alfresco-discord> <Mark> Yeah
2019-05-27 14:16:09 GMT <alfresco-discord> <Mark> wow, I figured it out thanks to your comment, visited the location in Nexus and used the various available suffixes as qualifiers. Very cool.
2019-05-27 14:16:25 GMT <alfresco-discord> <yreg> <dependency> <groupId>org.alfresco</groupId> <artifactId>alfresco-rm-community-repo</artifactId> <version>2.7.b</version> <classifier>classes</classifier> </dependency>
2019-05-27 14:16:26 GMT <alfresco-discord> <Mark> For reference: this page. https://artifacts.alfresco.com/nexus/service/local/repositories/releases/content/org/alfresco/alfresco-rm-community-repo/2.7.b/
2019-05-27 14:16:33 GMT <alfresco-discord> <Mark> Exactly, that works. Awesome!
2019-05-27 14:17:10 GMT <alfresco-discord> <Mark> I'm still on an SDK 3 project, so I'm all good for now. Thanks a lot!
2019-05-27 14:18:09 GMT <alfresco-discord> <yreg> just make sure to mark the dependency as provided, in order to avoid shipping it in you AMP as duplicate
2019-05-27 14:18:41 GMT <alfresco-discord> <Mark> Yeah I'm doing that. But thanks for the tip.
2019-05-27 14:21:45 GMT <hi-ko> Is there a compat matrix which version von platform is working with which version of Share, SearchServices?
2019-05-27 14:22:57 GMT <alfresco-discord> <yreg> hi-ko not sure I understand
2019-05-27 14:23:34 GMT <alfresco-discord> <yreg> but you can always check the share tag, and check on which repo it depends
2019-05-27 14:24:20 GMT <hi-ko> if someone installed ACS 6.0.7 which is the latest version of Share and SearchServices he could/should use?
2019-05-27 14:24:45 GMT <hi-ko> same for ACS 6.1.2 and so on ...
2019-05-27 14:25:49 GMT <alfresco-discord> <yreg> Share lists the repo version against which it was built (or share-services was, at least) : https://github.com/Alfresco/share/blob/alfresco-share-parent-22.214.171.124/pom.xml#L36
2019-05-27 14:25:50 GMT <alfbot> Title:share/pom.xml at alfresco-share-parent-126.96.36.199 · Alfresco/share · GitHub (at github.com)
2019-05-27 14:25:59 GMT <hi-ko> If I remember right this info used to be part of the release notes
2019-05-27 14:26:19 GMT <hi-ko> sure. but build contains things like RC2
2019-05-27 14:27:00 GMT <alfresco-discord> <yreg> but in my experience, share haven't evolved much since a year or two and I consider it to be safe to use the most recent share with any repo
2019-05-27 14:27:10 GMT <alfresco-discord> <yreg> given the right share services are installed
2019-05-27 14:27:28 GMT <alfresco-discord> <yreg> as for ASS, there is a matrix somewhere in the docs
2019-05-27 14:27:51 GMT <hi-ko> seen in both GA "releases" 6.0 and 6.1 so we switched to latest share and searchServices.
2019-05-27 14:34:06 GMT <hi-ko> yreg: you mean something like this: https://docs.alfresco.com/6.1/concepts/supported-platforms-ACS.html
2019-05-27 14:34:07 GMT <alfbot> Title:Supported Platforms | Alfresco Documentation (at docs.alfresco.com)
2019-05-27 14:34:49 GMT <hi-ko> It would be very helpful if Share and ASS provides requirements for minimal versions
2019-05-27 14:38:04 GMT <alfresco-discord> <yreg> nope, I remember seeing another matrix dedicated to ASS
2019-05-27 14:43:42 GMT <alfresco-discord> <Mark> There is another table dedicated to ASS on the ASS enterprise portal download page. It claims compatability for 188.8.131.52 with ACS 6.1.x, 6.0.x and 5.2.x
2019-05-27 15:02:58 GMT <alfresco-discord> <drazen04> Hi guys. Someone knows how send a custom email to creator every time a task in a workflow change my variable "state"?
2019-05-27 15:06:35 GMT <hi-ko> Mark: Thanks. ~later tell angelborroy: It would help us and maybe others to provide minimal repo version as part of ASS and Share
2019-05-27 15:12:33 GMT <alfresco-discord> <yreg> hi-ko you need to start your line with ~ or alfbot won't understand
2019-05-27 15:13:03 GMT <hi-ko> thanks yreg
2019-05-27 15:13:19 GMT <hi-ko> ~later tell angelborroy: It would help us and maybe others to provide minimal repo version as part of ASS and Share
2019-05-27 15:13:19 GMT <alfbot> hi-ko: The operation succeeded.
2019-05-27 15:13:34 GMT <hi-ko> here we are ;-)
The other logs are at http://esplins.org/hash_alfresco