IMHO, Axis should provide nothing more than the foundation
(SOAP+JAX-RPC+SAAJ). JSR172, WS-*, and other things should be kept out as
separate subprojects. Personally, I'd like to see us start to explore
feature requirements for a 2.0 workstream. A few items I see in
particular:
1. Architecture cleanup. I'm not talking a complete revamp like we saw
SOAP-->Axis, just a cleanup of many of the architectural elements such as
the handler framework, WSDL2Java/Java2WSDL pluggability, asynchronous
operation, etc.
2. SOAP 1.2 support, including support for pluggable SOAP 1.2 Feature
implementations (e.g. it should be possible to build something like
WS-ReliableMessaging support into a module that can be plugged into Axis
so that services are automatically capable of using it)
3. JAX-RPC and SAAJ of course
4. Better integration of WSIF as a programming interface for Axis (as an
alternative to JAX-RPC when a more WSDL-based view is necessary). This
would include a converged WSIF/Axis message model
5. A cleaner separation between runtime components and development
components (e.g. the WSDL code could be separated out into a separate jar
and made optional.)
6. An improved XSD Parser
7. Autodetected Plugin based deployment of handlers, providers, etc. It
should be possible to drop a jar file containing Axis component
implementations into the classpath and have Axis automatically detect and
deploy them.
8. WSDL 1.2 support
Keep in mind... I'm saying that we should start to *explore* the feature
requirements... I'm not saying that we should start to design or implement
2.0 yet.
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(877) 511-5082 (voice/fax) ** NEW NUMBER **
(700) 930-1979 (t/l) ** NEW NUMBER **
Programming Web Services With SOAP
O'Reilly & Associates, ISBN 0596000952
Have I not commanded you? Be strong and courageous.
Do not be terrified, do not be discouraged, for the Lord your
God will be with you whereever you go. - Joshua 1:9
Davanum Srinivas <[EMAIL PROTECTED]>
03/14/2003 09:33 AM
Please respond to axis-dev
To
[EMAIL PROTECTED], [EMAIL PROTECTED]
cc
bcc
Subject
Re: Axis Build System - Possible conversion to Maven
Dan, Folks,
Here's what i see coming up for Axis..
- JAXRPC 1.1
- SAAJ 1.2
- SOAP 1.2
- WSDL 1.2 (2.0?)
- JSR 172 (J2ME Web Services Specification)?
- WS-* specifications?
- Anything else?
My feeling is that we should target the first 3 for Axis 1.2 release
Thanks,
dims
--- Dan Diephouse <[EMAIL PROTECTED]> wrote:
> May I ask the unanswerable question: when will the 2.x stream start? :)
>
> More specifically, is 1.2 going to be the last one in the 1.x stream? On
> previous experience I would say that this is going to be released in the
next
> two months, but I could be wrong.
>
> - Dan
>
> James M Snell wrote:
> > For the Axis 1.x workstream, I'd say -1 to this. As Axis 1.x is a
> > released product, I am very reluctant to change a process that already
> > works. It may not be 100% ideal but that's the nature of the OSS
beast.
> > It works.
> >
> > When the Axis 2.x workstream launches, I'd say we can revisit this
> > question and see what makes the most sense based on the merits of the
> > individual technologies.
> >
> > - James Snell
> > IBM Emerging Technologies
> > [EMAIL PROTECTED]
> > (877) 511-5082 (voice/fax) ** NEW NUMBER **
> > (700) 930-1979 (t/l) ** NEW NUMBER **
> > Programming Web Services With SOAP
> > O'Reilly & Associates, ISBN 0596000952
> >
> > Have I not commanded you? Be strong and courageous.
> > Do not be terrified, do not be discouraged, for the Lord your
> > God will be with you whereever you go. - Joshua 1:9
> >
> >
> >
>
> --
> Dan Diephouse
> http://junktoast.com
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com
