You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcp-open@apache.org by Steve Loughran <st...@apache.org> on 2008/01/14 11:26:10 UTC
java6 and JAX-WS/JAXB
I've just discovered that the new release of java 6, java6.4, has just
updated its supported API versions of JAX-WS and JAX-B, from version 2.0
to 2.1:
http://weblogs.java.net/blog/ramapulavarthi/archive/2008/01/jaxws_21_and_ja.html
How does this fit in with the JCP rules?
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Re: java6 and JAX-WS/JAXB
Posted by Daniel Kulp <dk...@apache.org>.
As an example, this is a MAJOR pain for projects like CXF where we're
implementing JAX-WS.
Our 2.0.x branch (targets JAX-WS 2.0) builds fine with java5 and seems to
work OK on java6<4, but will now not build on java6>4.
On the flip side, our trunk (targetting JAX-WS 2.1) builds/runs fine on
java5, but has major issues with java6<4 without doing wacky endorsed
things. I haven't tried v4, but trunk MAY be able to build with it
since the API jars are updated. Thus, this may be a "win" for that.
In anycase, it's kind of annoying that we now have to document "howto"
for Java 5, Java6 < 4 and Java 6 >=4.
Dan
On Tuesday 15 January 2008, Steve Loughran wrote:
> Geir Magnusson Jr. wrote:
> > This has been working this way for years, hasn't it?
>
> Usually they keep the API constant -no new classes/methods. If you
> build for Java5, then you don't care which version of java5 your end
> user runs on. Here you cannot be 100% sure that anything built on java
> 6.4 even links on an earlier java 6 version.
>
> if you streer clear of JAX-WS and JAXB all should be well. I'm just
> surprised that they upgraded versions without having to go through
> some JCP process
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
Re: java6 and JAX-WS/JAXB
Posted by Steve Loughran <st...@apache.org>.
Geir Magnusson Jr. wrote:
> This has been working this way for years, hasn't it?
Usually they keep the API constant -no new classes/methods. If you build
for Java5, then you don't care which version of java5 your end user runs
on. Here you cannot be 100% sure that anything built on java 6.4 even
links on an earlier java 6 version.
if you streer clear of JAX-WS and JAXB all should be well. I'm just
surprised that they upgraded versions without having to go through some
JCP process
Re: java6 and JAX-WS/JAXB
Posted by "Geir Magnusson Jr." <ge...@pobox.com>.
This has been working this way for years, hasn't it?
geir
On Jan 15, 2008, at 11:12 AM, Steve Loughran wrote:
> Geir Magnusson Jr. wrote:
>> yeah, I think it's hard to see a problem - they are updating the
>> RI, for all practical purposes. I guess it's arguable that this is
>> mandating functionality by specifing new versions of the
>> subordinate JSRs, but I don't think anyone would care unless there
>> was a valid technical, legal or -ish objection
>> geir
>
> I think its a serious precedent, as it moves the maintenance
> releases into new features -and guarantees that any jaxb/jax-ws code
> built on the new version wont even link on java6 < v4, let alone
> work the same.
>
>> On Jan 14, 2008, at 10:26 AM, Steve Loughran wrote:
>>>
>>> I've just discovered that the new release of java 6, java6.4, has
>>> just updated its supported API versions of JAX-WS and JAX-B, from
>>> version 2.0 to 2.1:
>>>
>>> http://weblogs.java.net/blog/ramapulavarthi/archive/2008/01/jaxws_21_and_ja.html
>>>
>>> How does this fit in with the JCP rules?
>>>
>>> --
>>> Steve Loughran http://www.1060.org/blogxter/publish/5
>>>
>
>
>
Re: java6 and JAX-WS/JAXB
Posted by Steve Loughran <st...@apache.org>.
Geir Magnusson Jr. wrote:
> yeah, I think it's hard to see a problem - they are updating the RI, for
> all practical purposes. I guess it's arguable that this is mandating
> functionality by specifing new versions of the subordinate JSRs, but I
> don't think anyone would care unless there was a valid technical, legal
> or -ish objection
>
> geir
I think its a serious precedent, as it moves the maintenance releases
into new features -and guarantees that any jaxb/jax-ws code built on the
new version wont even link on java6 < v4, let alone work the same.
>
>
>
> On Jan 14, 2008, at 10:26 AM, Steve Loughran wrote:
>
>>
>> I've just discovered that the new release of java 6, java6.4, has just
>> updated its supported API versions of JAX-WS and JAX-B, from version
>> 2.0 to 2.1:
>>
>> http://weblogs.java.net/blog/ramapulavarthi/archive/2008/01/jaxws_21_and_ja.html
>>
>>
>> How does this fit in with the JCP rules?
>>
>> --
>> Steve Loughran http://www.1060.org/blogxter/publish/5
>>
>
Re: java6 and JAX-WS/JAXB
Posted by "Geir Magnusson Jr." <ge...@pobox.com>.
yeah, I think it's hard to see a problem - they are updating the RI,
for all practical purposes. I guess it's arguable that this is
mandating functionality by specifing new versions of the subordinate
JSRs, but I don't think anyone would care unless there was a valid
technical, legal or -ish objection
geir
On Jan 14, 2008, at 10:26 AM, Steve Loughran wrote:
>
> I've just discovered that the new release of java 6, java6.4, has
> just updated its supported API versions of JAX-WS and JAX-B, from
> version 2.0 to 2.1:
>
> http://weblogs.java.net/blog/ramapulavarthi/archive/2008/01/jaxws_21_and_ja.html
>
> How does this fit in with the JCP rules?
>
> --
> Steve Loughran http://www.1060.org/blogxter/publish/5
>
Re: java6 and JAX-WS/JAXB
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ah. got my numbers wrong.
- -- dims
Emmanuel Lecharny wrote:
| Davanum Srinivas wrote:
|> AFAIK, There is no JSR for Java 6. They are totally free to do what
|> they want is my guess.
| http://jcp.org/en/jsr/detail?id=270 maybe ?
|
| --
| cordialement, regards,
| Emmanuel Lécharny
| www.iktek.com
| directory.apache.org
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHi3ofgNg6eWEDv1kRAtchAJ0UjKTeYd8SeiPLnK7XJqcud54aVACg62MY
+aQ3c5RrOmyiaYJxIwZo51I=
=VNA9
-----END PGP SIGNATURE-----
Re: java6 and JAX-WS/JAXB
Posted by Emmanuel Lecharny <el...@gmail.com>.
Davanum Srinivas wrote:
> AFAIK, There is no JSR for Java 6. They are totally free to do what
> they want is my guess.
http://jcp.org/en/jsr/detail?id=270 maybe ?
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: java6 and JAX-WS/JAXB
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve,
the contents of JDK 1.5 / Java 5 is governed by http://jcp.org/en/jsr/detail?id=176 ("JSR 176: J2SETM 5.0 (Tiger)
Release Contents").
AFAIK, There is no JSR for Java 6. They are totally free to do what they want is my guess.
thanks,
dims
Steve Loughran wrote:
|
| I've just discovered that the new release of java 6, java6.4, has just
| updated its supported API versions of JAX-WS and JAX-B, from version 2.0
| to 2.1:
|
| http://weblogs.java.net/blog/ramapulavarthi/archive/2008/01/jaxws_21_and_ja.html
|
|
| How does this fit in with the JCP rules?
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHi3JIgNg6eWEDv1kRAg0hAJ9tJrpbnSlxq8uhtE9b2gKHauMpBACfRDjH
MMUjelUBQYb/eGK4/PpFinA=
=6kB2
-----END PGP SIGNATURE-----