• To: "'XML Developers List'" <xml-dev@l...>
• Subject: RE: A bunch of components, but no mandated organization - reasonable?
• From: "Roger L. Costello" <costello@m...>
• Date: Wed, 12 Jan 2005 14:40:54 -0500
• In-reply-to: <41E579A6.9090504@j...>
• Thread-index: AcT43L/xo4ItUWzcQaypFbAeCCjZbwAAMpTA

>I assume that this question has as its impetus ...

Here's my motivation for the question: in a large, complex Enterprise you
may know the kinds of "things" that need to be moved around (e.g., Book,
BookCover, etc) but you don't have a-priori knowledge of the specific
transactions that will be needed.  

So, is it feasible to simply declare a bunch of components (that everyone
understands), which may be dynamically assembled by one system and shipped
to another system where the assembly is dynamically understood.

/Roger

• Follow-Ups:
  • RE: A bunch of components, but no mandated organization- reasonable?
    • From: Dave Pawson <davep@d...>
  • RE: A bunch of components, but no mandated organization - reasonable?
    • From: "Michael Kay" <mike@s...>

• References:
  • Re: A bunch of components, but no mandated organization- reasonable?
    • From: Jeff Rafter <lists@j...>

• Prev by Date: Re: A bunch of components, but no mandated organization- reasonable?
• Next by Date: Re: A bunch of components, but no mandated organization - reasonable?
• Previous by thread: Re: A bunch of components, but no mandated organization- reasonable?
• Next by thread: RE: A bunch of components, but no mandated organization - reasonable?
• Index(es):
  • Date
  • Thread