Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 19A6318A8A for ; Wed, 21 Oct 2015 04:25:28 +0000 (UTC) Received: (qmail 27228 invoked by uid 500); 21 Oct 2015 04:25:28 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 27194 invoked by uid 500); 21 Oct 2015 04:25:27 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 27179 invoked by uid 99); 21 Oct 2015 04:25:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Oct 2015 04:25:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AB5152C14F3 for ; Wed, 21 Oct 2015 04:25:27 +0000 (UTC) Date: Wed, 21 Oct 2015 04:25:27 +0000 (UTC) From: "Freeman Fang (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CXF-6493) cxf-rt-transports-http-3.1.1.jar contains OSGi interface classes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-6493: --------------------------------- Assignee: Freeman Fang > 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 > Assignee: Freeman Fang > 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)