We have been deploying our apps as servlets for the past 2+ years. We
started using the SSDD target but found it lacking. The biggest hassle we
found was the SSDD didn¹t seem to include everything we needed. One of the
only limitations I have come across is that the resulting WAR file can be
run without having the container expand it first (which is the default
behavior for Tomcat but not WebLogic see below for the reason). Our apps
get built using the following steps:
1. Build the frameworks using <wocompile> and <woframework>
2. Build the applications using <wocompile> and <woapplication>
3. Assemble the web applications manually instead of using the supplied SSDD
target. Our final deployment includes the following structure:
WEB-INF
classes
Library
Frameworks
OurFoundation.framework
OurModel.framework
OurServices.framework
JavaEOAccess.framework
JavaEOControl.framework
JavaFoundation.framework
JavaJDBCAdaptor.framework
JavaWebObjects.framework
JavaWebServicesClient.framework (if needed)
JavaWebServicesSupport.framework (if needed)
JavaWOExtensions.framework (if needed)
JavaWOJSPServlet.framework
JavaXML.framework
lib
<any non WO jars needed JDBC Drivers, XML parsers,
mail.jar, etc>
web.xml (Need to make sure that the WOClasspath context
parameter includes all of the WO frameworks listed above plus your
application frameworks. There is an environment variable WEBINFROOT that
gets resolved at runtime to the path where the WEB-INF folder is located.
This is the primary reason that the WAR file must be expanded in order to
run properly.
4. After the web app is assembled it is WARed using the ant <jar> task.
Hope this helps others.
--
Dov Rosenberg
Conviveon/Inquira
Knowledge Management Experts
http://www.conviveon.com
http://www.inquira.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
