[ 
https://issues.apache.org/jira/browse/SYNAPSE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712542#action_12712542
 ] 

Andreas Veithen commented on SYNAPSE-524:
-----------------------------------------

Adding them to the system classpath will not work, at least not with the 
current way we provide the patches. The reason is that our patches only contain 
individual classes. If we add them to the system classpath, they will not see 
their dependencies which reside in the web app. The patches must be loaded from 
the same class loader from which the original JARs are loaded. In addition 
deploying the patches to the system classloader may have unpredictable impact 
on other applications running on the server (which may use a different version 
of the original JAR!).

> Patches are not applied to the WAR distribution
> -----------------------------------------------
>
>                 Key: SYNAPSE-524
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-524
>             Project: Synapse
>          Issue Type: Bug
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>             Fix For: 1.3
>
>
> I noticed that the patches (e.g. httpcore-nio-4.0-patch-httpcore-193.jar) are 
> bundled with the ZIP distribution, but not with the Web application. This 
> could cause inconsistent behavior between a standalone deployment and a 
> deployment into an application server.
> According to the servlet spec (SRV.9.5 in v2.4), "The Web application class 
> loader must load classes from the WEB-INF/classes directory first, and then 
> from library JARs in the WEB-INF/lib directory." This gives a hint how to 
> bundle these patches into the WAR so that the modified classes have priority.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to