Thanks to the fine guys at MarkLogic, we now have both the User and Dev lists archived.

You may search/browse them collectively here:

• http://torquebox.markmail.org/search/?q=

Or you may browse them individually

• User List
• Developer List

Enjoy!

I’m happy to announce the release of TorqueBox 1.0.0.Beta16.

Go download it and read the docs now.

I’d like to especially thank GertThiel and dmilith (both on #torquebox IRC on freenode) for their input and bug-finding contributions for this release. Gert’s been working on enterprisey cache support using JBoss Cache. Expect to see that integrated in a future upcoming release. He also helped narrow down some bugs involving sessions and Rack integration (TORQUE-38 and TORQUE-39).

Included in this release, though:

Bug

• TORQUE-20 - Ensure task queues fully undeploy
• TORQUE-23 - Fix jobs.yml documentation
• TORQUE-28 - Removing *-rails.yml from $JBOSS_HOME/server/*/deploy does not undeploy the application.
• TORQUE-35 - Specifying context in web.yml causes NPE
• TORQUE-36 - When using a context, relative paths are wrong if a trailing slash is not included
• TORQUE-37 - Rails’ production.log shouldn’t be mixed into JBoss AS’ server.log
• TORQUE-38 - Set Rack’s env[‘REMOTE_ADDR’]
• TORQUE-39 - Servlet-based session-store initialization fails for RAILS_ENV=production

Task

• TORQUE-29 - Create a rails application template
• TORQUE-31 - Support generic Rack frameworks (sinatra, etc) and config.ru

Quick on the heels of 1.0.0.Beta14, I’m happy to announce 1.0.0.Beta15.

Download it and read the documentation now.

First off, this release re-enabled multiple versions of Rails. Feel free to use anything 2.2.2+. This include 2.3.4.

By default the TorqueBox distribution ships with 2.3.4, but you may certainly use others.

Which brings us to some major new functionality: running apps using Rails gems. You no longer have to freeze rails into your app. You certainly may still freeze Rails, and vendor/rails/ will take precedence. Or you can just specify the RAILS_GEM_VERSION variable in your config/environment.rb.

Also, any other gems specified in your environment.rb can be pulled in from the global Gem path.

As usual, rake gems:install will attempt to install your app’s gems into the global Gem path.

The full list of bugs fixed since 1.0.0.Beta14:

• TORQUE-5 - Rails Gem should be loadable from shared JRUBY_HOME-based gempath.
• TORQUE-24 - rails.bat missing
• TORQUE-26 - reset_session fails with nil

After a hiatus while I worked on cloud stuff, we’re back to cranking on TorqueBox.

I’m happy to announce version 1.0.0.Beta14.

Download it and read the documentation.

This release includes only a few changes:

• Fewer gratuitous JRuby runtime instantiations. This shaved ~30s off application deployment time on my laptop
• Standardized on YAML-handling library. This reduces our dependencies by 1.
• Support for public/index.html being served if necessary.
• Re-enabling symlink deployments of RAILS_ROOTs
• Documentation improvements by Jean Deruelle on the telecom/SIP bits

For this release, Rails 2.3.2 is still the recommended version to use. Rails 2.3.3 will work, but controllers will not be reloaded, even in the development environment.

Rails 2.3.4 fails entirely. It appears that in fixing the controller-reloading bug in 2.3.3, they possibly added a thread/mutex bug.

So, stick with 2.3.2, or 2.3.3 if you don’t mind not having your code reload.

The next release will focus on getting us working happily with the latest versions of Rails.

The TorqueBox Ruby application platform has reached 1.0.0.Beta13 and is available now.

This release includes a handful of improvements, including some for hybrid Java/Ruby shops:

• Finer-grained control by supporting web.xml
• Support for jboss-web.xml and *-ds.xml

And some for everyone:

• Runtime pool management for non-threadsafe mode
• Specify context-path when deploying with rake

The list of closed JIRA entries:

Bug

• TORQUE-9 - Torquebox not using config/jboss-web.xml to configure jndi references, etc.

Feature Request

• TORQUE-8 - Allow to specify the deploy context path from the rake task
• TORQUE-10 - Enable JRuby pooling to be configured manually, even with “threadsafe” Rails (2.2+)

Task

• TORQUE-12 - Re-enable RSpec tests
• TORQUE-14 - Document pooling.yml

As always, see the downloads page for all of the downloadable artifacts, and the latest documentation is also available.