DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32771>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32771


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Additional Comments From [EMAIL PROTECTED]  2004-12-22 11:51 -------
Well, Remy, just out of curiosity, when you consider a bug a bug? ;)
> Avoid screwing up context.xml (and same with server.xml).
In a perfect world i'd agree with you, but in a large company where, who's
operating (and sometimes configuring) the application servers are not the same
people who wrote the apps, to paraphrase a famous movie, "I've seen things, you
humans can't even imagine...":)

Anyhow, i tried to look into the source and i saw that the problem is that the
app gets registered in the deployed Map when indeed the Context has not been
built and there's no child with that name added to the host container.
This makes the app no longer neither deployable nor undeployable and makes
Tomcat behaving erratically at stop time.
If i didn't overlook something, in org.apache.catalina.startup.HostConfig should
be enough to check if the digester correctly built the Context and if has been
added as a child to the host container before registering it into the deployed 
Map.
In this case, the war deployer will have a chance later to try to deploy the app
war, but since the context.xml is screwed up, the app will be registered but
will remain stopped.
This will allow to undeploy and redeploy it without problems.

Obviously this will cause the context.xml to be parsed twice, and the log will
show twice the SAXException messages, but i don't think this should be a
problem, because now it is a recoverable and controlled situation.

I'll attach a patch for this.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to