[ 
http://issues.apache.org/jira/browse/AXIS-2272?page=comments#action_12360597 ] 

Jason Weiss commented on AXIS-2272:
-----------------------------------

Tom,

Yes, WSDL 1.1 supports overloaded operations, however; as you can see in my 
pasted Java code- I don't have an overloaded operation.  I have 1 method.  1 
Method that results in WSDL that says I have *two* insert methods.  Clearly, a 
bug.  

package com.cynergysystems.training;

import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.SQLException;

import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;

public class IdeaImpl
{
        
        public void insert(IdeaBean bean) throws SQLException
        {
                try
                {
                        Context ctxt = new InitialContext();
                        DataSource ds = (DataSource) 
ctxt.lookup("java:comp/env/jdbc/Cynergy");
                        Connection conn = ds.getConnection();
                        conn.setAutoCommit(true);
                        
                        PreparedStatement pstmt = conn.prepareStatement("insert 
into training_idea values (null,?,?,?)");
                        pstmt.setInt(1, bean.getCategoryId());
                        pstmt.setString(2, bean.getTopic());
                        pstmt.setString(3, bean.getDescription());
                        pstmt.execute();
                        
                        conn.close();
                } catch (SQLException sqle)
                {
                        sqle.printStackTrace();
                        throw sqle;
                } catch (NamingException e)
                {
                        e.printStackTrace();
                        throw new SQLException(e.getMessage());
                }
        }

}



> 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

Reply via email to