David,
Thanks for the query... If you have a chance to take a look at
the article on migrating the BEA webapp.cookie war to Lutris
EAS 4, you'll see that the _only_ issue was that the BEA web.xml
file's DTD reference is inconsistent. Lutris EAS 4 caught that, so the engineer
replaced the WebLogic DTD reference (Web Application 1.2 with 2.2, which
is consistent with the web-app_2_2.dtd name).
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
1.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
with
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
and everything ran fine.
The topic of version control is huge in issue of standard J2EE platforms.
Also, J2EE does not address a lot of the implementation details that have a
direct impact on application portability, particularly in the area of RMI.
Also... a lot of J2EE app servers now support Xerces, Xalan, etc..., which
are not part of the J2EE standard. Therefore, if you are using SAX, XSLT
in your WAR, you may/will have the issue of which version of the libraries
does your target J2EE platform support.
David
David Thatcher wrote:
> > Behalf Of David H. Young
> > Sent: Sunday, August 05, 2001 10:15 PM
> > To: [log in to unmask]
> > Subject: [HP3000-L] ANN: Lutris Enhydra Journal (August Issue)
> >
> >
> > *** Lutris Enhydra Journal
> > *** August 2001 Issue now available
> > *** Free On-Line Publication
> > *** http://custportal.lutris.com/customer/journal.html to register
> >
> > This issue celebrates the release of the Early Access
> > version of Lutris EAS 4, featuring support for the J2EE APIs
> > implemented as individual services in the new Services Architecture.
> >
> > In addition to the articles below, be sure to check out the
> > EnhydraME announcement for supporting mobile and micro device
> > development with Enhydra.
> >
> > Articles:
> > - Introducing Lutris EAS and the Services Architecture
> > - Lutris EAS Services Architecture Classloader
> > - Migrating a BEA WAR to Lutris EAS
>
> David,
>
> Why would you need to convert Web Application Archive (WAR) files if Enhydra
> was J2EE compliant???
>
> I can create an application using WAR on any J2EE compliant server and
> distribute the application to any of the following servers without the
> effort of migrating...
>
> BEA's WebLogic
> IBM's WebSphere
> HP's Bluestone
> Oracle's OC4J
> SAP's IN-Q-MY
> Evermind Orion
>
> J2EE is a Vendor-neutral standard. For those interested in the J2EE
> specification: http://java.sun.com/j2ee/blueprints/
>
> David Thatcher
> Advanced Network System, Inc.
> http://www.advnetsys.com
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
--
David H. Young
Chief Evangelist
Lutris Technologies, Inc.
1200 Pacific Avenue, Suite 300
Santa Cruz, CA 95060 USA
831.460.7310; 831.471.9754 (fax)
http://www.lutris.com
http://www.enhydra.org
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
