TorqueBox v4.0.0.beta1 Release NotesRelease Date: 2015-06-10 // about 7 years ago
The 'torquebox' gem was missing gem dependencies on 'torquebox-caching' and 'torquebox-messaging'. This has been fixed.
Streaming of responses when not using chunked transfer-encoding is fixed. Previously, the response wouldn't be streamed and only get sent when the response was finished. This impacts Rail's response.stream, SSE, etc. Anything using chunked transfer-encoding worked fine and will continue to work fine.
📦 Bundler wasn't being packaged inside executable jars created with 'torquebox jar' if Bundler was installed in a non-standard $GEM_HOME. The logic now looks at Gem.path instead of Gem.default_path, and thus should respect $GEM_HOME.
Recent versions of Nokogiri will once again work when an app is packaged as a .war and deployed to WildFly.
Passing "--env foo" to the "torquebox war" command no longer results in "NoMethodError: undefined method `=' for nil:Nilclass". Previously, this error would happen anytime you used the "--env" flag unless you also used the "--envvar FOO=BAR" flag to set some environment variable earlier in the command.
🚚 Development moved to the 'master' branch instead of 'torqbox'
✅ The Rack Hijack API has been partially implemented. The only tested use of this is with the
tubesockgem for WebSocket support.
🖨 Print out the host and port that web is listening on when programmatically started with :auto_start set to true.
Wars generated with 'torquebox war' can now be run directly with
java -jar foo.war, just like jars.
📦 Scripts can now be run from inside packaged jar and war files using "-S". Ex:
java -jar my_rails_app.jar -S rake db:migrate