[
https://issues.apache.org/jira/browse/CXF-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965709#comment-14965709
]
Florent Guillaume commented on CXF-6493:
----------------------------------------
Please fix this packaging issue, these classes don't belong to CXF so shouldn't
be packaged with it.
> cxf-rt-transports-http-3.1.1.jar contains OSGi interface classes
> ----------------------------------------------------------------
>
> Key: CXF-6493
> URL: https://issues.apache.org/jira/browse/CXF-6493
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.1.1
> Reporter: Seth Leger
> Priority: Critical
>
> The cxf-rt-transports-http-3.1.1.jar contains several OSGi HTTP interface
> classes and the classes are exported in the OSGi Export-Package for the
> bundle.
> {noformat}
> ...
> org/osgi/
> org/osgi/service/
> org/osgi/service/http/
> org/osgi/service/http/HttpContext.class
> org/osgi/service/http/HttpService.class
> org/osgi/service/http/NamespaceException.class
> org/osgi/service/http/package.html
> org/osgi/service/http/packageinfo
> ...
> {noformat}
> {noformat}
> Export-Package: org.osgi.service.http;version="1.2.1",...
> {noformat}
> The bundle should not export classes from the OSGi HTTP spec in
> Export-Package; it is the responsibility of the OSGi HTTP service to export
> the specification classes.
> The inclusion of the classes also causes problems for us because we have a
> Java project with a large classpath (including CXF). We embed an OSGi
> container inside the outer JVM and we run into problems if CXF is in the
> outer classpath because the classes in cxf-rt-transports-http-3.1.1.jar cause
> classloading conflicts with the OSGi HTTP service inside the OSGi container.
> You should eliminate the interface classes from the JAR to prevent problems
> like this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
