Eric, The IONA XMLBus implements JAXM and SOAP with Attachments and has been used by Microsoft as the reference implementation for .NET interoperability. The next drop of the XMLBus Technology Preview (Preview of functionality that is productized by IONA Orbix E2A platform) will be on XMLBus.com this monday. It will have a complete implementation of JAXM v1.0. The current shipping version is based on a draft spec of JAXM. We have used this implementation for ebXML TRP v1.0 as well.
becky -----Original Message----- From: Dahnke, Eric [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 6:15 PM To: '[EMAIL PROTECTED]' Subject: RE: RPC Vs Messaging We're using the JAXM package to generate SOAP Messages with code out of the JAXM package. And I've been told one can (will be able to) use JAXM with Axis. Something like the following. MessageFactory mf = MessageFactory.newInstance(); SOAPMessage msg = mf.createMessage(); SOAPPart sp = msg.getSOAPPart(); SOAPEnvelope envelope = sp.getEnvelope(true); SOAPHeader hdr = envelope.getHeader(); SOAPBody bdy = envelope.getBody(); ... SOAPMessage reply = con.call(msg, urlEndpoint); For our needs we haven't needed RPC over soap yet, and have just needed to pass around SOAP messages w/ attachments. I'm sure the RPC side is equally distinct, and SOAP seems very flexible. I'm always hearing people talking about passing entire messages as Strings or doing this or that via messaging and or rpc. - HTH -----Original Message----- From: Krishnamurthy, Ramanathan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 5:43 PM To: '[EMAIL PROTECTED]' Subject: RPC Vs Messaging Is this distinction necessary ? Isn't messaging a special case of RPC. I recently moved from SOAP_2_2 to Axis. And axis doesn't seem to differentiate the two. Thanks for any insight. ram ---------------------------------------------------------------------------- ------------ Ramanathan Krishnamurthy AP Engines, Inc. Five Clock Tower Place, Suite 250 Maynard, MA 01754
