 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | -none- | -none- 2007-10-02 - By nyronian
Back
Excuse me...I meant version 5.5.20
nyronian wrote:
>
> I am on 5.0.25.....
>
> Here are the different deployments I have tried and the problems I have:
>
> First, the context.xml is simple:
>
> <Context path="/site" docBase="/usr/apps/app1" reloadable="false"
> privileged="false" />
>
> The server.xml Host entry is:
> <Host name="localhost" appBase="webapps" unpackWARs="false"
> autoDeploy="false" deployOnStartup="true" xmlValidation="false"
> xmlNamespaceAware="false">
>
> (I have toyed with different settings on unpackWARS, autoDeploy and
> deployOnStartup without success)
>
> Scenario 1:
> 1. Place the context.xml in the META-INF of the war and deploy using the
> manager "WAR file to deploy"
> - As expected, it ignores the path and places the war in the appBase
> directory, not in the docBase directory.
>
> Scenario 2:
> 1. Place the war and context.xml in a particular location on disk.
> 2. Using the "Deploy directory or WAR file located on server" (in manager)
> I use the following options:
> a. Context Path = /site
> b. XML Configuration file URL = file:/path/to/file/context.xml
> c. WAR or Directory URL = file:/path/to/war/abc.war
>
> - This simply leave the war where it is at, does not unpack it in the
> specified docBase and tries to start the war...unsucessfully at that.
> - I was hoping it would load the war, unpack it in the docBase and start
> it up
>
> Scenario 3:
> 1. Place the war and context.xml in a particular location on disk.
> 2. Using the "Deploy directory or WAR file located on server" (in manager)
> I use the following options:
> a. Context Path (optional) = leave this blank
> b. XML Configuration file URL = file:/path/to/file/context.xml
> c. WAR or Directory URL = file:/path/to/war/abc.war
>
> - Message FAIL - Invalid context path was specified
> - this ignores the path in the context.xml and required the optional
> parameter Context Path.
>
> At any rate, I have mulled over these options in several combinations all
> of which has been unsucessful.
>
> There is one Sucessful Senario:
>
> 1. Stop the application.
> 2. maually</> delete and unpack the new war in the specified docBase
> directory.
> 3. Using the "Deploy directory or WAR file located on server" (in manager)
> I use the following options:
> a. Context Path = /site
> b. XML Configuration file URL = file:/path/to/file/context.xml
> c. WAR or Directory URL = file:/path/to/unpackedwar/directory
>
> - This seems to work but do not want the manual steps.
>
>
>
> Scott McClanahan wrote:
>>
>> On Tue, 2007-10-02 at 16:51 -0400, nyronian wrote:
>>>
>>> To put it simply, I would like to use the manager to deploy an app
>>> just like
>>> auto-deployment works but I need to change the context (path) without
>>> changing the name of the war.
>>>
>>> I am trying to implement the following deployment requirment:
>>>
>>> 1. Change the context (path) of the war I am deploying, different from
>>> the
>>> name of the war. Note: I know this is not best practice and against
>>> tomcats model but I cannot change the name of the war, as much as I
>>> would
>>> love to.
>>>
>>> 2. Deploy the war outside of the appBase directory via the tomcat
>>> manager.
>>> Note: this has to be done in order to change the context. The context
>>> cannot be changed if it resides in the appBase directory
>>>
>>> 3. When deploying the war, have it:
>>> a. load the war from disk (or from an URL)
>>> b. un-deploy itself if needed (delete the directory off disk)
>>> c. unPack itself to disk in the location specified (as specified
>>> by
>>> the docBase parm)
>>> d. deploy itself under the given context (path)
>>>
>>>
>>>
>>> Note: I have done a ton of research and can't seem to find this exact
>>> scenario. I can manually do this by simply laying out the war on disk
>>> and
>>> loading the context.xml file and point to the directory, but I can't
>>> seem to
>>> auto-deploy with this scenario with the manager tool.
>>>
>>> Thanks.
>>> --
>>> View this message in context:
>>> http://www.nabble.com/deploy-outside-of-appBase-w-Manager-tf4558016.html
#a13007722
>>> Sent from the Tomcat - User mailing list archive at Nabble.com.
>>>
>>>
>>> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
>>> To start a new topic, e-mail: users@(protected)
>>> To unsubscribe, e-mail: users-unsubscribe@(protected)
>>> For additional commands, e-mail: users-help@(protected)
>>>
>>>
>> You can if you use tomcat 5.0.x for the most part (5.0.28 for sure). It
>> works brilliantly.
>>
>>
>> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
>> To start a new topic, e-mail: users@(protected)
>> To unsubscribe, e-mail: users-unsubscribe@(protected)
>> For additional commands, e-mail: users-help@(protected)
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/deploy-outside-of-appBase-w
-Manager-tf4558016.html#a13009274
Sent from the Tomcat - User mailing list archive at Nabble.com.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
|
