[TORQUE-1012] Eager loading for messaging is not working with ruby DSL and a shared pool
Ensure the major version's incremental directory gets created
Merge remote-tracking branch 'goldmann/TORQUE-1012-shared-pool-eager-loading' into 2x-dev
Merge pull request #141 from goldmann/TORQUE-1004-sendfile-doc

[TORQUE-1004] Document how to enable sendfile support in TorqueBox
Rev stilts/polyglot.
Extend stomp subscriber to provide hash-like access to destination parameters.
Document it.
Make sure we export the Java libs with naming gem to connect remotely
[TORQUE-877] Support for remote message processors

This commit adds back support for remote message processors. See messaging documentation for more info.

To connect to remote host a username and password authentication is required.
To lookup a destination it needs to be exported in the 'jboss/exported' JNDI naming context on the remote host to be visible outside of it.

DSL:

TorqueBox.configure do
  queue "/queue/remotequeue" do
    remote do
      host "somehost:4444"
      username "username"
      password "password"
    end

    processor SimpleProcessor do
      concurrency 2
    end
  end
end

YAML:

queues:
  /queue/remotequeue:
    remote:
      host: "somehost:4444"
      username: "username"
      password: "password"

messaging:
  /queue/remotequeue:
    SimpleProcessor:
      concurrency: 2

Additional changes:

1. Add 'org.projectodd' category to trace log for integs
2. Added documentation
3. Added integration test
4. Updated schema for YAML and DSL
capistrano support set to use sudo to start/stop torquebox with initd control style
[TORQUE-1031] Web contexts should be normalized

Was fixed in polyglot, but adding integration tests here to make sure it works as expexted.