[jira] Commented: (AXIS2-1597) WAR deployment on WLS results in incorrect service configuration

["James Shiell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AXIS2-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481112 ] 

James Shiell commented on AXIS2-1597:
-------------------------------------

This is a classloader problem. The setup of the second service AAR (version.aar) is failing as the load of /META-INF/services.xml is picking up the services.xml of the previous AAR (which has OrderManagementWS).

This occurs in the called to populateService at ~line 150 of DeploymentEngine.

> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org