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?
-----Original Message-----
From: Volkmann, Mark [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 9:15 AM
To: '[EMAIL PROTECTED]'
Subject: RE: need an alternative to Sun's JAX-RPC RI in JWSDP 1.2I have worked with both Axis and JWSDP. What do you want to know?
> -----Original Message-----
> From: Mark D. Hansen [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 22, 2003 8:44 PM
> To: AXIS Users (E-mail 2)
> Subject: need an alternative to Sun's JAX-RPC RI in JWSDP 1.2
>
>
> I'm pulling my hair out trying to work with Sun's JAX-RPC RI
> - particularly the wscompile tool. Am I just dense or is it
> hard to work with?
>
> Will I be any happier switching over to Axis? Has anybody on
> this list worked with both?
>
> Thanks,
>
> Mark
>
***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************
