TorqueBox v4.0.0.beta3 Release NotesRelease Date: 2016-06-17 // about 6 years ago
rackgem dependency of
torquebox-webwas loosened in preparation for Rack 2.0.
torquebox jarwas fixed to match based on a more natural
--exclude fooinstead of requiring a leading slash as in
--exclude /foo. The leading slash variant will continue to work as well.
👍 Long-running monitored daemon support was added. When running in a WildFly cluster, the daemons can optionally be singletons (one instance running per cluster). See the API docs for
TorqueBox::Daemonfor more details.
env.each_pairon the Rack environment hash would sometimes only iterate over some of the hash. This is fixed so that it will iterate over the entire hash as expected.
🐎 Our performance-optimized RackEnvironmentHash implemention had a method override that was incompatible with JRuby 220.127.116.11. This has been removed and JRuby versions >= 18.104.22.168 should work again.
java -jar my_torquebox_app.jar -S ...default gems (json, rake, etc) may not have been found or even bundled inside the jar file correctly. Now they are.
The WunderBoss version was bumped to 0.12.1, bringing in newer versions of Infinispan, Undertow, and several other of the underlying libraries. This also allows us to support running inside WildFly 10.0.0.Final.
✅ Integration tests are now run against WildFly 9.0.1.Final and WildFly 10.0.0.Final.
💎 Empty 304 responses sent from a Ruby application were ending up with a
Transfer-Encoding: chunkedheader added and could result in the request hanging for some clients. This was fixed with the WunderBoss upgrade that brought in a newer Undertow version.
Repeated executions of
torquebox warwill no longer cause the generated archive to continually grow in size. We were accidentally including the existing archive inside the new archive every time the command was run.
Previous changes from v4.0.0.beta2
TorqueBox::Loggerclass now provides methods to instantiate new loggers and configure the underlying logging system.
Starting TorqueBox via rackup and specifying a port will no longer throw an error about converting a RubyString to int.
0️⃣ Executable wars and jars will default to the correct RACK_ENV / RAILS_ENV when created with the "-e" or "--envvar" options instead of always defaulting to development.