On 04/ 3/09 05:26 PM, glassfish_at_javadesktop.org wrote:
> OK thanks for the input, I tried as you suggested, but got the same behavior. What strikes me as odd is other webapps are working fine in this same scenario, and just two of them are not.
>
> Also, I am having a hard time understanding the difference between assigning a webapp a virtual server, and assigning a virtual server a default web app. Can someone help explain in easy terms the difference between assigning as such in the two different spots?
>
Consider this example:
Config:
http-listener:
id: "mylistener"
port: 1234
virtual-server:
id: "myvs"
hosts: "abc"
http-listeners: "mylistener"
Deploy foo.war on virtual server "myvs":
-> foo.war will be accessible at
http://abc:1234/foo
Declare foo.war as the default-web-module of virtual server "myvs":
-> foo.war will be accessible at both
http://abc:1234/foo
and
http://abc:1234/
i.e., for as long as foo.war is declared as the default-web-module
of "myvs", it will not only be accessible at its designated context
root "/foo", but will also "occupy" the root context ("/") of "myvs".
Jan
> Thanks again much for the help!
> Eric
> [Message sent by forum member 'scit' (scit)]
>
> http://forums.java.net/jive/thread.jspa?messageID=340559
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>