Hi Wouter,
If i understand it correctly from your previous email, you install
build 28, then copy over build 26 of domain.xml to this new
installation.
So, your domain.xml suggested that you have installed admin console,
but the installed bits can't be found, thats why the upgrade failed.
You should never just copy domain.xml from one build to another, there
will be other issues besides admin console.
However, i do think that we should allow upgrade even if old bits can't
be found. So, i filed
https://glassfish.dev.java.net/issues/show_bug.cgi?id=6477
and is fixed in build 28a. Thanks for your suggestion.
When build 28a is out, you should see the update is available in both
the admin console -> updatetool -> Available Updates tab or the
updatetool itself. You can install this update and when you restart
the server, the updated bits will be detected.
I haven't responsed to your previous question about what are the
packages related to admin console. Here is the list:
glassfish-gui GlassFish Administration Console
glassfish-jdbc-gui GlassFish JDBC Administration Console plugin
glassfish-web-gui GlassFish Web Container Administration Console plugin
thanks
Anissa
Wouter van Reeven wrote:
On Wed, Oct 08, 2008 at 09:11:25AM +0200, To quality wrote:
On Tue, Oct 07, 2008 at 03:00:42PM -0700, Anissa Lam wrote:
I mean you can start up updatetool by doing glassfishv3_prelude/bin/
updatetool.
Yes that is how I install e.g. EJB3.1 support. Is it possible to install admin
console via updatetool as well? If so, which package should I install?
Using updatetool I uninstalled GlassFish Admin Console and then installed it
again. Still GlassFish complains that it cannot upgrade Admin Console when I try
to load it. So, in the end I removed Admin Console via upodatetool, restarted
GlassFish and then opened the Admin Console at port 4848. Now it's installed
again.
Thanks, Wouter