On 02/ 8/10 05:54 AM, glassfish_at_javadesktop.org wrote:
> Yes, that particular issue was fixed in v2.1.1.
>
> However, I suspect it's a different problem in your case, as even with that bug not fixed, it will still work if you redeploy the application.
>
I think there is some kind of misunderstanding on the user's part. His
original
complaint was like this:
"But the directory listing is not disabled, even after redeploying the
application."
vivekmv2000, note that simply redeploying your app (*without* restarting
the server)
in order for it to pick up any changes to default-web.xml was *never* an
option:
A server restart is always required for any changes in default-web.xml
to be picked up.
This is because the default-web.xml is parsed only during domain
startup, and its parsed
contents are held in memory and never updated until a subsequent server
restart.
Prior to the fix for
https://glassfish.dev.java.net/issues/show_bug.cgi?id=3844, in addition
to restarting the server, you also had to redeploy your app in order for
it to pick up any
changes to the default-web.xml.
With the fix for IT 3844 in place, a server restart will be sufficient.
I just verified that this
works as intended with v2.1.1.
Jan
> [Message sent by forum member 'hzhang_jn' (hong.zhang_at_sun.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=385440
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>