jruby-rack 1.0.6.rc1 → 1.0.6

data/History.txt

@@ -1,12 +1,38 @@
 == 1.0.6 (01/20/11)
 
-- Related to JRUBY-5281 and spaces in the path. Copy jruby.home fix
-  here also. Fixes "no such file to load" LoadErrors for lots of
+- GH#4: Related to JRUBY-5281 and spaces in the path. Copy jruby.home
+  fix here also. Fixes "no such file to load" LoadErrors for lots of
   cases.
 - NOTE: Next release will remove this code from JRuby-Rack completely,
   relying on JRuby to properly determine jruby.home.
 - GH#8: Allow DefaultRackApplicationFactory to use an existing, single
   runtime. (David Calavera)
+- GH#9: Support chunked Transfer-Encoding, allowing for early flush of
+  the output (Alejandro Crosa)
+- Add some new options for handling the Rack body.
+  - If the body object responds to `#call`, then the servlet output
+    stream will be yielded to it.
+  - If the body object responds to `#to_channel`, then JRuby-Rack will
+    copy the channel to the output stream for you. The same happens if
+    the body responds to `#to_inputstream`.
+  - Otherwise, JRuby-Rack follows the standard Rack behavior of
+    calling `#each` on the body and copying the contents to the output
+    stream.
+- GH#7: JavaServletStore: Add missing #exists? and #destroy
+  implementations
+- JRUBY_RACK-38: Don't needlessly raise errors because of client abort
+  exceptions
+- GH#5: Experimental background spooling enabled by
+  `jruby.rack.background.spool` context parameter
+- JRUBY_RACK-39: Proper routing of / => /index.html (if it exists).
+  New config properties `jruby.rack.filter.adds.html` and
+  `jruby.rack.filter.verify.resource.exists` to tweak this behavior.
+- Improved error and environment capture when something goes wrong,
+  e.g., `no such file to load` errors. Now a status dump will be put
+  in the server log. In the future, we may hook up a remote bug
+  submission capture process.
+- Add env['SERVER_SOFTWARE'] to Rack environment.
+- Hack around Bundler bug #1033
 
 == 1.0.5 (01/11/11)
 

data/README.md

@@ -14,7 +14,7 @@ depends on the latest version of JRuby-Rack and ensures it gets placed in
 your WAR file when it gets built.
 
 If you're assembling your own WAR using other means, you can install the
-`jruby-rack` gem. It provides a method to located the jruby-rack jar file:
+`jruby-rack` gem. It provides a method to locate the jruby-rack jar file:
 
     require 'fileutils'
     require 'jruby-rack'
@@ -61,22 +61,9 @@ runtime pool as you wish.
 
 ## For Other Rack Applications
 
-Here's a sample web.xml configuration for a Sinatra application. The
-main difference is to place the rackup script for assembling the
-Rack-based application in the 'rackup' parameter. Be sure to escape
-angle-brackets for XML.
-
-    <context-param>
-      <param-name>rackup</param-name>
-      <param-value>
-        require 'rubygems'
-        gem 'sinatra', '~&gt; 0.9'
-        require './lib/demo'
-        set :run, false
-        set :environment, :production
-        run Sinatra::Application
-      </param-value>
-    </context-param>
+Here's a sample web.xml configuration for a Rack application. The main
+difference is that JRuby-Rack looks for a "rackup" file named
+`config.ru` in `WEB-INF/config.ru` or `WEB-INF/*/config.ru`.
 
     <filter>
       <filter-name>RackFilter</filter-name>
@@ -91,6 +78,23 @@ angle-brackets for XML.
       <listener-class>org.jruby.rack.RackServletContextListener</listener-class>
     </listener>
 
+If you don't have a config.ru or don't want to include it in your web
+app, you can embed it in web.xml as follows (using Sinatra as an
+example). Be sure to escape angle-brackets for XML!
+
+    <context-param>
+      <param-name>rackup</param-name>
+      <param-value>
+        require 'rubygems'
+        gem 'sinatra', '~&gt; 1.0'
+        require './lib/demo'
+        set :run, false
+        set :environment, :production
+        run Sinatra::Application
+      </param-value>
+    </context-param>
+
+
 # Features
 
 ## Servlet Filter
@@ -135,10 +139,10 @@ framework. In the case of Rails, runtimes are pooled. For Merb and
 other Rack applications, a single runtime is created and shared for
 every request.
 
-## Servlet Context Init Parameters
+## JRuby-Rack Configuration
 
-JRuby-Rack can be configured by setting context init parameters in
-web.xml.
+JRuby-Rack can be configured by setting these key value pairs either
+as context init parameters in web.xml or as VM-wide system properties.
 
 - `rackup`: Rackup script for configuring how the Rack application is
   mounted. Required for Rack-based applications other than Rails or
@@ -171,17 +175,26 @@ web.xml.
   `production`.
 - `jruby.rack.logging`: Specify the logging device to use. Defaults to
   `servlet_context`. See below.
-- `jruby.rack.slash.index`: Force rewriting of requests that end in
-  '/' to be passed through to the container as '/index.html'. Default
-  is false, but is turned on for Jetty by default to avoid triggering
-  directory index pages.
+- `jruby.rack.background.spool`: (EXPERIMENTAL) Enable large request
+  bodies to be spooled to a tempfile in the background.
+- `jruby.rack.filter.adds.html`: The default behavior for Rails and
+  many other Ruby applications is to add an .html extension to the
+  resource and attempt to handle it before serving a dynamic request
+  on the original URI. However, this behavior may confuse other
+  servlets in your application that have a wildcard mapping. Defaults to true.
+- `jruby.rack.filter.verify.resource.exists`: If
+  `jruby.rack.filter.adds.html` is true, then this setting, when true,
+  adds an additional check using `ServletContext#getResource` to
+  verify that the .html resource exists. Default is false. (Note that
+  apparently some servers may not implement `getResource` in the way
+  that is expected here, so in that case this setting won't matter.)
 
 ## Logging
 
 JRuby-Rack sets up a delegate logger for Rails that sends logging
 output to `javax.servlet.ServletContext#log` by default. If you wish
-to use a different logging system, set the `jruby.rack.logging`
-context parameter as follows:
+to use a different logging system, configure `jruby.rack.logging` as
+follows:
 
 - `servlet_context` (default): Sends log messages to the servlet
   context.
@@ -193,13 +206,13 @@ context parameter as follows:
   left up to you.
 
 For those loggers that require a specific named logger, set it in the
-`jruby.rack.logging.name` context parameter.
+`jruby.rack.logging.name` option.
 
 # Building
 
 Checkout the JRuby Rack code and cd to that directory.
 
-    git clone git://kenai.com/jruby-rack~main jruby-rack
+    git clone git://github.com/nicksieger/jruby-rack.git
     cd jruby-rack
 
 You can choose to build with either Maven or Rake. Either of the
@@ -214,9 +227,6 @@ The generated jar should be located here: target/jruby-rack-*.jar.
 
 This example shows how to create and deploy a simple Rails app using
 the embedded Java database H2 to a WAR using Warble and JRuby Rack.
-JRuby Rack is now included in the latest release of Warbler (0.9.9),
-but you can build your own jar from source and substitute it if you
-like.
 
 Install Rails and the driver and ActiveRecord adapters for the H2
 database:
@@ -229,7 +239,7 @@ Install Warbler:
 
 Make the "Blog" application
 
-    jruby -S rails blog
+    jruby -S rails new blog
     cd blog
 
 Copy this configuration into config/database.yml:
@@ -248,16 +258,16 @@ Copy this configuration into config/database.yml:
 
 Generate a scaffold for a simple model of blog comments.
 
-    jruby script/generate scaffold comment name:string body:text
+    jruby script/rails generate scaffold comment name:string body:text
 
 Run the database migration that was just created as part of the scaffold.
 
     jruby -S rake db:migrate
 
-Start your application on the Rails default port 3000 using Mongrel/
+Start your application on the Rails default port 3000 using WEBrick
 and make sure it works:
 
-    jruby script/server
+    jruby script/rails server
 
 Generate a custom Warbler WAR configuration for the blog application
 
@@ -310,6 +320,7 @@ The war should be ready to deploy to your Java application server.
   project, Goldspike
 - Chris Neukirchen, for Rack
 - Sun Microsystems, for early project support
+- Engine Yard, for more recent support
 
 [1]: http://caldersphere.rubyforge.org/warbler
 [2]: http://repository.codehaus.org/org/jruby/rack/jruby-rack/

data/lib/jruby/rack/version.rb

@@ -7,6 +7,6 @@
 
 module JRuby
   module Rack
-    VERSION = "1.0.6.rc1"
+    VERSION = "1.0.6"
   end
 end

metadata

@@ -1,8 +1,8 @@
 --- !ruby/object:Gem::Specification 
 name: jruby-rack
 version: !ruby/object:Gem::Version 
-  prerelease: 6
-  version: 1.0.6.rc1
+  prerelease: 
+  version: 1.0.6
 platform: ruby
 authors: 
   - Nick Sieger
@@ -10,7 +10,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-01-25 00:00:00 -06:00
+date: 2011-02-11 00:00:00 -06:00
 default_executable: 
 dependencies: []
 
@@ -27,7 +27,7 @@ files:
   - History.txt
   - LICENSE.txt
   - README.md
-  - lib/jruby-rack-1.0.6.rc1.jar
+  - lib/jruby-rack-1.0.6.jar
   - lib/jruby-rack.rb
   - lib/jruby/rack/version.rb
 has_rdoc: true
@@ -48,13 +48,13 @@ required_ruby_version: !ruby/object:Gem::Requirement
 required_rubygems_version: !ruby/object:Gem::Requirement 
   none: false
   requirements: 
-    - - ">"
+    - - ">="
       - !ruby/object:Gem::Version 
-        version: 1.3.1
+        version: "0"
 requirements: []
 
 rubyforge_project: jruby-extras
-rubygems_version: 1.4.2
+rubygems_version: 1.5.1
 signing_key: 
 specification_version: 3
 summary: Rack adapter for JRuby and Servlet Containers