You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2006/11/03 14:26:17 UTC
[jira] Commented: (AXIS2-1597) WAR deployment on WLS results in
incorrect service configuration
[ http://issues.apache.org/jira/browse/AXIS2-1597?page=comments#action_12446949 ]
Davanum Srinivas commented on AXIS2-1597:
-----------------------------------------
Is this 1.1 Branch/RC2? or HEAD?
> WAR deployment on WLS results in incorrect service configuration
> ----------------------------------------------------------------
>
> Key: AXIS2-1597
> URL: http://issues.apache.org/jira/browse/AXIS2-1597
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.1
> Environment: WLS 9.2
> Reporter: James Shiell
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org