I think that this item qualifies as struts material because affected
code originates in the Struts project. I am reasonably experienced
with Tomcat and Apache and am moving to use Struts.

I have a working Apache (1.3.19) installed by Mandrake 8.0 and a
current version of Tomcat 3.2.3 installed from the jakarta.apache.org
download site (binary not source). I am also using mod_jk.so from
the same source.

As I understand it, the WAR file is designed to allow you to install
a web application in a single location and (in he case of Tomcat)
restart the container to use the application.

I am working through the README and INSTALL documents that
were in the struts tarball and have successfully installed and run
the struts-documentation.war file. This appears to work correctly
on both Tomcat and Apache at:
       +  http://cpu1753.adsl.bellglobal.com/struts-documentation/
        + http://cpu1753.adsl.bellglobal.com:8080/struts-documentation/

When I move on to the struts-example.war file, I get an imlementation
which executes correctly on Tomcat, but does not properly map the
*do URI's of the control servlet when I run it through Apache.

I realize that the documentationn for installing struts is a bit 'rough'
but I feel that these WAR files should be usable out-of-the-box
and should not require elaborate sorcery to set up and run.

I am able to run the struts-example code if I change* the generated
mapping in /opt/jakarta-tomcat-3.2.3/conf/mod_jk.auto-conf:

The change was:

        JkMount /struts-example/servlet/* ajp12
    to
        JkMount /struts-example/* ajp12

Of course, the app still works in Tomcat because that configuration is
not affected by the contents of mod_jk.conf-auto.

Any suggestions ?

The working versions are:

       +  http://cpu1753.adsl.bellglobal.com/struts-example/
        + http://cpu1753.adsl.bellglobal.com:8080/struts-example/




* -  Yes, I know it will be rewritten.


----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 31, 2001 2:52 PM
Subject: Re: reloading config files


>
>
> Hi Chris,
>
> Reloading depends on your server, not on Struts!
>
> I believe that tomcat 4 reloads automatically, but I know there has been
some
> problems with it.  You might want to check that mailing list.
>
> Cheers,
>
> Dave
>
>
>
>
>
> Chris Heinemann <[EMAIL PROTECTED]> on
08/31/2001
> 09:23:14 AM
>
> Please respond to [EMAIL PROTECTED]
>
> To:   Struts User Group
<[EMAIL PROTECTED]>
> cc:    (bcc: David Hay/Lex/Lexmark)
> Subject:  reloading config files
>
>
>
> Hello everybody,
>
> I have just started with Struts and must say I am very impressed.  I
> know I don't have a right to complain because I haven't submitted any
> patches yet.  However, I do have one grip, when altering config files
> (such as struts-config.xml and ApplicationResources.properties) I need
> to restart tomcat.  Couldn't it reload if the files are newer than the
> last reload?  This would be very helpful in development.  It could be
> turned off in production via a init param.
>
> Thank you,
> Chris Heinemann
>
>
>
>
>
>
>
>

Reply via email to