Bit brutal there, Steve! Whole world of difference between "should" and "what is". I do understand what you are trying to convey and you are absolutely correct in that you can and are able to return complex XML types in WS-*. At the same time, given that WS-I punted on profiling XML Schema, Interop is not all sweetness and light given that various WS toolkits do not implement XML Schema in a complete or consistent manner. As such there are some XML schema artifacts that to not play nice across toolkits. There was a thread some time back on the SOAPBuilders list that I and some other familiar folks participated in, and took some notes on. You can find them @ http://www.aniltj.com/blog/2005/07/20/SOAPBuildersDiscussionSummaryOnWeb ServicesInteroperabilityIssuesMarch2005.aspx Also documented some issues with XML Schema to Object mappings @ http://www.aniltj.com/blog/2005/12/11/XMLSchemaToObjectMappingsIssuesAnd WorkArounds.aspx [May be a bit outdated at this time] Regards, - Anil
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Jones Sent: Wednesday, December 06, 2006 11:32 AM To: [email protected] Subject: Re: [service-orientated-architecture] Limitations of return type of a service 1) Service is a business concept So I'm assuming you are talking about WS-*. If you can't return complex XML schemas from your WS-* implementation then quite frankly its rubbish. There should be no limitations. Steve On 06/12/06, darlin' Viju <[EMAIL PROTECTED]> wrote: All, Is there any limitations for the return type of a service ? My understanding is the service should return only primitive types and objects which has primitive types as variables. This is to ensure that the service can be used across languages. Is this correct or is it like there is no limitation at all? Is it posible to return an xml from a service? Thanks, - d Vj <http://geo.yahoo.com/serv?s=97476590/grpId=9428360/grpspId=1705007181/m sgId=6635/stime=1165426199>
