[KARAF-6093] Error putting an attachment on a SOAP message via CXF due to javax.xml.soap

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2.2
• Fix Version/s: 4.2.3
• Component/s: karaf
• Assignee: Jean-Baptiste Onofré
• Reporter: Brandan Jeter
• Created: 15/Jan/19 23:10
• Updated: 02/Jul/21 12:50
• Resolved: 16/Jan/19 05:16

Description

As of https://github.com/brjeter/karaf/commit/50ccdc93a1ff1e619f808e13f38fbacbb26213c0#diff-9142d4f795c7f69aa9e8b7bc87e18a59L345, javax.activation is expected to be exported by a servicemix bundle instead of bundle 0. This is causing a LinkageError because javax.xml.soap uses javax.activation but is still being exported by bundle 0.

loader constraint violation: when resolving method "javax.xml.soap.SOAPMessage.createAttachmentPart(Ljavax/activation/DataHandler;)Ljavax/xml/soap/AttachmentPart;" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, org/apache/cxf/binding/soap/saaj/SAAJInInterceptor, and the class loader (instance of <bootloader>) for the method's defining class, javax/xml/soap/SOAPMessage, have different Class objects for the type javax/activation/DataHandler used in the signature

 

Issue Links

• relates to: KARAF-6106 LinkageError due to javax.activation not in kernel anymore
• links to: GitHub Pull Request #719
• links to: GitHub Pull Request #728