Blog for pramodg

GlassFish v3 gem v0.1.1 for JRuby at RubyForge

In my previous blog I had informed you all of the the GlassFish v3 gem v0.1.0. The first release was pushed out last week so that Charles Nutter to demo at the acts_as_conference held last weekend. The gem was very well received at the conference and based on the feedback provided by the attendees, have decided to release a new version to address many of the common issues that were reported.

Issues being addressed in v0.1.1

The following issues are being addressed in this version (v0.1.1) of the gem :

The name of the gem is being changed from GlassFish to glassfish. The rails naming convention for the gems is with all lower case or with names that contain underscore.

Support for the applications to be deployed at the Root Context ("/") of the server. The Webrick and Mongrel servers deploy the application to the root context by default.

Change the default port the server to be 3000 from 8080. Port 8080 has been the default http port of the GlassFish application server, but since we are targetting the Ruby on Rails market with this space, it is better to have the http port set to 3000. At this stage I have also changed the SSL port from the GlassFish default of 8181 to 3131 and the admin default port of 4848 to be 3838.

Provide command arguments to the script to specify the number of runtime to be created. In v0.1.0 of the gem one could specify the number of runtimes if it was passed in as a specified as a java system property. With this version use could use the command

jruby -S glassfish_rails mephisto -n 2

to create 2 rails instance.

Create instances of rails in parallel. This would speed up the startup of the v3 gem

Main issues I plan to address in v0.1.2
Some of the main items that I plan to work on as part of the gem v0.1.2 :

I have created the gem from the v3 code that was checked out on 02/08/2008. All the local changes are currently on my laptop. Would be working on getting these chages checked into the v3 code base and would publish steps on how to create a gem from the trunk. Currently there is a manual step involved in setting up the port. I would have to fix this before checking the code in the svn trunk.

As part of this release was planning to add support for specifying RAILS_ENV as a command argument. But was running into some issues. Would like to provide this in the next release.

Provide a way for users to provide a port portion as one of the command argument. This would involve making changes in the v3 code since currently the logic is in place to read the port from the config/domain.xml.

There is growing interest for Merb and plan to interact with Nick Sieger to see how we can add support for Merb in the gem.

[Trackback] Pramod released an updated version&nbsp;0.1.1 of the JRuby GlassFish v3 gem. What's New ? - Mainly alignment with Rails convention The name of the gem is changed from "GlassFish" to "glassfish". The default port number is 3000. Applications are...

Hi Vishnu
Can you check the directory that you are at when the command "jruby -S glassfish_rails hello" is being issued.
Ensure that you are at the root of the hello application i.e :
if the hello sample is at /export/home/railsSample/hello then ensure that you are at
/export/home/railsSample when you issue the command "jruby -S glassfish_rails hello".

The gem currently does not work if you are within the sample application directory and issue the command. Will fix in one of the subsequent examples.

When running Mephisto with the 0.2 glassfish_rails gem I can't access the /admin URL, since it's associated with the GlassFish admin instead. This is extremely inconvenient so it would be practical if there was some way to specify another binding url for the GlassFish admin console.