geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher James Blythe (JIRA)" <>
Subject [jira] Created: (GERONIMO-4614) Overloaded WSDL operations are not supported
Date Fri, 03 Apr 2009 20:27:13 GMT
Overloaded WSDL operations are not supported

                 Key: GERONIMO-4614
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: webservices
    Affects Versions: 2.1.4
            Reporter: Christopher James Blythe
            Priority: Blocker

Performing certification testing for SpecjEnt benchmark on Geronimo 2.1.4, ran in the following

2009-04-03 15:39:16,576 ERROR [Axis2WebServiceContainer] Exception occurred while trying to
invoke service method doService() More than one operation found. Overloaded WSDL operations
are not supported.  WSDL Operation name: {}checkForRequestedWork
        at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(
        at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
        at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
        at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getOperationDescription(
        at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(
        at org.apache.axis2.engine.AxisEngine.receive(
        at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
        at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(
        at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(
        at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(
        at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(
        at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(
        at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(
        at org.apache.catalina.core.StandardHostValve.invoke(
        at org.apache.catalina.valves.ErrorReportValve.invoke(
        at org.apache.catalina.core.StandardEngineValve.invoke(
        at org.apache.catalina.valves.AccessLogValve.invoke(
        at org.apache.catalina.connector.CoyoteAdapter.service(
        at org.apache.coyote.http11.Http11Processor.process(
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(

Based on some feedback from colleagues, the issues stems from...

the problem was that the application uses 3 levels of inheritence...
interface 1 (annotated web service)
interface 2 (extends interface1, not a web service)
implementor (web service) 

it can handle the 
interface 1 (web service)
implementor (web service)
case, but the non-web-service in the middle caused it to blow up. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message