This is the really hard decision in my case. I've read plenty of articles supporting the use of only doc/lit, some supporting use of RPC, some "wrapped"....
The way I see it, each type of service has it's place and it's pros and cons. I don't really understand why you should ALWAYS use doc/lit. My service is not document based, it is RPC based request/response, like calling an add() method. doc/lit is for document based services, rpc/lit for rpc based services. This is also how it's generally explained in documentation from Sun. I think that for my implementation, using doc/lit adds unnecessary complexity to the interface usage and implementation, so I'd prefer to use RPC. Even MS who only supports doc/lit uses "wrapped" style to expose an RPC interface to their doc/lit service implementation! Of course this currently conflicts with MS who currently don't support rpc/lit. However, if they will support it in future releases (which should be available by the time my product is out there), then maybe I'll use RPC after all. Finally, I have one other concern with doc/lit: A doc/lit SOAP request doesn't contain the method name (unless it is wrapped style), so this makes it impossible to have multiple methods in your interface with the same set of parameters doesn't it? I read about this in an article, haven't tried it yet, but it makes sense. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875418#3875418 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875418 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
