Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0003773 [Resin] major always 11-19-09 06:09 03-01-10 16:43
Reporter cyttesen View Status public  
Assigned To ferg
Priority normal Resolution fixed  
Status closed   Product Version 3.1.9
Summary 0003773: class-loader for patches/hotfixes seems to have no effect
Description Having configured a <class-loader> section inside the <web-app-default> section like:

  <simple-loader path="${resin.root}/patches/classes"/>
  <tree-loader path="${resin.root}/patches"/>

Using log-level: all, makes Resin print this in jvm-default.log:
[11:33:24.337] {main} resin.home = /opt/dcp/IMS-WebServer/
[11:33:24.338] {main} resin.root = /opt/dcp/IMS-WebCustomerCare/
[11:33:24.338] {main} resin.conf = /opt/dcp/IMS-WebCustomerCare/

Now adding a jar file inside:

Or a class file inside:

Seems to have no effect when running the application. We are using this 'patches' directory to allow hotfixes to be installed. My test/hotfix was simply printing a log message on each request (it was a ServletFilter that was patched).

In the default resin.conf this is configured for the <web-app-default>:
  <tree-loader path="${resin.root}/ext-webapp-lib"/>

Using this directory the same behavior is observed.

I just want to be able to have the hotfix jar/classes in-front of the webapps jar/classes in the classpath.

Any suggestions or help is highly appreciated.


Additional Information
Attached Files

- Relationships

- Notes
03-01-10 16:43


- Issue History
Date Modified Username Field Change
11-19-09 06:09 cyttesen New Issue
03-01-10 16:43 ferg Note Added: 0004509
03-01-10 16:43 ferg Assigned To  => ferg
03-01-10 16:43 ferg Status new => closed
03-01-10 16:43 ferg Resolution open => fixed
03-01-10 16:43 ferg Fixed in Version  => 4.0.6

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.
26 unique queries executed.
Powered by Mantis Bugtracker