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 "Alex Grivnin (JIRA)" <ax...@ws.apache.org> on 2005/10/26 18:05:02 UTC
[jira] Updated: (AXIS-2272) Duplicated operation names
[ http://issues.apache.org/jira/browse/AXIS-2272?page=all ]
Alex Grivnin updated AXIS-2272:
-------------------------------
Attachment: axis.zip
Spring source files that install web service beans.
> Duplicated operation names
> --------------------------
>
> Key: AXIS-2272
> URL: http://issues.apache.org/jira/browse/AXIS-2272
> Project: Apache Axis
> Type: Bug
> Components: WSDL processing
> Versions: 1.2.1
> Environment: Server - jakarta tomcat 5.0.28, spring framework 1.2.5
> OS - Windows server 2003
> Java - java full version "1.4.2_07-b05"
> Client - Macromedia flex running in MS IE 6.0
> Reporter: Alex Grivnin
> Attachments: axis.zip
>
> Axis generates invalid WSDL - more specifically operation names appears to be duplicated in WSDL.
> This happens sporadically and I do not have a specific scenario to reproduce it. But I'll try to describe the application flow and may be it will provide some hint...
> Our application runs on a Tomcat server 5.0.28, it uses spring framework 1.2.5 for binding Axis beans which are exposed to the client. See wsdd fragment at the end of the message as well as spring context.
> At some point client (Macromedia flesh) requests wsdl before calling a web service and gets an exception that fetched WSDL is not supported (as it contains duplicated operation names).
> Configuration files:
> --------------------------
> ------- WSDD fragment ----------
> <service name="filtersWS" provider="Handler" style="java:RPC">
> <parameter name="handlerClass" value="com.mercury.onyx.client.services.axis.SpringBeanRPCProvider"/>
> <parameter name="methodName" value="deleteFilter,getFilter,saveUserFilter,getUserViews,getUserFilterCategories"/>
> <parameter name="springBean" value="filtersWS"/>
> <beanMapping languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterCategoryVO" qname="ns3:FilterCategoryVO" xmlns:ns3="someNamespace"/>
> <beanMapping languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterVO" qname="ns3:FilterVO" xmlns:ns3="someNamespace"/>
> <beanMapping languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterDefinitionVO" qname="ns3:FilterDefinitionVO" xmlns:ns3="someNamespace"/>
> <beanMapping languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterConstraintVO" qname="ns3:FilterConstraintVO" xmlns:ns3="someNamespace"/>
> <beanMapping languageSpecificType="java:com.mercury.onyx.client.services.vo.ViewVO" qname="ns3:ViewVO" xmlns:ns3="someNamespace"/>
> <beanMapping languageSpecificType="java:com.mercury.onyx.client.services.vo.AttributeVO" qname="ns3:AttributeVO" xmlns:ns3="someNamespace"/>
> </service>
> ------- End of WSDD fragment ----------
> ------- Spring bean context -------------
> <bean id="filtersWS" class="com.mercury.onyx.client.services.webservices.FiltersWS">
> <property name="filterDAO">
> <ref bean="filterDAO"/>
> </property>
> <property name="viewDAO">
> <ref bean="viewDAO"/>
> </property>
> <property name="userDAO">
> <ref bean="userDAO"/>
> </property>
> </bean>
> ------- End of Spring bean context -------------
--
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