You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by William Tam <em...@gmail.com> on 2010/11/04 15:40:18 UTC
[DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Willem and I would like to start a discussion regarding which release of
Camel should be upgraded to CXF 2.3. There is a lot of good reasons to
upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean
stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see
https://issues.apache.org/activemq/browse/CAMEL-3308) It also means that
users who upgrade to Camel 2.6 will be forced to upgrade to CXF 2.3. It
is almost certain that Camel 3 will have CXF 2.3.x, which (Camel 3) is
targeted from 1st quarter of 2011. It is not that far away. So,
let's hear your opinion on whether we should upgrade to CXF 2.3 in Camel
2.6 or not?
Thanks,
Willem and William
Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Is CXF 2.3 compatible with JDK 1.5.
I had an issue compiling camel-soap with some recent CXF 2.3 tooling upgrade.
See
https://issues.apache.org/activemq/browse/CAMEL-3310
On Thu, Nov 4, 2010 at 3:47 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Thursday 04 November 2010 10:40:18 am William Tam wrote:
>> Willem and I would like to start a discussion regarding which release of
>> Camel should be upgraded to CXF 2.3. There is a lot of good reasons to
>> upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean
>> stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see
>> https://issues.apache.org/activemq/browse/CAMEL-3308) It also means that
>> users who upgrade to Camel 2.6 will be forced to upgrade to CXF 2.3. It
>> is almost certain that Camel 3 will have CXF 2.3.x, which (Camel 3) is
>> targeted from 1st quarter of 2011. It is not that far away. So,
>> let's hear your opinion on whether we should upgrade to CXF 2.3 in Camel
>> 2.6 or not?
>
> I think it needs to be. Updating from 2.2 to 2.3 is a fairly minor upgrade
> (except for the continuation thing which was never documented and thus not
> likely used extensively at all). With 2.2 likely to go into unsupported mode
> fairly soon, getting Camel out with 2.3 is pretty important.
>
> I'd also like to get 2.3 into Camel quickly (at least for the builds) so we
> can identify anything that NEEDS to be fixed and get them into 2.3.1 which I'd
> like to do later this month.
>
> The camel 3.0 version in Q1 is still not finalized/settled, so I wouldn't use
> that as part of the decision point.
>
> Dan
>
>
>>
>> Thanks,
>> Willem and William
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Is CXF 2.3 compatible with JDK 1.5.
I had an issue compiling camel-soap with some recent CXF 2.3 tooling upgrade.
See
https://issues.apache.org/activemq/browse/CAMEL-3310
On Thu, Nov 4, 2010 at 3:47 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Thursday 04 November 2010 10:40:18 am William Tam wrote:
>> Willem and I would like to start a discussion regarding which release of
>> Camel should be upgraded to CXF 2.3. There is a lot of good reasons to
>> upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean
>> stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see
>> https://issues.apache.org/activemq/browse/CAMEL-3308) It also means that
>> users who upgrade to Camel 2.6 will be forced to upgrade to CXF 2.3. It
>> is almost certain that Camel 3 will have CXF 2.3.x, which (Camel 3) is
>> targeted from 1st quarter of 2011. It is not that far away. So,
>> let's hear your opinion on whether we should upgrade to CXF 2.3 in Camel
>> 2.6 or not?
>
> I think it needs to be. Updating from 2.2 to 2.3 is a fairly minor upgrade
> (except for the continuation thing which was never documented and thus not
> likely used extensively at all). With 2.2 likely to go into unsupported mode
> fairly soon, getting Camel out with 2.3 is pretty important.
>
> I'd also like to get 2.3 into Camel quickly (at least for the builds) so we
> can identify anything that NEEDS to be fixed and get them into 2.3.1 which I'd
> like to do later this month.
>
> The camel 3.0 version in Q1 is still not finalized/settled, so I wouldn't use
> that as part of the decision point.
>
> Dan
>
>
>>
>> Thanks,
>> Willem and William
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Posted by Daniel Kulp <dk...@apache.org>.
On Thursday 04 November 2010 10:40:18 am William Tam wrote:
> Willem and I would like to start a discussion regarding which release of
> Camel should be upgraded to CXF 2.3. There is a lot of good reasons to
> upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean
> stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see
> https://issues.apache.org/activemq/browse/CAMEL-3308) It also means that
> users who upgrade to Camel 2.6 will be forced to upgrade to CXF 2.3. It
> is almost certain that Camel 3 will have CXF 2.3.x, which (Camel 3) is
> targeted from 1st quarter of 2011. It is not that far away. So,
> let's hear your opinion on whether we should upgrade to CXF 2.3 in Camel
> 2.6 or not?
I think it needs to be. Updating from 2.2 to 2.3 is a fairly minor upgrade
(except for the continuation thing which was never documented and thus not
likely used extensively at all). With 2.2 likely to go into unsupported mode
fairly soon, getting Camel out with 2.3 is pretty important.
I'd also like to get 2.3 into Camel quickly (at least for the builds) so we
can identify anything that NEEDS to be fixed and get them into 2.3.1 which I'd
like to do later this month.
The camel 3.0 version in Q1 is still not finalized/settled, so I wouldn't use
that as part of the decision point.
Dan
>
> Thanks,
> Willem and William
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Posted by William Tam <em...@gmail.com>.
Thanks.
On 11/04/2010 10:21 PM, Willem Jiang wrote:
> I think the configuration is OK, but there are some big upgrade of
> Jetty, jaxws, jaxb in the CXF 2.3.x will make the user to do
> adjustment his runtime evironment. Fortunately camel-cxf have nothing
> to with it.
>
> I just did some work to make camel-cxf work with CXF 2.2.x and CXF
> 2.3.x at the same time.
> The user can make their own choice now :)
>
>
> On 11/5/10 4:33 AM, William Tam wrote:
>> I think there are reasons not to (not sure if they are good reasons
>> though)
>>
>> * Don't have to touch Camel 2.x camel-cxf component We can then direct
>> the effort/focus to Camel 3 to make it happen sooner.
>> * We probably still don't know this for sure yet. Besides the runtime,
>> spring configuration and camel-cxf APIs probably should be backward
>> compatible. Otherwise, Camel 2.6 upgrade could mean configuration change
>> exercises for users.
>>
>>
>>
>> On 11/04/2010 03:28 PM, Hadrian Zbarcea wrote:
>>> Is there a good reason not to?
>>>
>>> One would use the camel-cxf component either to expose a route as a ws
>>> (from) or to invoke a ws (to). From this point of view, the backward
>>> compatibility we require is on the wire, which I am pretty certain we
>>> do satisfy. The other issue is deployment, camel having a new set of
>>> dependencies would require an app to upgrade. In an osgi environment
>>> that should not be a problem. In a webapp it could be a bit
>>> problematic, but if the camel piece is in a separate war, that should
>>> be fine too.
>>>
>>> By the way, this is a discussion for dev@, not users@.
>>>
>>> Cheers
>>> Hadrian
>>>
>>> On Nov 4, 2010, at 10:40 AM, William Tam wrote:
>>>
>>>> Willem and I would like to start a discussion regarding which release
>>>> of Camel should be upgraded to CXF 2.3. There is a lot of good
>>>> reasons to upgrade to CXF 2.3. However, upgrading it in Camel 2.6
>>>> could mean stopping supporting CXF 2.2.x in the future Camel 2.x
>>>> releases. (see https://issues.apache.org/activemq/browse/CAMEL-3308)
>>>> It also means that users who upgrade to Camel 2.6 will be forced to
>>>> upgrade to CXF 2.3. It is almost certain that Camel 3 will have CXF
>>>> 2.3.x, which (Camel 3) is targeted from 1st quarter of 2011. It is
>>>> not that far away. So, let's hear your opinion on whether we should
>>>> upgrade to CXF 2.3 in Camel 2.6 or not?
>>>>
>>>> Thanks,
>>>> Willem and William
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
>
Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Posted by Willem Jiang <wi...@gmail.com>.
I think the configuration is OK, but there are some big upgrade of
Jetty, jaxws, jaxb in the CXF 2.3.x will make the user to do adjustment
his runtime evironment. Fortunately camel-cxf have nothing to with it.
I just did some work to make camel-cxf work with CXF 2.2.x and CXF 2.3.x
at the same time.
The user can make their own choice now :)
On 11/5/10 4:33 AM, William Tam wrote:
> I think there are reasons not to (not sure if they are good reasons though)
>
> * Don't have to touch Camel 2.x camel-cxf component We can then direct
> the effort/focus to Camel 3 to make it happen sooner.
> * We probably still don't know this for sure yet. Besides the runtime,
> spring configuration and camel-cxf APIs probably should be backward
> compatible. Otherwise, Camel 2.6 upgrade could mean configuration change
> exercises for users.
>
>
>
> On 11/04/2010 03:28 PM, Hadrian Zbarcea wrote:
>> Is there a good reason not to?
>>
>> One would use the camel-cxf component either to expose a route as a ws
>> (from) or to invoke a ws (to). From this point of view, the backward
>> compatibility we require is on the wire, which I am pretty certain we
>> do satisfy. The other issue is deployment, camel having a new set of
>> dependencies would require an app to upgrade. In an osgi environment
>> that should not be a problem. In a webapp it could be a bit
>> problematic, but if the camel piece is in a separate war, that should
>> be fine too.
>>
>> By the way, this is a discussion for dev@, not users@.
>>
>> Cheers
>> Hadrian
>>
>> On Nov 4, 2010, at 10:40 AM, William Tam wrote:
>>
>>> Willem and I would like to start a discussion regarding which release
>>> of Camel should be upgraded to CXF 2.3. There is a lot of good
>>> reasons to upgrade to CXF 2.3. However, upgrading it in Camel 2.6
>>> could mean stopping supporting CXF 2.2.x in the future Camel 2.x
>>> releases. (see https://issues.apache.org/activemq/browse/CAMEL-3308)
>>> It also means that users who upgrade to Camel 2.6 will be forced to
>>> upgrade to CXF 2.3. It is almost certain that Camel 3 will have CXF
>>> 2.3.x, which (Camel 3) is targeted from 1st quarter of 2011. It is
>>> not that far away. So, let's hear your opinion on whether we should
>>> upgrade to CXF 2.3 in Camel 2.6 or not?
>>>
>>> Thanks,
>>> Willem and William
>>>
>>>
>>>
>>>
>>>
>>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Posted by William Tam <em...@gmail.com>.
I think there are reasons not to (not sure if they are good reasons though)
* Don't have to touch Camel 2.x camel-cxf component We can then direct
the effort/focus to Camel 3 to make it happen sooner.
* We probably still don't know this for sure yet. Besides the runtime,
spring configuration and camel-cxf APIs probably should be backward
compatible. Otherwise, Camel 2.6 upgrade could mean configuration
change exercises for users.
On 11/04/2010 03:28 PM, Hadrian Zbarcea wrote:
> Is there a good reason not to?
>
> One would use the camel-cxf component either to expose a route as a ws (from) or to invoke a ws (to). From this point of view, the backward compatibility we require is on the wire, which I am pretty certain we do satisfy. The other issue is deployment, camel having a new set of dependencies would require an app to upgrade. In an osgi environment that should not be a problem. In a webapp it could be a bit problematic, but if the camel piece is in a separate war, that should be fine too.
>
> By the way, this is a discussion for dev@, not users@.
>
> Cheers
> Hadrian
>
> On Nov 4, 2010, at 10:40 AM, William Tam wrote:
>
>
>> Willem and I would like to start a discussion regarding which release of Camel should be upgraded to CXF 2.3. There is a lot of good reasons to upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see https://issues.apache.org/activemq/browse/CAMEL-3308) It also means that users who upgrade to Camel 2.6 will be forced to upgrade to CXF 2.3. It is almost certain that Camel 3 will have CXF 2.3.x, which (Camel 3) is targeted from 1st quarter of 2011. It is not that far away. So, let's hear your opinion on whether we should upgrade to CXF 2.3 in Camel 2.6 or not?
>>
>> Thanks,
>> Willem and William
>>
>>
>>
>>
>>
>>
>
>
Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Is there a good reason not to?
One would use the camel-cxf component either to expose a route as a ws (from) or to invoke a ws (to). From this point of view, the backward compatibility we require is on the wire, which I am pretty certain we do satisfy. The other issue is deployment, camel having a new set of dependencies would require an app to upgrade. In an osgi environment that should not be a problem. In a webapp it could be a bit problematic, but if the camel piece is in a separate war, that should be fine too.
By the way, this is a discussion for dev@, not users@.
Cheers
Hadrian
On Nov 4, 2010, at 10:40 AM, William Tam wrote:
>
> Willem and I would like to start a discussion regarding which release of Camel should be upgraded to CXF 2.3. There is a lot of good reasons to upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see https://issues.apache.org/activemq/browse/CAMEL-3308) It also means that users who upgrade to Camel 2.6 will be forced to upgrade to CXF 2.3. It is almost certain that Camel 3 will have CXF 2.3.x, which (Camel 3) is targeted from 1st quarter of 2011. It is not that far away. So, let's hear your opinion on whether we should upgrade to CXF 2.3 in Camel 2.6 or not?
>
> Thanks,
> Willem and William
>
>
>
>
>