=================================
Steven
Ah... I see what you doing... this is what is wrong
Do not change the name of the WEB APP.... of the WAR
The way TC relates context and path is thru the actual name of the file.
This is so that normal humans can easily change the context just by
changing the file name...
So make the context file in TC look something like this
<?xml version="1.0" encoding="UTF-8"?>
<Context docBase="D:/DEV/Ext/test/WebApplication2.war"
path="/WebApplication2"/>
The path is the context you want it to run on.... ie
domain/WebApplication2
Make them the SAME...
Then do this... in HOST
autoDeploy="true"
Then just drop the new wars over the old one.... and it will redeploy
automatically.
Notes...
You are not sharing files like this, ie when it deploys, each TC is
getting its own unpacked version in webapps... have a look.
So you see what happens and its what you calling CACHING... is that when
you change the name... TC looks for that context.
Cant find it, BUT does find the old already unpacked one in webapps... and
just runs that.
It cant connect that the new WAR name, ie context must be the same as war
file name.
<Context docBase="D:/DEV/Ext/test/WebApplication2.war"
path="/WebApplication2"/>
is the full way, so you can see if you can try match a context to a
different war name, but I dont think TC will figure it out.
If you want to "mismatch" war and context... you can
but then you must undeploy from /manager/html
and you must run this to redeploy
http://localhost:8080/manager/deploy?config=file://path/to/context.xml&path=/NewContext
Too much pain...
Then one last thing... becareful if you develop against one of these
TC's... as soon as you do that, the IDE will steal the context away.
And then you'll think its caching again... but its using the one in the
IDE...
ie you shouldnt develop against these production TC's.
How Apple shares one binary is a mystery to me... there you on your own,
but I dont think its related, other than I think you not seeing it because
the files are hiding in those hidden Apple bundles, and thats why it
probably been deployed extenally like this, because of those virtual
links.
Apple madness ;)
Steve Jobs is on another planet... so I suggest you also join
[EMAIL PROTECTED]
because the other stuff thats happening with Java and Apple, we cant help
you with... like where is Java 6 and other issues.
You predecessor played nicely.... good luck
The rest of us... we just drop webapps into webapp... then go fly planes
or play golf ;)
Thanks... I learnt something ;)
---------------------------------------------------------------------------
HARBOR : http://www.kewlstuff.co.za/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
---------------------------------------------------------------------------
Steve, another after-thought....
Was just thinking about what it is you actually doing, and why you confusing
the hell out of us ;)
Read up on http://localhost:8080/tomcat-docs/virtual-hosting-howto.html
You could actaully drop a whole Tomcat (Apple Bundle Virtual Machine thing)
Use one Tomcat where you can see the thing... just start it from a script,
or the Apple service thing, without hiding it in some fruit.
And then go thru the huge effort of dropping duplicate webapps into 2
folders ;)
An Apple guy may be able to clarify... but I think this whole thing is one
complex Apple contaminated way of doing virtual hosting.
And if there are 2 tomcats running, you must be on different ports ??????
So have a read, I think you can get it all back to one TC, on one port, and
just drop wars into webapps...
ie I think this whole thing is an Apple fix... for something that TC already
does ;)
2 wars, 1 TC.... is probably better than 2 TC's 1 war... hey ;)
Have fun....
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
