Re: New context in server.xml prevents war unpacking (TC 4.1.12)

[Celia Wu]

Please remove my name from your email list.
- Original Message -
From: Jacob Kjome
Sent: Thursday, October 24, 2002 11:19 PM
To: Tomcat Users List
Subject: Re: New context in server.xml prevents war unpacking (TC 4.1.12)


Unfortunately, this is expected behavior.  There is a bug about it at  
http://nagoya.apache.org/bugzilla/ if you want to search for it.  The docs  
mention this as the expected behavior, but don't give a reason why it  
should be that way.

Basically, if you name a  element, you will have to make sure  
you expand the .war yourself before starting Tomcat.

Any Tomcat developers want to pipe in and explain why the behavior is this way?

Jake

At 09:40 PM 10/24/2002 -0500, you wrote:
>I recently added a new context to server.xml so that I can set up a
>database
>connection pool resource for my webapp.
>
>The webapp was deploying/running well prior to adding this context.
>
>With the context added, starting Tomcat produces an error for that app
>context:
>
>java.lang.IllegalArgumentException: Document base
>/usr/local/tomcat/webapps/myapp does not exist or is not a readable
>directory
> at
>org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.jav  
>a:193)
>
>This suggests that docBase directory is expected to exist at start.
>Without that context in server.xml, the war unpacks and
>creates its directory.
>
>The context looks like this:
>
>reloadable="true" crossContext="true>
> ... resources here ...
> 
>
>If I change the docBase to "myapp.war", the application loads and runs
>properly, db conn pooling works a treat, BUT
>the war isn't unpacked at all.
>
>The behavior I want is to have the war get unpacked ( as it was before
>) so that I can serve some of the static content
>directly from Apache httpd, but still package/deliver/deploy the webapp
>as a war to Tomcat.
>
>Any thoughts as to why this is happening / how to solve?
>
>Thanks.
>
>- Ken
>
>
>--
>To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
>For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Re: New context in server.xml prevents war unpacking (TC 4.1.12)

[Robert L Sowders]

I believe the reloadable="true" statement refers to reloading currently 
deployed webapps that have changed in some way and not to "deploying" 
webapps.

So if you want to customize your context for your database you can either 
auto-deploy in the webapp directory then customize your context and 
restart Tomcat or make your own context and deploy your webapp yourself 
into the docbase you specified.  In either case the docbase will have to 
exist when Tomcat reads the server.xml file.  If not you get the error.

rls





Ken Pelletier <[EMAIL PROTECTED]>
10/24/2002 07:40 PM
Please respond to "Tomcat Users List"

 
To: Tomcat List <[EMAIL PROTECTED]>
cc: 
Subject:New context in server.xml prevents war unpacking (TC 4.1.12)

I recently added a new context to server.xml so that I can set up a 
database
connection pool resource for my webapp.

The webapp was deploying/running well prior to adding this context.

With the context added, starting Tomcat produces an error for that app 
context:

java.lang.IllegalArgumentException: Document base 
/usr/local/tomcat/webapps/myapp does not exist or is not a readable 
directory
 at 
org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.jav 
a:193)

This suggests that docBase directory is expected to exist at start. 
Without that context in server.xml, the war unpacks and
creates its directory.

The context looks like this:

 mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: 





--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: New context in server.xml prevents war unpacking (TC 4.1.12)

[Jacob Kjome]

Unfortunately, this is expected behavior.  There is a bug about it at 
http://nagoya.apache.org/bugzilla/ if you want to search for it.  The docs 
mention this as the expected behavior, but don't give a reason why it 
should be that way.

Basically, if you name a  element, you will have to make sure 
you expand the .war yourself before starting Tomcat.

Any Tomcat developers want to pipe in and explain why the behavior is this way?

Jake

At 09:40 PM 10/24/2002 -0500, you wrote:
I recently added a new context to server.xml so that I can set up a
database
connection pool resource for my webapp.

The webapp was deploying/running well prior to adding this context.

With the context added, starting Tomcat produces an error for that app
context:

java.lang.IllegalArgumentException: Document base
/usr/local/tomcat/webapps/myapp does not exist or is not a readable
directory
at
org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.jav 
a:193)

This suggests that docBase directory is expected to exist at start.
Without that context in server.xml, the war unpacks and
creates its directory.

The context looks like this:


  reloadable="true" crossContext="true>
... resources here ...


If I change the docBase to "myapp.war", the application loads and runs
properly, db conn pooling works a treat, BUT
the war isn't unpacked at all.

The behavior I want is to have the war get unpacked ( as it was before
) so that I can serve some of the static content
directly from Apache httpd, but still package/deliver/deploy the webapp
as a war to Tomcat.

Any thoughts as to why this is happening / how to solve?

Thanks.

- Ken


--
To unsubscribe, e-mail:   
For additional commands, e-mail: