Impacts of exposing the boot classpath in OSGI

[anushap40132887]

What can be the impacts of adding the following property in sling.properties to resolver class linkage error for the javax.activation errors?

(We have seen that adding this property is affecing sending HTMLemails)

org.osgi.framework.system.packages.extra=javax.activation;version\="1.1.1".

Is it advisable to use this fix in AEM 6.1 and above?

Thanks in advance.

[smacdonald2008]

I have never seen an issue like this before - how are you building you AEM project? Are you using Maven Archetype and AEM dependencies?

[anushap40132887]

Hi Scott, Thanks for your reply. Yes, we are using maven and AEM dependencies.

[smacdonald2008]

So you are writing an AEM OSGi bundle that you want to use to send emails. This should be straightforward without getting this error or modifying the sling props file. WHat API are you using to send email messages?

[anushap40132887 · Accepted solution]

We are using the “HtmlEmail -Apache Commons Email API” for sending emails and exception occurred in the method for setting mail content (email.setMsg(message); ). We were able to resolve the issue by changing the method as email.setContent(message, "text/html");

We have modified the sling.properties file in order to fix the linkage error that occurred while invoking webservice from AEM(https://forums.adobe.com/thread/2336233)

[smacdonald2008]

Thanks for posting the fix.