karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KARAF-2290) should also endorse activation-api spec jar
Date Wed, 24 Apr 2013 03:43:15 GMT

     [ https://issues.apache.org/jira/browse/KARAF-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Freeman Fang resolved KARAF-2290.

       Resolution: Fixed
    Fix Version/s: 3.0.0

commit fix
http://svn.apache.org/r1471235 for trunk
http://svn.apache.org/r1471234 for 2.3.x branch
http://svn.apache.org/r1471237 for 2.x branch

As this need use SMX Specs 2.3.0 which isn't released yet, so upgrade to use  SMX Specs 2.3-SNAPSHOT
for now so that we won't forget upgrade the specs version before release
> should also endorse activation-api spec jar
> -------------------------------------------
>                 Key: KARAF-2290
>                 URL: https://issues.apache.org/jira/browse/KARAF-2290
>             Project: Karaf
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.3.2, 2.4.0, 3.0.0
> as javax/activation/DataHandler need be loaded from bootloader anyway(because we endorse
other specs jars which need use  javax/activation/DataHandler ), so we shouldn't load it as
a bundle, to avoid LinkageError like
> Caused by: java.lang.LinkageError: loader constraint violation: when resolving overridden
method "org.apache.cxf.jaxb.attachment.JAXBAttachmentMarshaller.addSwaRefAttachment(Ljavax/activation/DataHandlerLjava/lang/String;"
the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5)
of the current class, org/apache/cxf/jaxb/attachment/JAXBAttachmentMarshaller, and its superclass
loader (instance of <bootloader>), have different Class objects for the type javax/activation/DataHandler
used in the signature
> > at org.apache.cxf.jaxb.JAXBDataBase.getAttachmentMarshaller

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message