If you read the JAXM 1.1 specification (e.g. ftp://128.11.159.146/pub/spec/jaxm/ahasdjfiyu44/jaxm-1_1-spec.pdf), you will see that the only required transport is HTTP, since JAXM requires support for SOAP 1.1 and SOAP Attachments, and SOAP 1.1 specifies an HTTP binding. The JAXM spec does reference MOM in general and JMS in particular, but with statements like
>>>> a given JAXM provider may choose to transport SOAP messages over a MOM infrastructure. This is an implementation detail that is completely invisible to the application, and it does not in any way transform a JAXM application into a MOM application. <<<< So, JMS support is an option with JAXM, not a requirement. More importantly, Apache SOAP does not implement JAXM. Apache Axis does implement JAXM, and I believe it supports JMS as a transport. It is still in beta, but it is a product you can work with. You may also want to look into Sun's Java Web Services Developer Pack (http://java.sun.com/webservices/downloads/webservicespack.html). Scott Nichol ----- Original Message ----- From: "Bhushan Dongare" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 30, 2002 1:57 AM Subject: RE: I repeat--- Help ??? JMS SOAP please go through JAXM specifications -----Original Message----- From: Vaibhav Joshi [mailto:[EMAIL PROTECTED]] Sent: Friday, August 30, 2002 1:06 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Scott Nichol' Subject: I repeat--- Help ??? JMS SOAP Hi, Does SOAP support asynchronous messaging ..for eg. JMS and if yes How???? -v -- 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
