I'm working on a project where we seem to be developing an extremely
XML-oriented enterprise application. The application is very
document-centric, and the various requirements for customizability are
pushing us towards heavy use of XML DOMs and XSLT transformations, not
just as an external communications format, but as tools for defining
the guts of the system. We have XML-based data (as a large XML DOM in
memory, not as a big XML text file), XML-based permissions, XML-based
workflow customization, etc.
I'm not unhappy with this direction - it seems to make a lot of sense
and it seems to fit our requirements. However, it's throwing me a bit
off; I'm having trouble fitting it into the normal J2EE approach. The
further we go, the more I begin to suspect EJBs aren't appropriate at
all.
One thought we've had is to use EJBs to manage caching the large DOM
structure, but I'm not entirely sure how well they'll be suited to
this.
Has anybody done something in this vein, or does anybody know of any
research, papers, white papers, good books, products, etc, that would
apply to this?
Steven J. Owens
[EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
