|
I can't comment on #2, but I will
say that in regards to #1, I found Axis much easier to use, configure, and get
help on. I also had a problem with the JWSDP wsdl2java tool. It had a problem
with the WSDL that a customer had generated. I got nowhere when approaching Sun
about the issue. I did not have the problem with Axis or a few other toolkits
that I tried at the time. Peter -----Original Message----- Thanks for
responding. I'd like to know: (1) Generally speaking,
do you find AXIS easier to use, better documented, and less buggy than JWSDP? (2) Specifically, I'm
trying to use JAX-RPC as a platform to develop a simple messaging
framework. JAXM would actually be better suited to my purposes, but I
can't use JAXM because I need to use official J2EE technology. I
discovered that the current JAXRPC RI doesn't support dynamic proxy for
oneway doc/lit - so it can't be used to develop my messaging framework.
Does AXIS 1.1 support dynamic proxy for oneway doc/lit?
**************************************************************************** This email may contain confidential *************************************************************************** |
Title: RE: need an alternative to Sun's JAX-RPC RI in JWSDP 1.2
- need an alternative to Sun's JAX-RPC RI in JWSDP 1.2 Mark D. Hansen
- RE: need an alternative to Sun's JAX-RPC RI in JWSD... Volkmann, Mark
- RE: need an alternative to Sun's JAX-RPC RI in JWSD... Mark D. Hansen
- RE: need an alternative to Sun's JAX-RPC RI in JWSD... Pascale, Peter H.
- RE: need an alternative to Sun's JAX-RPC RI in JWSD... Brain, Jim
- RE: need an alternative to Sun's JAX-RPC RI in JWSD... Volkmann, Mark
