axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Shiell (JIRA)" <>
Subject [jira] Commented: (AXIS2-1597) WAR deployment on WLS results in incorrect service configuration
Date Fri, 03 Nov 2006 15:42:17 GMT
    [ ] 
James Shiell commented on AXIS2-1597:

Swapping version and the Muse service around results in the correct path and the following
log message:

03-Nov-2006 15:39:23 org.apache.axis2.deployment.DeploymentEngine loadServicesFromUrl
INFO: Two services can not have same name, a service with OrderManagementWS already exists
in the system

This appears to relate to the service group handling, but I haven't dwelved any deeper as
of yet.

> WAR deployment on WLS results in incorrect service configuration
> ----------------------------------------------------------------
>                 Key: AXIS2-1597
>                 URL:
>             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:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message