Sounds to me like this is a bug in tomcat 5. Are you running a stable version of tomcat 5? It seems odd that what worked in tomcat 4 wouldn't work in 5. I've had some complaints about transitioning between various versions of tomcat. Every version has it's own quirks. I've been exploring Jboss recently, maybe you should too.

In tomcat 4, I first created the following folder:

$CATALINA_HOME/work/Standalone/${hostname}/manager/srv

This folder is where the war and context file for the
application will be placed when deploying via ant or
maven using the manager.

Now, in the application's context.xml file, I set the
path to '/srv/stuff' and the docBase to the same.

Once deployed, the war and context files will be named
stuff.war and stuff.xml in the above directory.

Tomcat 5 works a bit differently. When the app is
deployed with the srv prefix, the war and context file
are renamed to srv#stuff.war and srv#stuff.xml after
deployment via maven (haven't tested ant yet, but
we're trying to phase it out as a deployment tool
anyway). Here is the problem:

2004-11-22 09:47:38 StandardContext[/manager]Manager:
install: Installing context configuration at
'file:$CATALINA_HOME/conf/Catalina/${hostname}/srv#stuff.xml'
from 'jar:file:$CATALINA_HOME/webapps/srv#stuff.war!/'
2004-11-22 09:47:38 StandardContext[/manager]Manager:
ManagerServlet.configure[file:$CATALINA_HOME/conf/Catalina/${hostname}/srv#stuff.xml]
java.net.MalformedURLException: no !/ in spec
       at java.net.URL.<init>(URL.java:571)
       at java.net.URL.<init>(URL.java:434)
       at java.net.URL.<init>(URL.java:383)
...

I am assuming the problem is the # in the filename,
but I'm not sure.

I thought I found a workaround the other day. If I
just had maven build the war and then use the manager
html interface to deploy the war, it worked fine. The
files were in their place as stuff.xml and stuff.war.

But once I restarted tomcat, the manager list showed 2
apps deployed; /stuff and /srv/stuff, neither of which
worked.

I've tried several other configurations all with
varying levels of failure.

Any ideas?

Dustin


--- QM <[EMAIL PROTECTED]> wrote:

On Wed, Dec 01, 2004 at 09:36:28AM -0800, Dustin
wrote:
: For example, an app that
: had a path of /stuff now has a path of /srv/stuff.
: : I was able to get it working in tomcat 4 (the
solution
: seemed like a hack to me tho), but I am having
: problems getting it to work in tomcat 5.

Perhaps you could share what you did in Tomcat 4,
and what you've
tried in v5..?  That might give the rest of us a
head start.

I don't have the time to try it here, but I suppose
you've already
tried a context path of "/srv/stuff" and that
failed?

-QM

--

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



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



Reply via email to