Posted by kohsuke
on August 14, 2006 at 12:16 PM PDT
I've started working on the JAXB 2.1 maintenance review (I took over the spec work from Sekhar .) I'm still trying to get up to speed with the process and all, and I hate the UI of FrameMaker, but in the mean time, I posted all change proposals at java.net .
The idea of an MR is that we'd like to make selected easy changes to address the pain of users and technologies that build on top of the JAXB RI. In fact, many of the proposed changes are based on user feedbacks (such as #38, #144, #192, #201, and #216.) Some of those are also driven by JAX-WS (#38 and #201)
There are other changes that were considered, but some of those we had to abandon because it's too big for an MR. The top of the list is to better support interfaces, which has been a big pain. But we couldn't come up with a good solution, and any bandaid attempt would make it much complicated later when we address this problem "correctly."
I'll be posting more about some key highlights, but meanwhile you can read the change proposal attached to the issues. Similarly, if you have some pains in using JAXB, this is a good time to log that in the issue tracker. We will not be able to fix them all in an MR, but we'd like to hear from you.
Please feel free to vote on issues, attach your comments, or send some e-mails to email@example.com (you might have to request at least an observer role on the JAXB project to post comments on issues.)