Hello:
XML is a critical part of the "normal" J2EE approach. Sun has
strongly committed to XML, as evident by the Sun XML Java components
(parsers, etc.) as well as the heavy use of XML for specifying EJB
deployment and other deployment parameters.
It's easy to get carried away with certain technologies because
they're the "standard" way, but it's important to remember that J2EE
contains a whole suite of technologies that may or may not be useful.
EJB has a specific purpose: handling complex business logic
persistent in a database in those cases with wide-scale distribution
needs, extreme scalability, and object/database flexibility. This is
a pretty restricted set of needs, and I wouldn't feel coerced to meet
those needs if your project doesn't require them.
An enterprise application utilitizing a lot of XML is itself most
likely a J2EE application. If you store the XML in a database, you'll
probably be using JDBC (effectively a J2EE technology). If it's
web-based, you may be using servlets (J2EE) with or without JSP
(J2EE), etc. etc. EJBs are designed for a specific purpose, and
should be avoided if you don't need them.
Regards,
Ben Flaumenhaft
At 4:33 PM -0500 1/7/01, Steven Owens wrote:
>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".
===========================================================================
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".
