Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT
breaks CXF
------------------------------------------------------------------------------------
Key: SMX4-442
URL: https://issues.apache.org/activemq/browse/SMX4-442
Project: ServiceMix 4
Issue Type: Bug
Affects Versions: 4.1.0
Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
Reporter: Vincent Girard-Reydet
Fix For: 4.1.0
There is an inconsistency between the declared versions of Jetty and PAX-WEB
between the following features:
- web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
- http (apache-felix-karaf-1.1.0-SNAPSHOT)
Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
Initially PAX-WEB 0.6.0 is installed :
[ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp
Support (0.6.0)
[ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web
Container (0.6.0)
[ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender -
WAR (0.5.0)
[ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender -
Whiteboard (0.5.0)
If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to
reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
Now I install cxf-camel. First, it hangs. If I restart the server, I end up
with the following bundles added but not started:
[ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API
(0.7.1)
[ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service
SPI (0.7.1)
[ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime
(0.7.1)
[ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty
(0.7.1)
...
[ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix
Bundles: jetty-6.1.14 (6.1.14.2)
...
[ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix
Bundles: woodstox-3.2.8 (3.2.8.1)
This is sufficient to cause an exception when trying to access
http://localhost:8181/cxf/HelloWorld?wsdl.
Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to
solve the problem. This does *NOT* prevent camel-cxf from working (tested with
a sample project of mine).
This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
