Deployment in GlassFish v3 prelude

With GlassFish v3 prelude now out and widely available (you can download it from here), I thought I'd break my long blogging radio silence with a brief summary of deployment in GlassFish v3 prelude.


In this case, no news (well, only a little news, really)  is good news.  With GlassFish v3 prelude you can deploy applications in almost all the ways you can in earlier versions.  And because of the architectural changes in v3 deployment tends to be quite a bit faster than in v2.  Of course your mileage may vary.















Still works from v2
Does not work yet
New in v3

Admin console - as great as always


Command line (asadmin deploy)



  • The option --force now defaults to false.  This is safer and prevents people from accidentally overwriting an app of the same name they or someone else deployed earlier.

  • The deploydir command continues to work but is deprecated; the deploy command now accepts either an archive file (for example, a .war file) or a directory that contains the expanded form of the application


Autodeployment - Copy an archive into ${domain-dir}/autodeploy and GlassFish does the rest.  To undeploy the app, just delete the file you copied into the autodeploy directory in the first place.


Dynamic reloading (really "dynamic redeployment") - touch .reload in the application's directory and GlassFish redeploys the application


JSR-88 API - will be present in the final v3 release

http (REST-like) interface - From a browser or an application send an http request to request deployment or undeployment of an application:



http://localhost:4848/__asadmin/deploy?contextroot=bar&path=/usr/local/foo.war


http://localhost:4848/__asadmin/undeploy?name=foo


Keep web sessions across redeploy - Vince reminds me about the new redeploy command and its --properties keepSessions=true option, added in v3 prelude, which allows you (you probably guessed it) to keep any current sessions alive across the redeployment.  See Jan's blog for more about this.


Comments:

Tim, don't forget about the --properties option on the redeploy command... hey, did you skip mentioning redeploy, to boot?

I was able to leverage the keepSessions property from inside NetBeans to juice developer productivity... See http://blogs.sun.com/vkraemer/entry/are_you_sure_you_are for details about how it is being used.

For details about the keepSessions property, folks should read through http://blogs.sun.com/jluehe/entry/retain_session_data_during_redeployment, which is has the details that we leveraged to make the change in NetBeans.

More info about redeploy is here: http://docs.sun.com/app/docs/doc/820-4497/redeploy-1?a=view

vbk

Posted by Vincent Kraemer on November 06, 2008 at 02:35 AM CST #

Tim,
Would you happen to know when and if GlassFish v3 is scheduled to support clustering / high-availability? I have posted the following question on a number of blogs and newsgroups, but no replies as of yet:

I would like to use the DeliverResponse class in the latest version of grizzly, but v2ur2 seems to come with the 1.0.11 version. Is there any way I can upgrade my GlassFish v2ur2 with a later version of Grizzly. I require clustering / HA, so this is an issue. Thank you, Anthony

Posted by Anthony on January 02, 2009 at 02:37 AM CST #

Anthony,

It looks as if Lloyd has responded to your clustering/HA question on the dev@glassfish.dev.java.net alias and I think I saw a reply by Jean-Francois about your Grizzly question.

Many of us were out of the office for late December so that might explain some of the delay in responses.

Posted by Timothy Quinn on January 05, 2009 at 03:42 AM CST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

News and musings on the technology I work on at Oracle.

The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today