[
https://issues.apache.org/jira/browse/AXIS2C-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-530.
--------------------------------------
Resolution: Invalid
This looks to be some Java issue, it does not belong here in Axis2/C project
> Controlling scope of classloader
> --------------------------------
>
> Key: AXIS2C-530
> URL: https://issues.apache.org/jira/browse/AXIS2C-530
> Project: Axis2-C
> Issue Type: New Feature
> Environment: All
> Reporter: Oskar Carlstedt
>
> Today classes are loaded in the same classloader as the axis web application.
> This means the default class loader are fetching resources from the axis2
> webapp, not the service archive itself. The most common problem must be
> logging. E.g. commons logging is looking in the classpath for a
> logging.properties file, which in this case defaults to the same classpath as
> the axis2 webapp. A more expected behavour would be to follow the normal
> classloading mechanism of webapps deployed in a webserver, i.e. the leafmost
> classes overrides the classes further down in the classloader hierarchy. More
> exactly, resources in the service archive should be loaded first, then the
> axis webapp, then ...
> I posted the following on nabble:
> http://www.nabble.com/Classloader-Issues-in-Axis2-tf3238521.html#a9004959
> Kind regards
> Oskar Carlstedt
--
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]
