axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5755) WebMethods from different classes with same name don't work
Date Sun, 17 Apr 2016 16:45:25 GMT


Andreas Veithen commented on AXIS2-5755:

WebSphere uses a modified version of Apache Axis2 that doesn't correspond to any release,
and 1.5.4 is no longer supported. Have you tested this scenario with a recent Axis2 release
distributed by the ASF?

> WebMethods from different classes with same name don't work
> -----------------------------------------------------------
>                 Key: AXIS2-5755
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.5.4
>         Environment: Websphere Application Server 8.5 (fix-version 9)
> Windows 7
>            Reporter: Peter Stockinger
>            Priority: Blocker
>         Attachments:
> There appears to be a problem with the axis2 bundled in IBM Websphere AS 8.5 (I believe
the axis2 version used is 1.5.4).
> We are using JAX-WS annotated services and observe the following problem:
> - Two webservices have both a webmethod with the same name but different parameter- and
return-type (those also being from different namespaces).
> - Deployment works, endpoints are published.
> - If used (eg. with SoapUI) one of the webmethods will work, the other will fail with
the fault "axis2ns1:Server - Internal Error".
> - The log shows a javax.xml.bind.UnmarshalException, hinting that for whatever reason
method A with parameter X expects parameter Y (which belongs to method B)
> If the names of the webmethods are unique it works.

This message was sent by Atlassian JIRA

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

View raw message