Closed daronson1 closed 6 years ago
Hi - share functionality requires acs aem commons — do you have that installed? If so what version?
Hi David,
ACS Commons 3.11.0 is installed and active
Also are you version 1.0.2 of asset share commons? (This should’ve been resolved in that)
With acs commons 3.11.0 bundle Active, can you restart the asset share commons bundle? You shouldn’t have to do this but I’m curious if that resolved anything.
Same result (error) with 1.0.1, 1.0.2, and 1.0.3-snapshot (master branch) I also tried stopping and starting the bundle (to no avail...)
The issue appears to relate to the referenced email service - I have seen issues in the past resolved by manually creating the implied "bind" function... not sure if this will help, but that is an alternative...
@daronson1 does reinstalling Asset Share Commons after having ACS commons already installed fix it?
Uninstalling and re-installing the Asset Share Commons has no effect on the issue...
@daronson1 and asking the obvious; is the acs aem commons EmailServicr osgi component active or satisfied? And what is the state of the ASC emailshareserviceimpl osgi component in Felix?
@davidjgonzalez sounds like we are running into the same issue. @arpithaar do you have details? Following the comments here, doesn't seem like there's a fix yet or it was fixed in 1.0.2. We are using 1.0.3-SNAPSHOT, so we should have the fix.
I'm proposing simply copying the email service from ACS Commons into an Asset Share email service and then we can get rid of the ACS dependency completely. Its not great to have a duplication of a service, but the dependency on ACS is heavy for just a small service and would avoid these issues. Might be possible to make the Asset Share email service private so that people don't get confused between ACS and ASC ;) .
wdyt @davidjgonzalez, @kaushalmall ?
i moved the ACS EmailServiceImpl over last night but realized i had to make a service user, mapper config, and acls - so i took the for the dog for a walk instead.
TBH I dont like this approach, but im at the end of spending my evenings trying to figure out how to make these dependencies play nice.
Its just so confounding since i dont see what were doing that is so special compared to how every other project use the ACS Commons email service.
@davidjgonzalez @godanny86 @arpitaar not sure if any of this is related, but, there might be dependency issues with ACS Commons as well. @justinedelson recently helped me debug an issue which he then fixed in ACS Commons as well [0] . For us, we had to update the pom file like below.
<dependency>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-bundle</artifactId>
<exclusions>
<exclusion>
<groupId>org.apache.sling</groupId>
<artifactId>org.apache.sling.models.api</artifactId>
</exclusion>
</exclusions>
</dependency>
[0]https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1217
With the Mail server setup (and successfully sharing an asset in the AEM interface), the share functionality of the Asset Share interface doesn't work.
Steps to reproduce: