axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <>
Subject [jira] Resolved: (AXIS2-1597) WAR deployment on WLS results in incorrect service configuration
Date Thu, 28 Jun 2007 07:04:37 GMT


Deepal Jayasinghe resolved AXIS2-1597.

    Resolution: Fixed

With recent ClassLoader issues this should be fixed by now. I checked this few weeks ago with
URL repo and it worked fine.


> WAR deployment on WLS results in incorrect service configuration
> ----------------------------------------------------------------
>                 Key: AXIS2-1597
>                 URL:
>             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
>             Fix For: 1.3
> 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:
For additional commands, e-mail:

View raw message