On 2/6/2001 at 4:32 AM Josh wrote:
>Before I went ahead and started implementing this approach I wanted to
know if there had been any more recent successful attempts.
This was just added to the installation page for 1.0. The instructions
were posted for this purpose by one user, and confirmed by another. If
these don't work for you, please let us know.
Next on the agenda is something for JRun and Websphere. Any suggestions
from people using those products? (In a format we can paste into the
documentation.)
WEBLOGIC 5.1 (service pack 8)
-----------------------------
* Obtain and install the Xerces XML parser (problems have been reported
with the Sun reference implementation). Put xerces.jar in your
WebLogic system
path.
* Obtain and unpack the Struts binary distribution (this procedure
assumes
it was extracted to C:\jakarta-struts).
* Add an entry to weblogic.properties for each of the Struts web
applications that you would like to configure. For example, to make
the
struts-example application available, add the following line to
weblogic.properties:
weblogic.httpd.webApp.strutsexample=c:/jakarta-struts/webapps/struts-ex
ample.war
* You do not need to include struts.jar or any of the application
specific
classes in the WebLogic classpath, since this will be done
automatically
(unless deploying an unpacked web archive- see below).
* Start WebLogic server and point your web browser to the struts
application. For example, to connect to the example application added
in
step 3:
http://localhost:7001/strutsexample
* This example application depends on the Struts specific resource file
ApplicationResources.properties to be present on the classpath.
However,
WebLogic only extracts *.class files from the archive so this file
will not
be found, resulting in an error the first time it is needed-
something
similar to: javax.servlet.ServletException: runtime failure in custom
tag
'message'. Steps 6 & 7 will need to be performed for this
application, and
any other that relies on ApplicationResources.properties.
* Extract ApplicationResources.properties from the *.war file, and
manually copy it to the respective package in the _tmp_war_ directory
WebLogic created for this application. Again referring to the
struts-example
application, this would be:
c:\jakarta-struts\webapps\WEB-INF\_tmp_war_strutsexample
* Restart WebLogic. You will now be able to run the application:
http://localhost:7001/strutsexample
* The above steps should be followed for applications deployed as *.war
files. For unpacked web applications, configuration involves adding
both
struts.jar and /WEB-INF/classes to the WebLogic classpath. For this
reason,
I would suggest deploying applications as war files to WebLogic.
However,
the same example application can be successfully deployed in
extracted
format by modifying weblogic.properties (assuming the war was
extracted to
directory webapps/struts-example):
weblogic.httpd.webApp.strutsexample=c:/jakarta-struts/webapps/struts-ex
ample/
And starting WebLogic with the updated WebLogic classpath. For
example:
c:\jdk1.3\bin\java -ms16m -mx64m
-classpath c:\weblogic\lib\weblogic510sp8boot.jar;
c:\weblogic\classes\boot;
c:\xerces\xerces.jar
-Dweblogic.class.path=c:\weblogic\lib\weblogic510sp8.jar;
c:\weblogic\license;
c:\weblogic\classes;
c:\weblogic\myserver\serverclasses;
c:\weblogic\lib\weblogicaux.jar;
c:\jakarta-struts\lib\struts.jar;
c:\jakarta-struts\webapps\struts-example\WEB-INF\classes
-Dweblogic.system.home=c:\weblogic-Djava.security.manager
-Djava.security.policy=c:\weblogic\weblogic.policyweblogic.Server
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/about/struts/
