Hi, Vince
This is actually by design: :-)
http://wiki.glassfish.java.net/Wiki.jsp?page=VersioningDesignDocument#section-VersioningDesignDocument-5.5VersionSUndeployment
"If a user undeploys the currently enabled version, then GlassFish
will not enable automatically another version."
It's possible that we do this when there are two versions, but what
about there are more than two versions. And we don't always know users'
intention. I think we should just keep it simple here.
Thanks,
- Hong
On 5/27/2010 1:07 PM, Vince Kraemer wrote:
> I was playing with versioned web apps for a minute or two today. It
> looks like it is pretty solid.
>
> But I did run into something that I think is a bug.
>
> I deployed two versions of a web app. that worked beautifully.
>
> Then, I undeployed the version that was enabled (the second one that I
> deployed).
>
> I expected the older version to become enabled.
> It did not become enabled automatically.
>
> I can see that there are situations where doing automatic enable on
> undeploy would not be possible (without telepathy)... but in
> situations where there are just two versions of the web app, it would
> be a usability win to do the enable automatically.
>
> People like to be lazy.
>
> vbk
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>