> -----Original Message----- > From: Mark Bradley [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 14, 2002 4:12 PM > To: [EMAIL PROTECTED] > Subject: newbie questions > > > Hello, > > I've a few simple newbie questions regarding Apache SOAP. If someone > could answer them then it would really make my day! > > 1) My understanding is that Apache SOAP can parse strings into their > appropriate simple data types wheres JAXM cannot do this. I mean, if I > don't want to manually parse simple data types from strings then > Apache SOAP is my only choice. Do I understand correctly? >
Mark, JAXM is an XML-oriented SOAP API. It assumes that the application is working with XML data, therefore it lets the application perform the data translation. The JAX-RPC API is the standard Java API that you would want to use if you would rather have your SOAP implementation perform the Java to XML data translations. There are more than two dozen SOAP implementations for Java. The JAXM and JAX-RPC APIs are relatively new, so only a few of them support these APIs. (They use proprietary APIs instead.) Most SOAP implementations support both XML- and Java-oriented APIs. Sun's reference implementations for JAXM and JAX-RPC are a little different, since they are reference implementations rather than products. Apache SOAP was the first SOAP implementation. It predates WSDL and the Java APIs, and it's architecture makes it difficult to extend and enhance. 20 month ago the developers on this project elected to start a new SOAP implementation called Axis rather than trying to reengineer this implementation. Axis supports the JAX-RPC API. If you're just starting out, I'd recommend that you use Axis rather than Apache SOAP. But as I said, there are more than two dozen different SOAP implementations to choose from. Almost all of them supply a Java-oriented API that looks and feels like RMI, and they automatically transform Java into XML and XML into Java for you. Here's a quick list: - Apache SOAP (older implementation - only one that doesn't support WSDL) - Apache Axis (new implementation - supports WSDL and JAX-RPC) - Sun JAX-RPC reference implementation - Systinet WASP (supports JAX-RPC and JAXM) - Novell JBroker Web (supports JAX-RPC) - IBM WSTK (based on Axis, supports JAX-RPC)) - IONA XMLbus (supports JAXM) - The Mind Electric GLUE - Cape Clear Cape Connect - XSOAP - Spheon JSOAP - DevelopMentor SOAP - BEA WebLogic Workshop - SOAPwiz (plug-in for JBuilder 4) - Killdara Vitiris (for embedded applications) - eSOAP (client only, for embedded applications) - Wingfoot SOAP (client only, for embedded applications) - kSOAP (for the KVM) Most J2EE app server providers also provide SOAP support in their products: BEA WebLogic Server, IBM WebSphere, Oracle Application Server, Marcomedia JRun, Borland Application Server, etc. > 2) I am interested in getting Apache SOAP to work only for the > parsing aspect of it. That is, I would like to create my own Servlet > which grabs the HTTP Response itself and then passes it to Apache > SOAP to parse. I assume this must be possible in Apache SOAP, but > could someone give me a general outline of how it is done? > I think you'll find it easier to use Axis for this purpose. The code is much more modular than Apache SOAP. > thanks, > Mark. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
