Dan, I am of multiple minds whether the JS stuff is done enough for 2.1. It hasn't attracted a giant audience, and some of the other things I'd add to it would really like to have some substrate for easier annotation support in place first. On balance, we could call it cooked for 2.1.
I am also responsible for some Aegis things that may or may not be the source of trouble and distress, such as the MTOM changes that I made. I think I at least need to make some of them controllable. --benson On Feb 13, 2008 4:15 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > Could everyone that has been working on 2.1items please check JIRA and > update/resolve any items? > > We still have 55 open 2.1 issues and 11 2.0.5 issues so it LOOKS like we > still have a ton of work to do. However, we're now passing the JAX-WS > 2.1 TCK (except for a couple challenged tests that we're waiting for > responses from Sun) so I'm going to assume, at the very least, a bunch > of the 2.1 related tasks are complete. > > I've gone ahead and create a 2.1.1 version number in Jira. If you're > sure something won't get done for 2.1 but is pretty important to get in > shortly thereafter, go ahead and assign it to that version. > > Thanks! > -- > J. Daniel Kulp > Principal Engineer, IONA > [EMAIL PROTECTED] > http://www.dankulp.com/blog >
