On Dec 9, 2007 1:45 PM, Stevan Camp <[EMAIL PROTECTED]> wrote: > Hello, > > I'm new to Tuscany and wondered if anyoen out there was able to offer me > some help. > > I have a non-SCA service which operates with two JMS queues, one being > request and one being response. They follow the usual pattern: > > * Client sends a request message to the Service by posting a message on > teh > req queue. > * Service picks up message, takes some action and returns a response > message > back to the client via the response queue. > > I'd like to construct an SCA service to proxy/masquerade this operation, > so > that: > > * SCA Client calls an operation on the SCA Service > * SCA Service posts a suitable JMS message to the req queue > * SCA Service listens to the Response queue or a MDB notifies the SCA > service once a response is received > * SCA Service makes a callback to the client with the result of the JMS > response. > > Does any of this make sense, is it do-able? > > Is anyone able to offer me any help on this one, havent found a suitable > example yet, other than some refs in the SCA JMS Binding spec, which I > couldn't quite translate into a service. > > I'm sorry if any of this is not quite right... I'm still trying to find my > > feet in the Tuscany/SCA world. > > Stevan. >
You can do that with Tuscany using the Tuscany JMS binding. The JMS binding is a partial implementation of the SCA JMS binding spec ( http://www.osoa.org/download/attachments/35/SCA_JMSBinding_V100.pdf), but the code has been a little neglected for a while so is a bit rough and didn't make it into an official Tuscany release yet, so right now you'd have to build it yourself. Coincidentally I'm right now working on fixing up this to make it more usable, spec compliant, and in a state we can include it in the next Tuscany release. Be really helpful if you could try it out as I do this to give feed back on if it does what you need or not. One question I have right away is what type of JMS messages do you need and whats the type of contents of those messages? Right now the code just supports JMS object messages, but the JMS binding spec says by default it should use JMS text messages with the payload being XML, see section 1.5.2on page 5 of the spec. What do you need for this to work with your existing application queues? ...ant
