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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/06/11 21:19:26 UTC
[jira] Updated: (AXIS2-1597) WAR deployment on WLS results in
incorrect service configuration
[ https://issues.apache.org/jira/browse/AXIS2-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-1597:
-------------------------------------
Priority: Blocker (was: Major)
> 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
> Assignee: Deepal Jayasinghe
> Priority: Blocker
>
> 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