I hope that there is some misunderstanding here.
virtual hosts should have NOTHING to do with deploying stuff packed/unpacked. Jetty should only deploy to a virtual host IFF a virtual-host tag is specified in your WEB-INF/jboss-web.xml. This will work independendantly of however you choose to package your app. Is anyone experiencing any behaviour that would lead them to believe otherwise ? Jules Andrea Delle Chiaie wrote: > Hi rp, > I had the same problem and I've found, looking at the jboss console traces > that JBoss-Jetty deploys the .war under the virtual host called > myvirtualhost and so, if you are able to resolve the name myvirtualhost (if > is your machine, just add myvirtualhost to your hosts file) try to point > your browser to http://myvirtualhost:8080/your_context and you'll see it > working. > I don't know why Jetty is configured to use the myvirtualhost and I didn't > find where it is, but I know that this is the situation, please if someone > knows the solution, post in the list. > Bye > > Mr. Andrea Delle Chiaie > > Notio Srl > Viale Ratto delle Sabine 45/a > 00133 - ROMA > tel +39-06-41.29.47.73 > fax +39-06-41.40.44.28 > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: martedi 9 luglio 2002 19.26 > To: [EMAIL PROTECTED] > Subject: [JBoss-user] JBoss 2.4.7 + Catalina 4.0.4 - problems deploying > expanded directory > > > > Using JBoss 2.4.4 + Jetty, I can deploy an unpacked, expanded directory by > pointing the > autodeployer in the jboss.jcml to that particular directory. I try the same > thing with JBoss 2.4.7 > + Tomcat (Catalina) 4.0.4 and it doesn't work at all !! > > It appears to be deployed - the log file indicates that it is creating a > module of <dir_name>/ > with a context path of /<dir_name>/. No errors on deployment. Yet, when I > try to hit a particular > .jsp immediately under that context path, say > http://localhost/<dir_name>/<jsp_name> I get > a 500 error message from Catalina saying that there is no context configured > to handle the > request. > > I've tried putting the directory into JBoss' deploy directory. I've tried > putting the directory into > JBoss' deploy directory and then renaming it to <dir_name>.war, etc. I get > the same results > as above. > > The only time I can get it working with Tomcat is to package the directory > up and deploy it > as a packaged file. This ought to work! Can anyone explain why it isn't? > > rp > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Two, two, TWO treats in one. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
