Thanks Deepal for narrowing the list down here. I just wanted to add a few
things.
In response to Amila's comment:
> Do we have to run any standard test suite to claim the compliance? I mean
for JAXWS we have to pass the SUNs' TCK.?
Yes, someone with access to the Apache CTS buckets will need to run the
JAXWS TCK. I'm not familiar with what the access restrictions are on this
though. Is anyone aware of how this process works within Apache?
Regardless, I believe the suite must be run by someone not working on the
code.
> On Dec 19, 2007 12:02 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> > Hi Devs and Users,
> >
> > I saw a number of users asking about the next release of Axis2 , so I
...
> > doing a release on end of February ?
> >
> > So in the release I would like to see following list of items
> > - Support for RPC-Encoded
> > - Full support for JAX-WS
> > - Enhance NIO transport support
> > - Discuss and implement dynamic phase rule support
> > - Fix the issues we found at MS PlugFest
> > - Anything else ..... ??
> >
I want to clarify the second item here, Full support for JAX-WS. Beyond
getting the TCK running and complete, what is your expectation for this
work? I would anticipate this to include a better integration of JAX-WS
into the Axis2 deployment model. A preliminary description of this is
included AXIS2-3223. There's work that could be done to further simplify
things after this is complete, but what's described in that JIRA is the
first step.
Also, I'd like to add Java 6 tolerance (at least for JAX-WS) to the list.
As of today, there are compile errors when running with a Java 6 JDK. I
think we can include Java 6 support first for JAX-WS Apps and can consider
extending that to the other programming models if others feel an immediate
need. I've opened JIRA AXIS2-3425 (
https://issues.apache.org/jira/browse/AXIS2-3425) with more information..
Thanks,
-Nick
