[
https://issues.apache.org/jira/browse/AXIS2-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481125
]
James Shiell commented on AXIS2-1597:
-------------------------------------
Got the bugger.
This occurs if another META-INF/services.xml is accessible on the app-server
classpath. As ClassLoader.getResource(..) will check the parent classloader
first it results in this being read in preference to the service file. Hence
the app-server accessible file is always returned.
Hence you end up with the solutions:
1. Ensure no other META-INF/services.xml are accessible from the app-server CP,
or
2. Override ClassLoader.getResource() in DeploymentClassLoader and ensure the
local CP is checked first.
> WAR deployment on WLS results in incorrect service configuration
> ----------------------------------------------------------------
>
> Key: AXIS2-1597
> URL: https://issues.apache.org/jira/browse/AXIS2-1597
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.1
> Environment: WLS 9.2
> Reporter: James Shiell
> Assigned To: Deepal Jayasinghe
>
> When Axis is deployed as a WAR on WLS 9.2 the service configuration mappings
> in AxisConfiguration appear to be bollocksed.
> I have two services (declared in the following order) - version.aar, and a
> custom Muse service, containing four services in a single service group.
> However, the AxisConfiguration object describes all services as having a
> filename of the version.aar file (full path).
> This breaks Muse, which tries to lookup the muse.xml in the service AAR, only
> to be directed to the wrong one by the configuration.
> This does not occur in an exploded deployment.
--
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]
