OK, just to complete the post, I'll tell you about the problem I encountered. Now, I have decided that I don't think there's anything wrong with the jboss-web.xml example I originally posted.

When you deploy web apps in JBoss/Tomcat, jboss uses a couple of "working" directories inside server/MY_SERVER.

One of them is called "work" and one of them is called "tmp".

I have noticed that, especially on Windows 2000, sometimes stuff is not getting properly deleted from one or both of these directories. When that happens, stuff can get screwed up. ;) It seems to be the equivalent of you fixing something, but your changes not "taking" -- and I'm sure you know what a nightmare that can be.

Could be a file permission thing, as I suggested earlier in another post in response to problems someone else was having with deploying on WebLogic. I haven't had time to learn about Windows 2000 security (gee, can't wait) and file management.

I ended up having problems with the virtual host setup on my unix box, though it might just be a mozilla problem or misconfiguration. So I changed my jboss-web.xml to simply this:

<jboss-web>
 <context-root>/</context-root>
</jboss-web>

That should be the equivalent of replacing the "default" web app (which I removed from jbossweb-tomcat50.sar/ROOT.war to make sure there weren't further conflicts), but I'm not 100% positive. So that's what I should have posted as the original jboss-web xml. Didn't mean to throw the whole virtual-host thing in there when it's not necessary.

Hope you are having better luck than me!

Erik



Erik Weber wrote:

James, sorry, but this file ended up causing problems. Obviously there is more to configuring a virtual host than this, but I haven't had time to research it yet.

I'll repost as I tackle that.

Erik



Erik Weber wrote:

No, but I was overlooking something simple (virtual host setup) to do the equivalent, in jboss-web.xml:

<jboss-web>
   <context-root>/</context-root>
   <virtual-host>foo</virtual-host>
</jboss-web>

Which would allow you to access your web app using:

http://foo:8080/

with no context name.

Hope that helps,
Erik


James Mitchell wrote:

Did you ever get a response on this?



--
James Mitchell
Software Engineer / Open Source Evangelist
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx

----- Original Message ----- From: "Erik Weber" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 2004 9:38 PM
Subject: Re: [OT] JBoss/Tomcat & default context





The main thing I want to get around is having to restart the server, if that's possible.

Thanks,
Erik


Erik Weber wrote:



Hi. I need to test my foo.war file using the default context in JBoss 3.2.4/Tomcat 5. So right now I am unpacking the war and placing all the contents inside /deploy/jbossweb-tomcat50.sar/ROOT.war/, in place of the default JBoss web app contents.

Is there an easier way?

Erik


--------------------------------------------------------------------- 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]







--------------------------------------------------------------------- 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]



--------------------------------------------------------------------- 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]



Reply via email to