Anne Thomas Manes wrote:
> Great article, Dennis. I agree with your recommendation that schema
> designers should try to avoid using XSD data types that don't match up
> well with Java and .NET datatypes (and vice versa). But I have another
> recommendation: if the situation allows it (i.e., if the complexity of
> the process doesn't require complex object graphs and algorithms) just
> don't use a compiled OO programming language and avoid the whole
> XML/object impedance mismatch. Use XQuery or a scripting language
> instead.
>
> I know. It's a radical idea.
Anne, are you suggesting that the software programming language choice is the
answer? What's more important from your perspective? Reuse, portability of
execution, inter-working of data flow, speed of development, or something else?
How would you rank these kinds of considerations in your choice of a
programming
language/environment/platform?
Gregg Wonderly
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[email protected]
mailto:[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
