Mantis - Resin
Viewing Issue Advanced Details
3773 major always 11-19-09 06:09 03-01-10 16:43
cyttesen  
ferg  
normal  
closed 3.1.9  
fixed  
none    
none 4.0.6  
0003773: class-loader for patches/hotfixes seems to have no effect
Having configured a <class-loader> section inside the <web-app-default> section like:

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

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

Now adding a jar file inside:
/opt/dcp/IMS-WebCustomerCare/5.3.0.0_x/patches

Or a class file inside:
/opt/dcp/IMS-WebCustomerCare/5.3.0.0_x/patches/classes

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>:
<class-loader>
  <tree-loader path="${resin.root}/ext-webapp-lib"/>
</class-loader>

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.

Regards,
Christian




Notes
(0004509)
ferg   
03-01-10 16:43   
server/1h61