You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/03/26 21:28:27 UTC
[jira] Resolved: (WSCOMMONS-529) MANIFEST.MF for axiom-api JAR in
1.2.8 release is missing an Import-Package entry
[ https://issues.apache.org/jira/browse/WSCOMMONS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved WSCOMMONS-529.
---------------------------------------
Resolution: Won't Fix
In the current trunk, the OSGi support has been completely redesigned. See [1]. Can you test this with 1.2.9-SNAPSHOT?
[1] http://markmail.org/thread/nmpyxefndcnqoc2s
> MANIFEST.MF for axiom-api JAR in 1.2.8 release is missing an Import-Package entry
> ---------------------------------------------------------------------------------
>
> Key: WSCOMMONS-529
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-529
> Project: WS-Commons
> Issue Type: Bug
> Affects Versions: Axiom 1.2.8
> Reporter: Mike Edwards
> Attachments: axiom-api-1.2.8.MF
>
>
> The MANIFEST.MF file for the axiom-api-1.2.8.jar is missing an Import-Package entry for:
> org.apache.axiom.soap.impl.llom.soap11
> This causes an exception of the following kind when using the axiom-api-1.2.8.jar under OSGi:
> org.apache.axiom.om.OMException: java.lang.ClassNotFoundException: org.apache.axiom.soap.impl.llom.soap11.SOAP11Factory
> at org.apache.axiom.om.OMAbstractFactory.getSOAP11Factory(OMAbstractFactory.java:147)
> ...
> Adding an Import-Package entry as follows overcomes this problem:
> org.apache.axiom.soap.impl.llom.soap11;resolution:=optional,
> ...I note that this matches the Import-Package entry for the equivalent soap12 package, which is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.