Hi,
It's not part of the JAR or WAR specs, it's a tomcat-specific feature,
and it's in our docs.

Yoav Shapira http://www.yoavshapira.com


>-----Original Message-----
>From: Phillip Qin [mailto:[EMAIL PROTECTED]
>Sent: Monday, October 18, 2004 12:32 PM
>To: 'Tomcat Users List'
>Subject: RE: Tomcat Ant Tasks
>
>Or documented in tomcat doc? Sorry, I forgot.
>
>-----Original Message-----
>From: Phillip Qin [mailto:[EMAIL PROTECTED]
>Sent: October 18, 2004 12:31 PM
>To: 'Tomcat Users List'
>Subject: RE: Tomcat Ant Tasks
>
>
>I think it is part of sub's jar spec.
>
>-----Original Message-----
>From: Gregg Bolinger [mailto:[EMAIL PROTECTED]
>Sent: October 18, 2004 12:29 PM
>To: 'Tomcat Users List'
>Subject: RE: Tomcat Ant Tasks
>
>
>PERFET!  Thanks.  Now, is that in the docs anywhere?  If it's not, it
>should
>be.
>
>-----Original Message-----
>From: Phillip Qin [mailto:[EMAIL PROTECTED]
>Sent: Monday, October 18, 2004 11:16 AM
>To: 'Tomcat Users List'
>Subject: RE: Tomcat Ant Tasks
>
>Pack your context into war, as META-INF/context.xml using ant jar
command.
>
>
>
>-----Original Message-----
>From: Gregg Bolinger [mailto:[EMAIL PROTECTED]
>Sent: October 18, 2004 12:14 PM
>To: 'Tomcat Users List'
>Subject: RE: Tomcat Ant Tasks
>
>
>Then I am confused.  I have a config that contains my apps context
where I
>have defined my datasource for JNDI etc.  If I don't define config in
the
>deploy task, a default context is created, which I don't want.
>
>Also, the war deploys just fine, like I said.  So I don't have a
problem
>deploying the WAR file.  I am only having a problem getting my custom
>context config to get deployed as well.
>
>-----Original Message-----
>From: Phillip Qin [mailto:[EMAIL PROTECTED]
>Sent: Monday, October 18, 2004 11:08 AM
>To: 'Tomcat Users List'
>Subject: RE: Tomcat Ant Tasks
>
>This is my ant task
>
><deploy
>       url="${dev.manager}"
>       username="${username}"
>       password="${password}"
>       path="${context.path}"
>       war="${war.url}"
>       update="true"/>
>
>No need to define config. On *nix box, war.url is
file:/your/path/to/war,
>on
>win32 box, war.url is file:/c:/your/path/to/war.
>
>
>Context will always be dropped off conf/${engine}/${host} as
>${your.context}.xml
>
>
>-----Original Message-----
>From: Gregg Bolinger [mailto:[EMAIL PROTECTED]
>Sent: October 18, 2004 11:26 AM
>To: [EMAIL PROTECTED]
>Subject: Tomcat Ant Tasks
>
>
>I am trying to use Tomcat Ant tasks to deploy my application while
testing.
>The only part I am having a problem with is trying to deploy the
context
>config file.  Below is my task
>
>
>
><target name="deploy-local" depends="war">
>
>        <deploy
>
>            url="${tomcat.local.url}"
>
>            username="${username}"
>
>            password="${password}"
>
>            path="${path}"
>
>            update="true"
>
>            config="//$(basedir}/resources/anykey.xml"
>
>            war="//${basedir}/build/${deploy.name}"/>
>
>    </target>
>
>
>
>The war file is deployed just fine, but my config file goes nowhere.
ANT
>claims everything was successful.  Does anyone have any ideas about
this?
>
>
>
>Thanks
>
>
>
>Gregg Bolinger
>
>
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>!DSPAM:4173efd1139771216089279!



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to