You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Freeman Fang <fr...@gmail.com> on 2008/05/17 05:53:11 UTC
Re: Preferred JDK Version?
Hi Dan,
Can we say cxf 2.0.x fix branch work with jdk 1.6?
I saw several test failure build with 1.6.0_06, they are
testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testNoServiceImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testNoServiceNOPortType(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
Thanks
Freeman
Daniel Kulp wrote:
> On Tuesday 01 April 2008, davidwsica wrote:
>
>> Can someone provide an update on using JDK6 (latest update 5) with the
>> latest CXF 2.1? Are there still issues with JAX-WS 2.1?
>>
>
> Not with jaxws. We have one system test failure in the jaxrs stuff, but
> it's "non-critical". Basically, the hashmaps are ordered differently
> in J6 which is causing a problem with a test that is assuming a
> particular order. (yes, it's a bad test. We're looking at it.)
>
> Other than that, the entire CXF build builds and tests fine with Java6
> and the TCK has the same failures with Java6 as it does with Java5.
>
> Oh: there is one demo that is also failing that Sean is looking at.
>
> Dan
>
>
>
>
>> Thanks,
>> David
>>
>> James Mao wrote:
>>
>>> FYI, the JDK6 Update3 is the last update which contain the jaxws api
>>> 2.0 and jaxb api 2.0,
>>> the later release will contain the jaxws api 2.1 and jaxb api 2.1
>>>
>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21
>>> _in_jav.html
>>>
>>> And another difference this is license, we use Apache 2.0
>>>
>>> James
>>>
>>>
>>>> On Wednesday 10 October 2007, David W Sica wrote:
>>>>
>>>>> If JDK6 includes jaxws and jaxb jars what do I gain by using CXF
>>>>> over just JDK6? If I do decide to use JDK6, can I get more
>>>>> details regarding your response below on copying stuff to jre/lib?
>>>>>
>>>> Well, CXF supports a lot of things the JAX-WS implemention in JDK 6
>>>> does not. Things like jms transports, advanced https
>>>> configuration, Spring configuration, WS-A, WS-RM, etc....
>>>>
>>>> Let me clear about one thing:
>>>> CXF 2.0.x should work perfectly fine with JDK6. The api jars and
>>>> such that we ship are the same version as those built into JDK6.
>>>>
>>>> The problem will be with CXF 2.1 which is our current development
>>>> mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer
>>>> than what's in JDK6. To use the 2.1 snapshots, you'd most likely
>>>> need to copy the jaxb-* and jaxws-api-* jars (and maybe stax-api*)
>>>> from our lib directory to the jre/lib/endorsed dir. I'm not 100%
>>>> sure as I haven't tested it yet. At this point, I'm mostly
>>>> working on fixes and stuff still targetting 2.0.3 which should work
>>>> fine for JDK6. (although I don't have JDK6 installed to really
>>>> test with yet)
>>>>
>>>> Dan
>>>>
>>>>
>>>>> Thanks,
>>>>> David
>>>>>
>>>>> On 10/4/07, Daniel Kulp <dk...@apache.org> wrote:
>>>>>
>>>>>>> Also, should I
>>>>>>> pursue using JDK6 for deployment? Do I gain anything with JDK6
>>>>>>> as far as CXF is concerned?
>>>>>>>
>>>>>> I would not use jdk6 for right now. JDK6 is definitely going to
>>>>>> cause us problems on trunk. jk6 includes older versions of the
>>>>>> jaxws and jaxb jars which may conflict with the ones we require.
>>>>>> Thus, to work with jdk6, some stuff may need to be copied from
>>>>>> our lib dir to the jre/lib dir. We haven't spent much time
>>>>>> investigating that yet as trunk is still moving/changing pretty
>>>>>> fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the new
>>>>>> stuff on trunk that will be a problem.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> J. Daniel Kulp
>>>>>>
>
>
>
>
Re: Preferred JDK Version?
Posted by Freeman Fang <fr...@gmail.com>.
Thanks for clarifying this issue for me.
Cheers
Freeman
Daniel Kulp wrote:
>
> On May 16, 2008, at 11:53 PM, Freeman Fang wrote:
>
>> Hi Dan,
>>
>> Can we say cxf 2.0.x fix branch work with jdk 1.6?
>>
>
> No, the 2.0.x branch doesn't work with 1.6. It can "somewhat work"
> with JDK 1.6 up to update 3, but not at all with updates 4 and later
> without endorsing a bunch of things which would mess up the jaxws
> stuff built into the jdk.
>
>
>> I saw several test failure build with 1.6.0_06, they are
>> testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>> testNoServiceImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>> testNoServiceNOPortType(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>>
>
> The trunk (2.1) should work with JDK 1.6 update 4 and later except for
> one of the JAX-RS tests (last I checked, Sergey might have fixed it)
> due to Abdera relying on a particular hash map ordering or something
> like that. However, it WON'T work with updates 1 - 3. I t needs
> update 4 or later.
>
> Dan
>
>
>>
>> Thanks
>>
>> Freeman
>>
>> Daniel Kulp wrote:
>>> On Tuesday 01 April 2008, davidwsica wrote:
>>>
>>>> Can someone provide an update on using JDK6 (latest update 5) with the
>>>> latest CXF 2.1? Are there still issues with JAX-WS 2.1?
>>>>
>>>
>>> Not with jaxws. We have one system test failure in the jaxrs
>>> stuff, but it's "non-critical". Basically, the hashmaps are
>>> ordered differently in J6 which is causing a problem with a test
>>> that is assuming a particular order. (yes, it's a bad test.
>>> We're looking at it.)
>>>
>>> Other than that, the entire CXF build builds and tests fine with
>>> Java6 and the TCK has the same failures with Java6 as it does with
>>> Java5.
>>>
>>> Oh: there is one demo that is also failing that Sean is looking at.
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>> Thanks,
>>>> David
>>>>
>>>> James Mao wrote:
>>>>
>>>>> FYI, the JDK6 Update3 is the last update which contain the jaxws api
>>>>> 2.0 and jaxb api 2.0,
>>>>> the later release will contain the jaxws api 2.1 and jaxb api 2.1
>>>>>
>>>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21
>>>>> _in_jav.html
>>>>>
>>>>> And another difference this is license, we use Apache 2.0
>>>>>
>>>>> James
>>>>>
>>>>>
>>>>>> On Wednesday 10 October 2007, David W Sica wrote:
>>>>>>
>>>>>>> If JDK6 includes jaxws and jaxb jars what do I gain by using CXF
>>>>>>> over just JDK6? If I do decide to use JDK6, can I get more
>>>>>>> details regarding your response below on copying stuff to jre/lib?
>>>>>>>
>>>>>> Well, CXF supports a lot of things the JAX-WS implemention in JDK 6
>>>>>> does not. Things like jms transports, advanced https
>>>>>> configuration, Spring configuration, WS-A, WS-RM, etc....
>>>>>>
>>>>>> Let me clear about one thing:
>>>>>> CXF 2.0.x should work perfectly fine with JDK6. The api jars and
>>>>>> such that we ship are the same version as those built into JDK6.
>>>>>>
>>>>>> The problem will be with CXF 2.1 which is our current development
>>>>>> mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer
>>>>>> than what's in JDK6. To use the 2.1 snapshots, you'd most likely
>>>>>> need to copy the jaxb-* and jaxws-api-* jars (and maybe stax-api*)
>>>>>> from our lib directory to the jre/lib/endorsed dir. I'm not 100%
>>>>>> sure as I haven't tested it yet. At this point, I'm mostly
>>>>>> working on fixes and stuff still targetting 2.0.3 which should work
>>>>>> fine for JDK6. (although I don't have JDK6 installed to really
>>>>>> test with yet)
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>>
>>>>>>> Thanks,
>>>>>>> David
>>>>>>>
>>>>>>> On 10/4/07, Daniel Kulp <dk...@apache.org> wrote:
>>>>>>>
>>>>>>>>> Also, should I
>>>>>>>>> pursue using JDK6 for deployment? Do I gain anything with JDK6
>>>>>>>>> as far as CXF is concerned?
>>>>>>>>>
>>>>>>>> I would not use jdk6 for right now. JDK6 is definitely going to
>>>>>>>> cause us problems on trunk. jk6 includes older versions of the
>>>>>>>> jaxws and jaxb jars which may conflict with the ones we require.
>>>>>>>> Thus, to work with jdk6, some stuff may need to be copied from
>>>>>>>> our lib dir to the jre/lib dir. We haven't spent much time
>>>>>>>> investigating that yet as trunk is still moving/changing pretty
>>>>>>>> fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the new
>>>>>>>> stuff on trunk that will be a problem.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> J. Daniel Kulp
>>>>>>>>
>>>
>>>
>>>
>>>
>>
>
> ---
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
>
>
>
>
Re: Preferred JDK Version?
Posted by Daniel Kulp <dk...@apache.org>.
On May 17, 2008, at 12:11 PM, Adrian Corcoran wrote:
> So is it also the case that cxf 2.0.x will not run with jaxb 2.1?
> currently
> using jdk 5, & jaxb 2.0.5 but may move to to jaxb 2.1 and use jaxb
> 2.0 for
> wsdl2java/xjc
2.0.x SHOULD work fine with JAXB 2.1.x. However, it won't be "JAX-WS
2.0 compliant" if you do that. I've seen a couple people replace the
JAXB stuff in 2.0.x with 2.1 versions (to use SXC for example).
Dan
>
>
> On Sat, May 17, 2008 at 4:50 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> On May 16, 2008, at 11:53 PM, Freeman Fang wrote:
>>
>> Hi Dan,
>>>
>>> Can we say cxf 2.0.x fix branch work with jdk 1.6?
>>>
>>>
>> No, the 2.0.x branch doesn't work with 1.6. It can "somewhat work"
>> with
>> JDK 1.6 up to update 3, but not at all with updates 4 and later
>> without
>> endorsing a bunch of things which would mess up the jaxws stuff
>> built into
>> the jdk.
>>
>>
>> I saw several test failure build with 1.6.0_06, they are
>>> testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>>> testNoServiceImport
>>> (org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>>> testNoServiceNOPortType
>>> (org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>>>
>>
>> The trunk (2.1) should work with JDK 1.6 update 4 and later except
>> for one
>> of the JAX-RS tests (last I checked, Sergey might have fixed it)
>> due to
>> Abdera relying on a particular hash map ordering or something like
>> that.
>> However, it WON'T work with updates 1 - 3. I t needs update 4 or
>> later.
>>
>> Dan
>>
>>
>>
>>
>>> Thanks
>>>
>>> Freeman
>>>
>>> Daniel Kulp wrote:
>>>
>>>> On Tuesday 01 April 2008, davidwsica wrote:
>>>>
>>>> Can someone provide an update on using JDK6 (latest update 5)
>>>> with the
>>>>> latest CXF 2.1? Are there still issues with JAX-WS 2.1?
>>>>>
>>>>>
>>>> Not with jaxws. We have one system test failure in the jaxrs
>>>> stuff, but
>>>> it's "non-critical". Basically, the hashmaps are ordered
>>>> differently in J6
>>>> which is causing a problem with a test that is assuming a
>>>> particular order.
>>>> (yes, it's a bad test. We're looking at it.)
>>>>
>>>> Other than that, the entire CXF build builds and tests fine with
>>>> Java6
>>>> and the TCK has the same failures with Java6 as it does with Java5.
>>>>
>>>> Oh: there is one demo that is also failing that Sean is looking at.
>>>>
>>>> Dan
>>>>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>> David
>>>>>
>>>>> James Mao wrote:
>>>>>
>>>>> FYI, the JDK6 Update3 is the last update which contain the jaxws
>>>>> api
>>>>>> 2.0 and jaxb api 2.0,
>>>>>> the later release will contain the jaxws api 2.1 and jaxb api 2.1
>>>>>>
>>>>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21
>>>>>> _in_jav.html
>>>>>>
>>>>>> And another difference this is license, we use Apache 2.0
>>>>>>
>>>>>> James
>>>>>>
>>>>>>
>>>>>> On Wednesday 10 October 2007, David W Sica wrote:
>>>>>>>
>>>>>>> If JDK6 includes jaxws and jaxb jars what do I gain by using CXF
>>>>>>>> over just JDK6? If I do decide to use JDK6, can I get more
>>>>>>>> details regarding your response below on copying stuff to jre/
>>>>>>>> lib?
>>>>>>>>
>>>>>>>> Well, CXF supports a lot of things the JAX-WS implemention in
>>>>>>>> JDK 6
>>>>>>> does not. Things like jms transports, advanced https
>>>>>>> configuration, Spring configuration, WS-A, WS-RM, etc....
>>>>>>>
>>>>>>> Let me clear about one thing:
>>>>>>> CXF 2.0.x should work perfectly fine with JDK6. The api jars
>>>>>>> and
>>>>>>> such that we ship are the same version as those built into JDK6.
>>>>>>>
>>>>>>> The problem will be with CXF 2.1 which is our current
>>>>>>> development
>>>>>>> mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer
>>>>>>> than what's in JDK6. To use the 2.1 snapshots, you'd most
>>>>>>> likely
>>>>>>> need to copy the jaxb-* and jaxws-api-* jars (and maybe stax-
>>>>>>> api*)
>>>>>>> from our lib directory to the jre/lib/endorsed dir. I'm not
>>>>>>> 100%
>>>>>>> sure as I haven't tested it yet. At this point, I'm mostly
>>>>>>> working on fixes and stuff still targetting 2.0.3 which should
>>>>>>> work
>>>>>>> fine for JDK6. (although I don't have JDK6 installed to really
>>>>>>> test with yet)
>>>>>>>
>>>>>>> Dan
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>> David
>>>>>>>>
>>>>>>>> On 10/4/07, Daniel Kulp <dk...@apache.org> wrote:
>>>>>>>>
>>>>>>>> Also, should I
>>>>>>>>>> pursue using JDK6 for deployment? Do I gain anything with
>>>>>>>>>> JDK6
>>>>>>>>>> as far as CXF is concerned?
>>>>>>>>>>
>>>>>>>>>> I would not use jdk6 for right now. JDK6 is definitely
>>>>>>>>>> going to
>>>>>>>>> cause us problems on trunk. jk6 includes older versions of
>>>>>>>>> the
>>>>>>>>> jaxws and jaxb jars which may conflict with the ones we
>>>>>>>>> require.
>>>>>>>>> Thus, to work with jdk6, some stuff may need to be copied from
>>>>>>>>> our lib dir to the jre/lib dir. We haven't spent much time
>>>>>>>>> investigating that yet as trunk is still moving/changing
>>>>>>>>> pretty
>>>>>>>>> fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the
>>>>>>>>> new
>>>>>>>>> stuff on trunk that will be a problem.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> J. Daniel Kulp
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>> ---
>> Daniel Kulp
>> dkulp@apache.org
>> http://www.dankulp.com/blog
>>
>>
>>
>>
>>
---
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Preferred JDK Version?
Posted by Adrian Corcoran <ad...@gmail.com>.
So is it also the case that cxf 2.0.x will not run with jaxb 2.1? currently
using jdk 5, & jaxb 2.0.5 but may move to to jaxb 2.1 and use jaxb 2.0 for
wsdl2java/xjc
On Sat, May 17, 2008 at 4:50 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 16, 2008, at 11:53 PM, Freeman Fang wrote:
>
> Hi Dan,
>>
>> Can we say cxf 2.0.x fix branch work with jdk 1.6?
>>
>>
> No, the 2.0.x branch doesn't work with 1.6. It can "somewhat work" with
> JDK 1.6 up to update 3, but not at all with updates 4 and later without
> endorsing a bunch of things which would mess up the jaxws stuff built into
> the jdk.
>
>
> I saw several test failure build with 1.6.0_06, they are
>> testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>> testNoServiceImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>> testNoServiceNOPortType(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>>
>
> The trunk (2.1) should work with JDK 1.6 update 4 and later except for one
> of the JAX-RS tests (last I checked, Sergey might have fixed it) due to
> Abdera relying on a particular hash map ordering or something like that.
> However, it WON'T work with updates 1 - 3. I t needs update 4 or later.
>
> Dan
>
>
>
>
>> Thanks
>>
>> Freeman
>>
>> Daniel Kulp wrote:
>>
>>> On Tuesday 01 April 2008, davidwsica wrote:
>>>
>>> Can someone provide an update on using JDK6 (latest update 5) with the
>>>> latest CXF 2.1? Are there still issues with JAX-WS 2.1?
>>>>
>>>>
>>> Not with jaxws. We have one system test failure in the jaxrs stuff, but
>>> it's "non-critical". Basically, the hashmaps are ordered differently in J6
>>> which is causing a problem with a test that is assuming a particular order.
>>> (yes, it's a bad test. We're looking at it.)
>>>
>>> Other than that, the entire CXF build builds and tests fine with Java6
>>> and the TCK has the same failures with Java6 as it does with Java5.
>>>
>>> Oh: there is one demo that is also failing that Sean is looking at.
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>> Thanks,
>>>> David
>>>>
>>>> James Mao wrote:
>>>>
>>>> FYI, the JDK6 Update3 is the last update which contain the jaxws api
>>>>> 2.0 and jaxb api 2.0,
>>>>> the later release will contain the jaxws api 2.1 and jaxb api 2.1
>>>>>
>>>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21
>>>>> _in_jav.html
>>>>>
>>>>> And another difference this is license, we use Apache 2.0
>>>>>
>>>>> James
>>>>>
>>>>>
>>>>> On Wednesday 10 October 2007, David W Sica wrote:
>>>>>>
>>>>>> If JDK6 includes jaxws and jaxb jars what do I gain by using CXF
>>>>>>> over just JDK6? If I do decide to use JDK6, can I get more
>>>>>>> details regarding your response below on copying stuff to jre/lib?
>>>>>>>
>>>>>>> Well, CXF supports a lot of things the JAX-WS implemention in JDK 6
>>>>>> does not. Things like jms transports, advanced https
>>>>>> configuration, Spring configuration, WS-A, WS-RM, etc....
>>>>>>
>>>>>> Let me clear about one thing:
>>>>>> CXF 2.0.x should work perfectly fine with JDK6. The api jars and
>>>>>> such that we ship are the same version as those built into JDK6.
>>>>>>
>>>>>> The problem will be with CXF 2.1 which is our current development
>>>>>> mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer
>>>>>> than what's in JDK6. To use the 2.1 snapshots, you'd most likely
>>>>>> need to copy the jaxb-* and jaxws-api-* jars (and maybe stax-api*)
>>>>>> from our lib directory to the jre/lib/endorsed dir. I'm not 100%
>>>>>> sure as I haven't tested it yet. At this point, I'm mostly
>>>>>> working on fixes and stuff still targetting 2.0.3 which should work
>>>>>> fine for JDK6. (although I don't have JDK6 installed to really
>>>>>> test with yet)
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>> David
>>>>>>>
>>>>>>> On 10/4/07, Daniel Kulp <dk...@apache.org> wrote:
>>>>>>>
>>>>>>> Also, should I
>>>>>>>>> pursue using JDK6 for deployment? Do I gain anything with JDK6
>>>>>>>>> as far as CXF is concerned?
>>>>>>>>>
>>>>>>>>> I would not use jdk6 for right now. JDK6 is definitely going to
>>>>>>>> cause us problems on trunk. jk6 includes older versions of the
>>>>>>>> jaxws and jaxb jars which may conflict with the ones we require.
>>>>>>>> Thus, to work with jdk6, some stuff may need to be copied from
>>>>>>>> our lib dir to the jre/lib dir. We haven't spent much time
>>>>>>>> investigating that yet as trunk is still moving/changing pretty
>>>>>>>> fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the new
>>>>>>>> stuff on trunk that will be a problem.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> J. Daniel Kulp
>>>>>>>>
>>>>>>>>
>>>
>>>
>>>
>>>
>>
> ---
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
>
>
>
>
Re: Preferred JDK Version?
Posted by Daniel Kulp <dk...@apache.org>.
On May 16, 2008, at 11:53 PM, Freeman Fang wrote:
> Hi Dan,
>
> Can we say cxf 2.0.x fix branch work with jdk 1.6?
>
No, the 2.0.x branch doesn't work with 1.6. It can "somewhat work"
with JDK 1.6 up to update 3, but not at all with updates 4 and later
without endorsing a bunch of things which would mess up the jaxws
stuff built into the jdk.
> I saw several test failure build with 1.6.0_06, they are
> testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
> testNoServiceImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
> testNoServiceNOPortType
> (org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
The trunk (2.1) should work with JDK 1.6 update 4 and later except for
one of the JAX-RS tests (last I checked, Sergey might have fixed it)
due to Abdera relying on a particular hash map ordering or something
like that. However, it WON'T work with updates 1 - 3. I t needs
update 4 or later.
Dan
>
> Thanks
>
> Freeman
>
> Daniel Kulp wrote:
>> On Tuesday 01 April 2008, davidwsica wrote:
>>
>>> Can someone provide an update on using JDK6 (latest update 5) with
>>> the
>>> latest CXF 2.1? Are there still issues with JAX-WS 2.1?
>>>
>>
>> Not with jaxws. We have one system test failure in the jaxrs
>> stuff, but it's "non-critical". Basically, the hashmaps are
>> ordered differently in J6 which is causing a problem with a test
>> that is assuming a particular order. (yes, it's a bad test.
>> We're looking at it.)
>>
>> Other than that, the entire CXF build builds and tests fine with
>> Java6 and the TCK has the same failures with Java6 as it does with
>> Java5.
>>
>> Oh: there is one demo that is also failing that Sean is looking at.
>>
>> Dan
>>
>>
>>
>>
>>> Thanks,
>>> David
>>>
>>> James Mao wrote:
>>>
>>>> FYI, the JDK6 Update3 is the last update which contain the jaxws
>>>> api
>>>> 2.0 and jaxb api 2.0,
>>>> the later release will contain the jaxws api 2.1 and jaxb api 2.1
>>>>
>>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/
>>>> jaxws_21
>>>> _in_jav.html
>>>>
>>>> And another difference this is license, we use Apache 2.0
>>>>
>>>> James
>>>>
>>>>
>>>>> On Wednesday 10 October 2007, David W Sica wrote:
>>>>>
>>>>>> If JDK6 includes jaxws and jaxb jars what do I gain by using CXF
>>>>>> over just JDK6? If I do decide to use JDK6, can I get more
>>>>>> details regarding your response below on copying stuff to jre/
>>>>>> lib?
>>>>>>
>>>>> Well, CXF supports a lot of things the JAX-WS implemention in
>>>>> JDK 6
>>>>> does not. Things like jms transports, advanced https
>>>>> configuration, Spring configuration, WS-A, WS-RM, etc....
>>>>>
>>>>> Let me clear about one thing:
>>>>> CXF 2.0.x should work perfectly fine with JDK6. The api jars and
>>>>> such that we ship are the same version as those built into JDK6.
>>>>>
>>>>> The problem will be with CXF 2.1 which is our current development
>>>>> mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer
>>>>> than what's in JDK6. To use the 2.1 snapshots, you'd most likely
>>>>> need to copy the jaxb-* and jaxws-api-* jars (and maybe stax-api*)
>>>>> from our lib directory to the jre/lib/endorsed dir. I'm not 100%
>>>>> sure as I haven't tested it yet. At this point, I'm mostly
>>>>> working on fixes and stuff still targetting 2.0.3 which should
>>>>> work
>>>>> fine for JDK6. (although I don't have JDK6 installed to really
>>>>> test with yet)
>>>>>
>>>>> Dan
>>>>>
>>>>>
>>>>>> Thanks,
>>>>>> David
>>>>>>
>>>>>> On 10/4/07, Daniel Kulp <dk...@apache.org> wrote:
>>>>>>
>>>>>>>> Also, should I
>>>>>>>> pursue using JDK6 for deployment? Do I gain anything with JDK6
>>>>>>>> as far as CXF is concerned?
>>>>>>>>
>>>>>>> I would not use jdk6 for right now. JDK6 is definitely going
>>>>>>> to
>>>>>>> cause us problems on trunk. jk6 includes older versions of the
>>>>>>> jaxws and jaxb jars which may conflict with the ones we require.
>>>>>>> Thus, to work with jdk6, some stuff may need to be copied from
>>>>>>> our lib dir to the jre/lib dir. We haven't spent much time
>>>>>>> investigating that yet as trunk is still moving/changing pretty
>>>>>>> fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the new
>>>>>>> stuff on trunk that will be a problem.
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> J. Daniel Kulp
>>>>>>>
>>
>>
>>
>>
>
---
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Preferred JDK Version?
Posted by Daniel Kulp <dk...@apache.org>.
On May 17, 2008, at 5:21 AM, Freeman Fang wrote:
> And I also build cxf trunk with jdk1.6.0_06 and get different test
> failure
> testTypedefGeneration
> (org.apache.cxf.tools.corba.processors.IDLToWSDLGenerationTest)
>
> Can shed me some light shall we build cxf with jdk 16?
> Thanks very much
Hmm... I had that test working on update 4 on Linux. I'll dig
into next week to make sure everything on trunk is OK again.
Dan
>
>
> Freeman
>
> Freeman Fang wrote:
>> Hi Dan,
>>
>> Can we say cxf 2.0.x fix branch work with jdk 1.6?
>>
>> I saw several test failure build with 1.6.0_06, they are
>> testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>> testNoServiceImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>> testNoServiceNOPortType
>> (org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>>
>> Thanks
>>
>> Freeman
>>
>> Daniel Kulp wrote:
>>> On Tuesday 01 April 2008, davidwsica wrote:
>>>
>>>> Can someone provide an update on using JDK6 (latest update 5)
>>>> with the
>>>> latest CXF 2.1? Are there still issues with JAX-WS 2.1?
>>>>
>>>
>>> Not with jaxws. We have one system test failure in the jaxrs
>>> stuff, but it's "non-critical". Basically, the hashmaps are
>>> ordered differently in J6 which is causing a problem with a test
>>> that is assuming a particular order. (yes, it's a bad test.
>>> We're looking at it.)
>>>
>>> Other than that, the entire CXF build builds and tests fine with
>>> Java6 and the TCK has the same failures with Java6 as it does with
>>> Java5.
>>>
>>> Oh: there is one demo that is also failing that Sean is looking at.
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>> Thanks,
>>>> David
>>>>
>>>> James Mao wrote:
>>>>
>>>>> FYI, the JDK6 Update3 is the last update which contain the jaxws
>>>>> api
>>>>> 2.0 and jaxb api 2.0,
>>>>> the later release will contain the jaxws api 2.1 and jaxb api 2.1
>>>>>
>>>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21
>>>>> _in_jav.html
>>>>>
>>>>> And another difference this is license, we use Apache 2.0
>>>>>
>>>>> James
>>>>>
>>>>>
>>>>>> On Wednesday 10 October 2007, David W Sica wrote:
>>>>>>
>>>>>>> If JDK6 includes jaxws and jaxb jars what do I gain by using CXF
>>>>>>> over just JDK6? If I do decide to use JDK6, can I get more
>>>>>>> details regarding your response below on copying stuff to jre/
>>>>>>> lib?
>>>>>>>
>>>>>> Well, CXF supports a lot of things the JAX-WS implemention in
>>>>>> JDK 6
>>>>>> does not. Things like jms transports, advanced https
>>>>>> configuration, Spring configuration, WS-A, WS-RM, etc....
>>>>>>
>>>>>> Let me clear about one thing:
>>>>>> CXF 2.0.x should work perfectly fine with JDK6. The api jars
>>>>>> and
>>>>>> such that we ship are the same version as those built into JDK6.
>>>>>>
>>>>>> The problem will be with CXF 2.1 which is our current development
>>>>>> mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer
>>>>>> than what's in JDK6. To use the 2.1 snapshots, you'd most
>>>>>> likely
>>>>>> need to copy the jaxb-* and jaxws-api-* jars (and maybe stax-
>>>>>> api*)
>>>>>> from our lib directory to the jre/lib/endorsed dir. I'm not
>>>>>> 100%
>>>>>> sure as I haven't tested it yet. At this point, I'm mostly
>>>>>> working on fixes and stuff still targetting 2.0.3 which should
>>>>>> work
>>>>>> fine for JDK6. (although I don't have JDK6 installed to really
>>>>>> test with yet)
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>>
>>>>>>> Thanks,
>>>>>>> David
>>>>>>>
>>>>>>> On 10/4/07, Daniel Kulp <dk...@apache.org> wrote:
>>>>>>>
>>>>>>>>> Also, should I
>>>>>>>>> pursue using JDK6 for deployment? Do I gain anything with
>>>>>>>>> JDK6
>>>>>>>>> as far as CXF is concerned?
>>>>>>>>>
>>>>>>>> I would not use jdk6 for right now. JDK6 is definitely
>>>>>>>> going to
>>>>>>>> cause us problems on trunk. jk6 includes older versions of
>>>>>>>> the
>>>>>>>> jaxws and jaxb jars which may conflict with the ones we
>>>>>>>> require.
>>>>>>>> Thus, to work with jdk6, some stuff may need to be copied from
>>>>>>>> our lib dir to the jre/lib dir. We haven't spent much time
>>>>>>>> investigating that yet as trunk is still moving/changing pretty
>>>>>>>> fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the
>>>>>>>> new
>>>>>>>> stuff on trunk that will be a problem.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> J. Daniel Kulp
>>>>>>>>
>>>
>>>
>>>
>>>
>>
>>
>
---
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Preferred JDK Version?
Posted by Freeman Fang <fr...@gmail.com>.
And I also build cxf trunk with jdk1.6.0_06 and get different test failure
testTypedefGeneration(org.apache.cxf.tools.corba.processors.IDLToWSDLGenerationTest)
Can shed me some light shall we build cxf with jdk 16?
Thanks very much
Freeman
Freeman Fang wrote:
> Hi Dan,
>
> Can we say cxf 2.0.x fix branch work with jdk 1.6?
>
> I saw several test failure build with 1.6.0_06, they are
> testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
> testNoServiceImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
> testNoServiceNOPortType(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
>
>
> Thanks
>
> Freeman
>
> Daniel Kulp wrote:
>> On Tuesday 01 April 2008, davidwsica wrote:
>>
>>> Can someone provide an update on using JDK6 (latest update 5) with the
>>> latest CXF 2.1? Are there still issues with JAX-WS 2.1?
>>>
>>
>> Not with jaxws. We have one system test failure in the jaxrs stuff,
>> but it's "non-critical". Basically, the hashmaps are ordered
>> differently in J6 which is causing a problem with a test that is
>> assuming a particular order. (yes, it's a bad test. We're looking
>> at it.)
>>
>> Other than that, the entire CXF build builds and tests fine with
>> Java6 and the TCK has the same failures with Java6 as it does with
>> Java5.
>>
>> Oh: there is one demo that is also failing that Sean is looking at.
>>
>> Dan
>>
>>
>>
>>
>>> Thanks,
>>> David
>>>
>>> James Mao wrote:
>>>
>>>> FYI, the JDK6 Update3 is the last update which contain the jaxws api
>>>> 2.0 and jaxb api 2.0,
>>>> the later release will contain the jaxws api 2.1 and jaxb api 2.1
>>>>
>>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21
>>>> _in_jav.html
>>>>
>>>> And another difference this is license, we use Apache 2.0
>>>>
>>>> James
>>>>
>>>>
>>>>> On Wednesday 10 October 2007, David W Sica wrote:
>>>>>
>>>>>> If JDK6 includes jaxws and jaxb jars what do I gain by using CXF
>>>>>> over just JDK6? If I do decide to use JDK6, can I get more
>>>>>> details regarding your response below on copying stuff to jre/lib?
>>>>>>
>>>>> Well, CXF supports a lot of things the JAX-WS implemention in JDK 6
>>>>> does not. Things like jms transports, advanced https
>>>>> configuration, Spring configuration, WS-A, WS-RM, etc....
>>>>>
>>>>> Let me clear about one thing:
>>>>> CXF 2.0.x should work perfectly fine with JDK6. The api jars and
>>>>> such that we ship are the same version as those built into JDK6.
>>>>>
>>>>> The problem will be with CXF 2.1 which is our current development
>>>>> mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer
>>>>> than what's in JDK6. To use the 2.1 snapshots, you'd most likely
>>>>> need to copy the jaxb-* and jaxws-api-* jars (and maybe stax-api*)
>>>>> from our lib directory to the jre/lib/endorsed dir. I'm not 100%
>>>>> sure as I haven't tested it yet. At this point, I'm mostly
>>>>> working on fixes and stuff still targetting 2.0.3 which should work
>>>>> fine for JDK6. (although I don't have JDK6 installed to really
>>>>> test with yet)
>>>>>
>>>>> Dan
>>>>>
>>>>>
>>>>>> Thanks,
>>>>>> David
>>>>>>
>>>>>> On 10/4/07, Daniel Kulp <dk...@apache.org> wrote:
>>>>>>
>>>>>>>> Also, should I
>>>>>>>> pursue using JDK6 for deployment? Do I gain anything with JDK6
>>>>>>>> as far as CXF is concerned?
>>>>>>>>
>>>>>>> I would not use jdk6 for right now. JDK6 is definitely going to
>>>>>>> cause us problems on trunk. jk6 includes older versions of the
>>>>>>> jaxws and jaxb jars which may conflict with the ones we require.
>>>>>>> Thus, to work with jdk6, some stuff may need to be copied from
>>>>>>> our lib dir to the jre/lib dir. We haven't spent much time
>>>>>>> investigating that yet as trunk is still moving/changing pretty
>>>>>>> fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the new
>>>>>>> stuff on trunk that will be a problem.
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> J. Daniel Kulp
>>>>>>>
>>
>>
>>
>>
>
>