Simon, Thanks. How are you handling replyTo destinations? Since jms:address gives no way to specify the replyTo destination, it seems like one is forced to rely on some standard or convention to know where the web service will send responses.
-- Mark > -----Original Message----- > From: Simon Solomon [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 27, 2004 3:55 PM > To: [EMAIL PROTECTED] > Subject: Re: SOAP over JMS > > > > > > > Hi, > > I have been using WSIF's SOAP over JMS provider successfully > for a while > now. > You can look at the attached sample wsdl that has Soap over > Jms binding. > > Even though wsif provided an Axis transport for jms ( > org.apache.wsif.providers.soap.apacheaxis.WSIFJmsSender), > I did create a custom Axis transport class that handles the jms > read/writes. > > Sample WSDL > (See attached file: JmsPutGet.wsdl) > > Hope this helps, > > Simon Solomon > [EMAIL PROTECTED] > > > > > > "Mark D. Hansen" > > <[EMAIL PROTECTED] > > om> > To > "WSIF (E-mail)" > > 04/27/2004 03:37 > <[EMAIL PROTECTED]> > PM > cc > > > > Subject > Please respond to SOAP over JMS > > [EMAIL PROTECTED] > > he.org > > > > > > > > > > > > > > Can I use WSIF if I always want to use SOAP for my messaging > protocol, but > want to use different transports? E.g., SOAP over HTTP, SOAP > over JMS, > SOAP over SMTP. > > I have a feeling that the answer is "Yes", but in the WSIF > samples, the JMS > example seems to be for the "native binding" approach - not > using SOAP, but > instead a WSDL extension binding input/output directly to JMS > messages. > I'm interested in the simpler case where you simply wrap SOAP in a JMS > TextMessage and invoke normal SOAP-style web services, but use a > JMS-provider as transport. > > Any ideas about this? Is anyone still working on WSIF or has > something > else superceded it? > > Thanks, > > Mark >
