Hi Angel,
I'd say that the nice thing about message-oriented web services is that it decouples your over-the-wire representation from your actual data structures. Sometimes those messages will actually be processed as XML, or converted to object and run through a processing pipeline; othertimes they'll be mapped to simple method calls (often in the form of EJB methods). JibxSoap is actually designed to support this, as I outlined in my response to Tim. It already implements the handler you described, dispatching on the basis of the type of object that matches the XML payload of a request; the only part that's missing is wrapping and unwrapping the parameter to a call.
Note that if you do this wrapped-type of approach you can still control the XML representation for any complex structures you're passing; the wrapping just takes care of top-level simple parameters in an automatic way.
- Dennis
???e??? ?a???t?a??? wrote:
The whole point of using a message-oriented approach is not having to expose your complete interface method-by-method to the outside world.
What you need to do is build a single handler for all incoming messages, and then check out the mesage parameters to forward the request to the appropriate internal handler. Then, pass the response back, and send it on it's way ...
O:]
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ jibx-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jibx-users
