A colleague and myself have been trying to bridge his world of XML schemas, coming from a database modeling background, and my world of Web Services, and it hasn’t been easy. Where things break down are where we start to discuss mapping XML Schema back to a Java or C# class model. I’ll admit that the problems go away if we implement web services using what I term a schema-oriented development environment, typically associated with the BPM space.
It appears to me that there are approaches to XML Schema design that will make a mapping to a class model easy, and there are approaches that will make things difficult. I haven’t seen any such list documented, however. A decision that will need to be made is whether or not I should expect developers to begin from a method that looks something like:
XMLDocument myServiceCall(XMLDocument request)
or whether it’s realistic to map XML Schema types to a class hierarchy, letting developers work with something that will be a bit more familiar.
Thoughts? Any pointers to some good guidance in this space? Thanks-
Todd Biske
Software Infrastructure Engineering
A.G. Edwards Technology Group, Inc.
V:(314) 955-6254 F:(314) 955-4055 E:[EMAIL PROTECTED]
-------------------------------------------------------------------------------------
A.G. Edwards & Sons' outgoing and incoming e-mails are electronically
archived and subject to review and/or disclosure to someone other
than the recipient.
-------------------------------------------------------------------------------------
| Service-oriented architecture | Computer monitoring software | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
