Insert Witty Irony Here

Wednesday February 08, 2006

Good news for WebWork users One of my co-workers has been able to deploy a large app built on WebWork to GlassFish.

He ran into some security policy issues during deployment and testing. His blog entry has the details. (2006-02-08 08:25:10.0) Permalink

Monday February 06, 2006

News for AppFuse-rs I had posted a quick note about using Equinox on GlassFish. Matt Raible saw it and figured that AppFuse should work, too.

I think it will soon, but not today. A couple other folks appear to have run into an issue in GlassFish related to the use of Acegi. Once the issue is resolved, I will write up an entry about integrating AppFuse into the GlassFish environment (which includes the Derby database). (2006-02-06 17:16:34.0) Permalink

Tuesday January 31, 2006

Another way to waste a few minutes I have been helping a user duplicate the results of my Appclient calling and Stateles EJB 3.0 example. The user was seeing the Java Console open and then close right back up...

I read the user's code a couple times, to no avail...

It just did not work.

We kept getting this message in the log:

Applying default to ejb reference: Unresolved Ejb-Ref client.Main/bean@jndi: beans.DistantGreeting@null@beans.DistantGreeting@Session@null

The Root Cause

Monday January 30, 2006

A history lesson of deployment strategies A recent entry by Jean-Francoise Arcand, reminded me of an article that I saw a couple years ago. The article covered information about deploying application to SJSAS 8.

Folk who have been paying attention may note that the GlassFish Project is based on code that was originally part of SJSAS 8, so the article has information that is relevant today...

For example, folks who want to use a "supported" fast deployment method for their J2EE components and application may want to consider combining "Directory Deployment" with "Dynamic Reloading".

I have done some tests with dynamic reloading in the past. The reloading mechanism was smart enough to detect whether I had changed a DD file or a class and http://imdb.com/title/tt0097216/.

If you are an ant user, you can even write code that will detect if you have just changed a java file and do next to nothing when you build and "redeploy" a web app that just has JSP changes. [For JSP changes, you don't need to touch the dot-reload file...]

I haven't done it for a while, so I may need to look it up or reinvent it.

NetBeans Note: Folks that use NetBeans may not know that NetBeans does the right thing for JSP web-apps deployed to the SJSAS 8.1, 8.2, and GlassFish. Web-apps are directory deployed (by default) and JSP files are copied to the "deployment" directory when they are saved in the editor. So, you can edit and reload your JSP pages... no redeploy is required! (2006-01-30 11:27:36.0) Permalink