JRuby-Rack 0.9.4 Released


#1

Hi all,

I pushed out JRuby-Rack 0.9.4 this evening. You should be able to use
this version with Rails 2.3 without any of the previously mentioned
workarounds. This release should also be suitable for use with the new
Google AppEngine Java support.

http://jruby-rack.kenai.com/pages/Home

Warbler support for 0.9.4 should follow soon; we want to release gems
of the main JRuby bits so that Warbler versions will be independent of
JRuby and JRuby-Rack versions. Full changelog follows.

Cheers,
/Nick

  • PLEASE NOTE: Prior to 0.9.4, jruby-rack would try to use the java
    servlet session store by default. This caused more confusion than
    it’s worth; so the default Rails cookie session store has been
    reinstated for this release.
  • Upgrade bundled Rack version to 0.9.1
  • Introduce RackLogger, defaults to log to servlet context but can be
    made to point to stdout by setting -Djruby.rack.logging=stdout (for
    Google AppEngine)
  • Detect Rails 2.3 rack machinery and dispatch to it rather than the
    legacy CGI shim.
  • TODO: Still missing a java servlet Rack::Session adapter for Rails
    2.3. Should have it for next release.
  • Update example Rails application to Rails 2.3.2, include bits for
    deployment to Google AppEngine using Warbler.
  • RackApplication-related core Java classes have been insulated from
    the servlet API, so that (parts of) JRuby-Rack can be used outside
    of a servlet container. If your application or library is coupled to
    these classes, you’ll likely be broken with this release. See Nick
    for details.
  • Fix TLD to be more compatible (Fred McHale).
  • Switched main code repository to kenai.com. Github.com still
    available as a mirror and for forking.
  • EXPERIMENTAL: Beginnings of a JMS API (more details to come)
  • REMOVAL: All the goldspike compatibility bits have been removed. You
    should upgrade your application to use a web.xml similar to what
    comes with Warbler.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email