« GlassFish v3 gem... | Main | An Endorsement for... »
http://blogs.sun.com/pramodg/date/20080213 Wednesday February 13, 2008

GlassFish v3 gem v0.1.1 for JRuby at RubyForge

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 :


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 : Please note that this is not an exhaustive list and would continue to work on issues that are being reported on Glassfish Issue Tracker, JRuby JIRA and RubyForge.

If you have installed the previous version of the gem please uninstall the gem using the command
jruby -S gem uninstall GlassFish
Install the new version of the gem using the command :
jruby -S gem install glassfish

Sample output from executing the glassfish gem v0.1.1 on my Macbook pro :

My JRuby environment :
List of gems installed in my JRuby 1.0.3 environment

Command line argument support :
Command line argument support in GlassFish V0.1.1 gem

Start Mephisto application :
Launching the GlassFish v0.1.1 gem for Mephisto application

Mephisto web request
Mephisto application and Glassfish v0.1.1 gem

Resources :
GlassFish JRuby wiki
JRuby wiki


Posted by pramodg [Sun] ( February 13, 2008 10:19 PM ) Permalink | Comments[4]
Comments:

[Trackback] Pramod released an updated version 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...

Posted by Arun Gupta's Blog on February 14, 2008 at 06:53 AM PST #

Excellent! Thanks for pushing it out so quickly Pramod.

Posted by Rich Manalang on February 14, 2008 at 09:05 AM PST #

Hi Pramod,

When I run glassfish_rails, here's what I get:

Elena:hello vishnu$ jruby -S glassfish_rails hello
[..snipped..]
INFO: Startup service : Deployment
Feb 18, 2008 12:09:04 PM com.sun.enterprise.v3.server.AppServerStartup run
INFO: Startup service : org.glassfish.deployment.autodeploy.AutoDeployService@47fda0
Feb 18, 2008 12:09:04 PM com.sun.enterprise.v3.services.impl.GrizzlyAdapter <init>
INFO: Listening on port 3000
Feb 18, 2008 12:09:04 PM com.sun.enterprise.v3.services.impl.GrizzlyAdapter <init>
INFO: Listening on port 3131
Feb 18, 2008 12:09:04 PM com.sun.enterprise.v3.services.impl.GrizzlyAdapter <init>
INFO: Listening on port 3838
Feb 18, 2008 12:09:04 PM com.sun.enterprise.v3.server.AppServerStartup run
INFO: Startup service : com.sun.enterprise.v3.services.impl.GrizzlyService@d1a23c
Feb 18, 2008 12:09:05 PM com.sun.enterprise.v3.server.AppServerStartup run
INFO: Startup service : Application Loader
Feb 18, 2008 12:09:05 PM com.sun.enterprise.v3.server.AppServerStartup run
INFO: Glassfish v3 started in 990 ms

As you can see, I'm missing the "Starting Rails instances" bit, and I'm not sure what's wrong. I must be missing something simple here, but no idea what it is!

I am running this from the root of a rails install, and I've got all the gems you've listed installed.

Anything that you can think of?

Thanks,
Vishnu

Posted by Vishnu Gopal on February 17, 2008 at 10:43 PM PST #

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.

Thanks
Pramod

Posted by Pramod Gopinath on February 19, 2008 at 11:59 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed