Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: dev@cxf.apache.org
Subject: Re: CXF 2.2.x OSGi Bundle / import on javax.servlet.*
Date: Sat, 3 Jul 2010 13:37:14 -0400
User-Agent: KMail/1.13.3 (Linux/2.6.34; KDE/4.4.4; x86_64; ; )
Cc: Florent BENOIT <Florent.BENOIT@ow2.org>
References: <4C2DB97D.3010404@ow2.org>
In-Reply-To: <4C2DB97D.3010404@ow2.org>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201007031337.15089.dkulp@apache.org>

On Friday 02 July 2010 6:03:41 am Florent BENOIT wrote:
>     Hi,
> 
> I'm facing a problem with the CXF 2.2.9 Bundle and Servlet API in OSGi mode
> If javax.servlet package is exported in 3.0.0 version, the CXF bundle
> won't start
> 
> This is because, in the MANIFEST generated by the following pom.xml
> [https://svn.apache.org/repos/asf/cxf/branches/2.2.x-fixes/distribution/bun
> dle/all/pom.xml ], there is the following code:
> /javax.servlet.*;version="[0.0,3)";resolution:=optional,/
> 
> Which means that javax.servlet package exported in 3.0 version won't be
> accepted
> Is there a reason to use 3 ? or maybe you could switch to
> /javax.servlet.*;version="[0.0,4)";resolution:=optional,/
> in order to accept javax.servlet exported in 3.0 version or remove the
> versioning number ?
> 
> I may open an issue on the jira tracker about this.
> 

Yes.  Please do.  And a patch would be nice.   :-)

Dan


> Note that this is the same case for the trunk version :
> https://svn.apache.org/repos/asf/cxf/trunk/distribution/bundle/all/pom.xml
> 
> Regards,
> 
> Florent

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog