I've been looking for a plan when JAXB 2.0 is released
but couldn't find it.
Does anybody has this information?
Here is the dilemma: if we let everybody use the in-progress specs, then they will inject dependencies on non-final APIs and when the specs change later based on reviews, they will complain to us. But, if we don't, they will complain we don't let them do it.
I was personally bitten by the first many moons ago with the infamous JSP 0.92 spec; for years I would hear about people complaining that JSP 1.0 did not fully support the early, non-final, JSP 0.92.
Up until now, we have erred on being cautious, but we continue to listen very carefully to what the community is asking, so please continue to give us your feedback.
Message was edited by: pelegri
I assume you mean when will JAXB 2.0 be a final spec?
If so, the answer is... as soon as possible :-)
JAXB 2.0 will be in both J2EE 5 and in Mustang (J2SE 6), although JAXB 2.0 is not "bundled", and as such it could theoretically be released ahead of those. All software schedules are to be taken with a bit of salt, but, if I remember correctly, J2EE 5 is targetted around the end of the year, and Mustang is around the summer of 2006.
Is that what you were asking?
In about a month I will be refactoring our application.
The refactoring will involve the removal of all
configuration-data out of the database into xml.
I am now convinced that JAXB2.0 will be the perfect tool
to do this.
But if it cannot be used in a time-limit of 2 months
I will have to search for another tool.
So what I would like to know is : When will there be
a stable release of the RI of JAXB 2.0? (I hope that
it will be released earlier (and separate) than J2EE5)
Have you checked the technology preview? That might be stable enough to get started.
In any case, we are planning to start releasing regular builds to Java.Net "soon", and the spec is getting pretty stable. What I gave you was my best guess at final release dates.
The implementation of JAXB 2.0 will be at Java.Net, and it will be usable outside of J2EE. In particular, it is planned to be part of J2SE, in Mustang.
> Have you checked the technology preview? That might
> be stable enough to get started.
I think it is fair to say that the license that goes with the "technology preview" makes it for many of us out here impossible to start using it, even while the preview is stable enough for our purposes. Not giving a deadline or (much better) a license that would allow for redistribution for "direct or indirect commercial (including strategic) gain or advantage" isn't going to help adoption in my humble opinion.
Personally this waiting for final releases having a license attached that allows for redistribution is something that often makes me regret our choice for JAXB. Unfortunately there are no real alternatives for the Sun implementation. So to round up, I like JAXB but I dislike the licensing terms of the reference implementation previews.
> Personally this waiting for final releases having a
> license attached that allows for redistribution is
> something that often makes me regret our choice for
> JAXB. [b]Unfortunately there are no real alternatives
> for the Sun implementation.[/b]
Take a look at https://bindmark.dev.java.net/ and you may find some alternatives just around the corner...
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.