Miles to go …

If you are using Warbler to create a WAR file of your application and deploying on GlassFish or any other Servlet container, then you are likely seeing the following error during deployment:

This is a known issue as reported at JRUBY-3789 and JRUBY_RACK-18.

As the bug report indicates, this is actually an issue with jruby-rack-0.9.4 and is fixed in jruby-rack-0.9.5. The 3-step workaround is described here and explained below for convenience:

1. Do “warble war:clean” to clean up the .war file and staging area. This basically removes previous version of jruby-rack.jar.
2. Download the latest jruby-rack-0.9.5 snapshot (complete list) and copy in the “lib” directory of your application.
3. If “config/warble.rb” does not exist then generate it using “jruby -S config warble”. Edit “config/warble.rb” such that it looks like:
   

   # Additional Java .jar files to include. Note that if .jar files are placed   # in lib (and not otherwise excluded) then they need not be mentioned here.   # JRuby and JRuby-Rack are pre-loaded in this list. Be sure to include your   # own versions if you directly set the value   # config.java_libs += FileList["lib/java/*.jar"]   config.java_libs.delete_if {|f| f =~ /jruby-rack/ }   config.java_libs += FileList["lib/jruby-rack*.jar"]

   This will pack jruby-rack-0.9.5 snapshot instead of the one bundled with Warbler.

   Now warbler 1.0.0 bundles “jruby-complete-1.3.0RC1.jar”. Optionally, you can also download the latest jruby-complete (jruby-complete-1.3.1.jar as of this writing) and copy in the “lib” directory of your application. In that case, modify the above fragment to:

   # Additional Java .jar files to include. Note that if .jar files are placed   # in lib (and not otherwise excluded) then they need not be mentioned here.   # JRuby and JRuby-Rack are pre-loaded in this list. Be sure to include your   # own versions if you directly set the value   # config.java_libs += FileList["lib/java/*.jar"]   config.java_libs.delete_if {|f| f =~ /jruby-rack/ || f =~ /jruby-complete/ }   config.java_libs += FileList["lib/jruby-complete*.jar"]   config.java_libs += FileList["lib/jruby-rack*.jar"]

   This packs the “jruby-complete-1.3.1.jar” in your .war file.

And now follow your regular procedure of creating the .war file using “jruby -S warble” and happily deploy your Rails/Sintara/Merb applications on GlassFish.

There are several users who are already using Rails on GlassFish in production environment and they are listed at rubyonrails+glassfish+stories. Drop a comment on this blog if you are using it too

Technorati: jruby rack glassfish war servlet rubyonrails

Apache Wicket is an application framework to build web applications using HTML for markup and POJOs to capture the business logic and all other processing. Why Wicket digs more into the motivation behind this framework.

This Tip Of The Day (TOTD) shows how to create a simple Wicket application and get it running on GlassFish:

1. Create a Wicket project as:

   ~/samples/wicket >mvn archetype:create -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=1.3.6 -DgroupId=org.glassfish.samples -DartifactId=helloworld [INFO] Scanning for projects… [INFO] Searching repository for plugin with prefix: ‘archetype’. [INFO] ———————————————————————— [INFO] Building Maven Default Project [INFO]    task-segment: [archetype:create] (aggregator-style) [INFO] ———————————————————————— [INFO] Setting property: classpath.resource.loader.class => ‘org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader’. [INFO] Setting property: velocimacro.messages.on => ‘false’. [INFO] Setting property: resource.loader => ‘classpath’. [INFO] Setting property: resource.manager.logwhenfound => ‘false’. [INFO] [archetype:create] [WARNING] This goal is deprecated. Please use mvn archetype:generate instead [INFO] Defaulting package to group ID: org.glassfish.samples [INFO] —————————————————————————- [INFO] Using following parameters for creating OldArchetype: wicket-archetype-quickstart:1.3.6 [INFO] —————————————————————————- [INFO] Parameter: groupId, Value: org.glassfish.samples [INFO] Parameter: packageName, Value: org.glassfish.samples [INFO] Parameter: package, Value: org.glassfish.samples [INFO] Parameter: artifactId, Value: helloworld [INFO] Parameter: basedir, Value: /Users/arungupta/samples/wicket [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] ********************* End of debug info from resources from generated POM *********************** [INFO] OldArchetype created in dir: /Users/arungupta/samples/wicket/helloworld [INFO] ———————————————————————— [INFO] BUILD SUCCESSFUL [INFO] ———————————————————————— [INFO] Total time: 3 seconds [INFO] Finished at: Tue Jul 28 15:30:21 PDT 2009 [INFO] Final Memory: 12M/80M [INFO] ————————————————————————

2. Run it using the pre-configured Jetty plugin as:
   

   ~/samples/wicket/helloworld >mvn jetty:run [INFO] Scanning for projects… [INFO] Searching repository for plugin with prefix: ‘jetty’. [INFO] ———————————————————————— [INFO] Building quickstart [INFO]    task-segment: [jetty:run] [INFO] ———————————————————————— [INFO] Preparing jetty:run [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 2 source files to /Users/arungupta/samples/wicket/helloworld/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 2 source files to /Users/arungupta/samples/wicket/helloworld/target/test-classes [INFO] [jetty:run] [INFO] Configuring Jetty for project: quickstart [INFO] Webapp source directory = /Users/arungupta/samples/wicket/helloworld/src/main/webapp [INFO] Reload Mechanic: automatic [INFO] Classes = /Users/arungupta/samples/wicket/helloworld/target/classes 2009-07-28 15:31:35.820::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog [INFO] Context path = /helloworld [INFO] Tmp directory =  determined at runtime [INFO] Web defaults = org/mortbay/jetty/webapp/webdefault.xml [INFO] Web overrides =  none . . . INFO  – WebApplication             – [WicketApplication] Started Wicket version 1.3.6 in development mode ******************************************************************** *** WARNING: Wicket is running in DEVELOPMENT mode.              *** ***                               ^^^^^^^^^^^                    *** *** Do NOT deploy to your live server(s) without changing this.  *** *** See Application#getConfigurationType() for more information. *** ******************************************************************** 2009-07-28 15:31:37.333::INFO:  Started [email protected]:8080 [INFO] Started Jetty Server

   And the default web page is available at “http://localhost:8080/helloworld” and looks like:

   

   A later blog will show how to run this application using Embedded GlassFish. But for now lets package the application as a WAR file and deploy it on GlassFish.

3. Download GlassFish v3 Preview and unzip.
4. Create a WAR file as:
   

   ~/samples/wicket/helloworld >mvn package [INFO] Scanning for projects… [INFO] ———————————————————————— [INFO] Building quickstart [INFO]    task-segment: [package] . . . [INFO] Processing war project [INFO] Webapp assembled in[494 msecs] [INFO] Building war: /Users/arungupta/samples/wicket/helloworld/target/helloworld-1.0-SNAPSHOT.war [INFO] ———————————————————————— [INFO] BUILD SUCCESSFUL [INFO] ———————————————————————— [INFO] Total time: 6 seconds [INFO] Finished at: Tue Jul 28 15:35:59 PDT 2009 [INFO] Final Memory: 14M/80M [INFO] —————————————— ——————————

   and deploy as:

   ~/samples/wicket/helloworld >~/tools/glassfish/v3/preview/glassfishv3/bin/asadmin deploy target/helloworld-1.0-SNAPSHOT.war Command deploy executed successfully.

   The app is now accessible at “http://localhost:8080/helloworld-1.0-SNAPSHOT” and looks like:

   

Cool, that was pretty straight forward!

Now that’s a very vanilla application but at least shows that Wicket applications can be deployed on GlassFish out-of-the-box. A slightly more complex application will be shared on this blog in future.

Here are some more useful links for Wicket:

• Wicket Quickstart shows how to create a Wicket application and get started easily.
• Wicket Examples provide a flavor of how the code is structured.
• Wicket in Action is a great book that explains the concepts very well.
• May want to look at wicket-extensions for a list of gadgets/widgets that extend the core capability of the framework.

A few related blog posts planned:

• Run Wicket application using Embedded GlassFish
• Use Servlet 3.0 web-fragments.xml and leverage GlassFish v3 Pluggability to run Wicket applications
• A Wicket version of Track your running miles application
• Deploying Wicket applications from NetBeans to GlassFish

In the meanwhile, let us know if you are deploying your Wicket applications on GlassFish.

Please leave suggestions on other TOTD that you’d like to see. A complete archive of all the tips is available here.

Technorati: totd wicket glassfish netbeans

Here are some quotes about running Rails applications on GlassFish from user@jruby mailing list:

I find the glassfish gem to be the most performant of all — and I don’t need to war-up my app.

I also have some mongrel cluster stuff, but glassfish is simpler and just works.

Voila…blazing speed, can handle lots of traffic. Note that I am also cominging into apache from a dyndns name. So, whatever IP I have, I can go straight to execution on the glassfish gem and NO warring up! What could be easier deployment, or a faster execution?

It’s running fantasticly and performing like nothing I’ve seen before Completely stable memory, no wirings or anything bad for 5 days now.. (with several ab/htperf stresstests).

It’s always exciting to get good endorsements of our efforts in the GlassFish team

Other similar stories for using Rails/GlassFish in production are described at rubyonrails+stories.

Technorati: glassfish v3 gem rubyonrails stories jruby