Permalink
Commits on Mar 27, 2012
  1. TORQUE-738: Basic rails 3.2.2 app with netty.jar in the root and app/…

    …services
    
    with appropriate config/application.rb modifications.  Does not fail.
    
    See spec/rails_break_jar_spec.rb integration test.
    bobmcwhirter committed Mar 27, 2012
Commits on Mar 26, 2012
  1. [TORQUE-744] Ensure that both torquebox_init.rb and

    config/torquebox_init.rb are required for new runtimes.
    lance committed Mar 26, 2012
Commits on Mar 21, 2012
  1. TORQUE-743 Add config/torquebox.yml to template.rb. Tweak how we adju…

    …st the template with build info
    lance committed Mar 21, 2012
Commits on Mar 20, 2012
Commits on Mar 19, 2012
  1. [TORQUE-727] Document how to create a new Rails application with an a…

    …lternate version of Rails.
    lance committed Mar 19, 2012
  2. Limit defaultVisitNode's injection depth (TORQUE-733)

    We're using the indentLevel logic already in place to limit injection
    depth to 100 recursions into defaultVisitNode. I tried several apps
    and we none had a depth larger than 15, so 100 should be plenty of
    headroom for apps injecting deep inside code blocks.
    
    This is mainly a safety net so injection analysis doesn't take forever
    and blow the stack on very deeply nested code.
    bbrowning committed Mar 19, 2012
Commits on Mar 16, 2012
  1. Fixes for TORQUE-723 (jobs in modules via torquebox.rb) and TORQUE-73…

    …9 (config arrays dying).
    bobmcwhirter committed Mar 16, 2012
Commits on Mar 14, 2012
  1. Verify injection works from Padrino controllers (TORQUE-734)

    The key is to make sure to include TorqueBox::Injectors in the Padrino
    controller. It's a by-product of how our injection analysis works that
    each file needs the include statement even if a class inherits or
    extends another class that has already included TorqueBox::Injectors.
    bbrowning committed Mar 14, 2012
Commits on Mar 13, 2012
  1. Don't fail a deployment if we can't parse database.yml (TORQUE-728)

    We just log a warning that XA won't be enabled and let the deployment
    continue. The only known case where this should happen is when a
    database.yml contains ERB code.
    bbrowning committed Mar 13, 2012
  2. Only enable XA for current environment's database (TORQUE-732)

    If an application uses multiple databases, 'xa: true' will need to be
    set in the database.yml for the database entries that don't match the
    current environment (typically one of development/test/production).
    bbrowning committed Mar 13, 2012
Commits on Mar 12, 2012
  1. TORQUE-724 Fix task concurrency issues with newrelic being included m…

    …ultiple times. Thanks msavy
    lance committed Mar 12, 2012
Commits on Mar 9, 2012
  1. [TORQUE-731] Allows services and jobs to receive configuration

    options when specified in a config block.
    lance committed Mar 9, 2012
  2. fixes for TORQUE-729

    dobozysaurus committed Mar 9, 2012
Commits on Mar 7, 2012
Commits on Mar 2, 2012
Commits on Mar 1, 2012
  1. Add "app/", "models/", and "." to the default injection paths (TORQUE…

    …-721)
    
    This lets any runtime use objects under these paths with injections.
    
    This also required adding some additional logic to ensure services
    can't inject each other and end up in a circular dependency.
    bbrowning committed Mar 1, 2012