As I spend more time studying the two packages, I am beginning to see some areas where Axis is more mature. a) The ant tasks are real ant tasks not system calls to an external executable. b) There are a couple tools with GUI interfaces that are not provided with JWSDP. c) Axis is supported by xdoclet.
I am new to JAX-RPC and found the documentation shipped with JWSDP better suited for a beginner. I found it strange that although both packages implement JAX-RPC the examples given in the respective documentation are quite different. It wasn't until I took some time to review the actual JAX-RPC specification that I understood the differences between the respective examples. I slowly came to understand that they were interchangeable except in the areas of object creation. If I understand things correctly, the JAX-RPC specification is rather loose in several areas and one can't switch implementations without a slight amount of code tweaking. I was surprised by this, since I initially expected the examples to be almost identical (aside from the aspects particular to the example problems choosen). ----- Original Message ----- From: "Mark D. Hansen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 29, 2003 6:52 AM Subject: RE: JWSDP 1.2 vs Axis I found some bugs in the JWSDP 1.2 implementation of JAXRPC. For example: >Oneway operations are not supported for a doc/lit WSDL when using >dynamic proxy client. This will be fixed in the next version of JWSDP >expected to release later this year. On the other hand, the Axis implementation of JAXRPC isn't perfect either. I've been having problems with the Call.invokeOneWay( ... ) method. See the [EMAIL PROTECTED] email archives for other discussions about JAXRPC issues in the 1.2 release. After spending a couple weeks with the JWSDP, I switched to Axis, but for a narrow set of reasons related to the JAXRPC implementation in JWSDP. Note that the current JWSDP is still "early access" - with the final promised in October. I've been told by Sun that the problems I was having will be fixed in the October release. Hope that helps, Mark > -----Original Message----- > From: gawkboyrules [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 5:01 PM > To: [EMAIL PROTECTED] > Subject: JWSDP 1.2 vs Axis > > > I have been looking into the various potential solutions for > accessing a > SOAP service in Java. So far I have not been able to discern > whether Sun's > Java Web Services Developer Pack v.1.2 is preferable to Axis. > > Apparently version 1.2 of JWSDP was released on June 7, 2003. I have > discerned from various newsgroup postings that Axis is > somewhat better than > the older versions of JWSDP. What is not obvious is how the > newest 1.2 > release of JWSDP stacks up to Axis. > > To further confuse the issue, it is apparent that the JAX-RPC > implementation > shipped by Sun (in JWSDP) is intended not only as a reference > implementation > but also for production use. > It may be worth mentioning that I am currently coding in Eclipse but > performing external builds with Ant. I am also currently > making use of the > catalina release of tomcat although I may use a different > container for > production. > > Generally speaking I prefer to use a truly open-source > solution, but as a > practical matter from a user's standpoint the differences > between the Sun > open-source license and a true open source license is > somewhat academic. > The real business need is generally to find something > economical (i.e. free) > that isn't going to disappear anytime soon and is mature. I > simply want to > choose the technically best open-source or almost open-source > solution that > appears most likely to be the preferred solution by most > other developers in > the future. (If I was leading an open source project I would > insist on a > GPL or BSD style license but that's a whole different conversation.) > > Any information that helps me to decide which solution to > choose will be > appreciated. >
