WebObjects, EOModels, and EAI
WebObjects, EOModels, and EAI
- Subject: WebObjects, EOModels, and EAI
- From: Clark Mueller <email@hidden>
- Date: Sat, 1 Oct 2005 13:15:11 -0600
Hello all,
I am curious as to some of the suggested means of approaching the
particular task I am currently tinkering with. In a nutshell, I'm
attempting to design something that presents complete and total
modularity amongst itself. As I see it, my requirements are something
like the following:
- Complete modularity; any new module can be developed on the basis
- A message bus should be used; the bus would probably be written in WO.
- Compatibility among many programming languages should be supported
by the design (although an API for individual programming languages
would be acceptable); the architecture should not be *specific* to
Java or WebObjects.
- I'd like to not sacrifice the elegance of Enterprise Objects and
its relationships - between the models - if possible.
The last point above is what I view as the biggest obstacle to what I
actually want to do. The premise behind the architecture I'm trying
to build is that I should be able to swap out different modules to
build a custom system as the situation dictates. For example, to
build a complete POS, I would put together a customer, invoicing,
accounting, and inventory module. Theoretically, each should be
capable of interacting with one another as if you entered them all
into one EOModel. However, I would like to separate them for
extensibility (suppose I later want to build a work order system that
does no accounting, for example; I can drop the accounting module and
insert one to manage work orders).
Now, in the interest of preserving the power of Enterprise Objects,
I'd really, really like to be able to separate these things, but
retain a relationship between modules' EOModels as appropriate.
Naturally, the main obstacle to this as I see it is preserving
compatibility with non-Java modules (via web services, or something
like that).
I'm reasonably familiar with the mechanics of integrating systems,
and the means used, and the theory behind it. I've also had some
limited experience with actually integrating systems, but only in
*specific* environments. The other thing that is unique about what I
am trying to build now is that I don't want to tie it down to
building the EAI for a specific environment and specific existing
applications; I'd like to make it somewhat generic.
So, I am kind of at a loss as to exactly how I might proceed. Can
anyone give me a bit of insight? Am I SOL when it comes to preserving
EO among modules with this design?
Thanks,
Clark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden