Well,
I propose the following plan:
1/ Jetty ServiceMix Bundle 6.1.22_x will be present in system repo and
used by Karaf (especially for web/war/webconsole features) and
ServiceMix (especially the servicemix-http component)
2/ Jetty 7.1.x bundle will be present in system repo too and used by
Camel (especially for the camel-jetty component)
Regarding this, I'm working on SMX4 features to replace the overrided
Camel feature by the Camel karaf platform one.
Regards
JB
On 10/28/2010 08:20 PM, Jean-Baptiste Onofré wrote:
No problem Claus.
I know for the Guillaume's work as I'm Karaf commiter too ;) but we
can't wait for this enhancement as ServiceMix 4.3.0 will use Karaf 2.1.0
(already released).
As you said, I prefer to work on bundle "alignment" in ServiceMix.
Let me work on it ;)
Regards
JB
On 10/28/2010 05:58 PM, Claus Ibsen wrote:
Hi Jean
Sorry of posting directly to you on the dev forum but my gmail has
"Reply to all" as default.
I have posted on the dev since and Camel 2.5 do have Jetty 6.1 in the
camel-cxf feature for OSGi.
But then again it would be nice to align that version number with SMX
if possible.
But on the same time we know gnodet works on making karaf smarter in
terms of when installing features and being able to pick existing
bundles which fit.
So this we most likely be better in the future so camel-cxf feature
will be able to pickup and just use the jetty bundle already installed
by SMX.
On Thu, Oct 28, 2010 at 5:58 PM, Jean-Baptiste Onofré<[email protected]>
wrote:
Hi Claus,
regarding platform/karaf features, I quick checked and I've seen
jetty6.bundle.version used.
Let me check again :)
Regards
JB
On 10/28/2010 05:17 PM, Claus Ibsen wrote:
Camel 2.5 uses Jetty 7 in the camel-jetty component.
Its CXF 2.2 which are using Jetty 6.1.x.
CXF 2.3 has been upgraded to use Jetty 7 AFAIR
On Thu, Oct 28, 2010 at 4:33 PM, Jean-Baptiste Onofré<[email protected]>
wrote:
It was my plan, but:
- Karaf 2.1.0 uses jetty 6.1.22
- Camel 2.5.0 uses jetty 6.1.22
So, if I upgrade servicemix-http and SMX4 features to jetty 6.1.25, it
means
that we will have two jetty bundles in the system repo (and runtime).
Thoughts ?
Regards
JB
On 10/28/2010 04:19 PM, Gert Vanthienen wrote:
Jean-Baptiste,
Wouldn't it be better if we upgraded all the other bits to Jetty
6.1.25 then? If there are no API changes involved, we can still do
this while we're preparing for the 4.3.0 release and haven't actually
released anything, especially if there are significant
bugs/improvements in the newer version.
Regards,
Gert Vanthienen
------------------------
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Thu, Oct 28, 2010 at 3:31 PM,<[email protected]> wrote:
Author: jbonofre
Date: Thu Oct 28 13:31:12 2010
New Revision: 1028290
URL: http://svn.apache.org/viewvc?rev=1028290&view=rev
Log:
Downgrade Jetty version as other SMX modules still use Jetty 6.1.22.
You should upgrade to 6.1.25 which fixes issue around Jetty
performances.
Modified:
servicemix/smx3/trunk/pom.xml
Modified: servicemix/smx3/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/servicemix/smx3/trunk/pom.xml?rev=1028290&r1=1028289&r2=1028290&view=diff
==============================================================================
--- servicemix/smx3/trunk/pom.xml (original)
+++ servicemix/smx3/trunk/pom.xml Thu Oct 28 13:31:12 2010
@@ -102,7 +102,7 @@
<activeio-version>3.1.2</activeio-version>
<camel-version>2.5-SNAPSHOT</camel-version>
<jencks-version>2.2</jencks-version>
-<jetty-version>6.1.25</jetty-version>
+<jetty-version>6.1.22</jetty-version>
<jetty-servlet-api-version>6.1.14</jetty-servlet-api-version>
<geronimo-version>2.0.2</geronimo-version>
<geronimo-annotation-version>1.1.1</geronimo-annotation-version>
