geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rex Wang (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-4614) Overloaded WSDL operations are not supported
Date Fri, 02 Apr 2010 01:43:27 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rex Wang closed GERONIMO-4614.
------------------------------


closing it

> Overloaded WSDL operations are not supported
> --------------------------------------------
>
>                 Key: GERONIMO-4614
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4614
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.1.4
>            Reporter: Christopher James Blythe
>            Assignee: Jarek Gawor
>            Priority: Blocker
>             Fix For: 2.1.5
>
>
> Performing certification testing for SpecjEnt benchmark on Geronimo 2.1.4, ran in the
following issue.
> 2009-04-03 15:39:16,576 ERROR [Axis2WebServiceContainer] Exception occurred while trying
to invoke service method doService()
> javax.xml.ws.WebServiceException: More than one operation found. Overloaded WSDL operations
are not supported.  WSDL Operation name: {http://session.mfg.ejb.jappserver.spec.org/}checkForRequestedWork
>         at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:172)
>         at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:69)
>         at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:117)
>         at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getOperationDescription(EJBMessageReceiver.java:138)
>         at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(EJBMessageReceiver.java:68)
>         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
>         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
>         at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(Axis2WebServiceContainer.java:404)
>         at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(Axis2WebServiceContainer.java:353)
>         at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:282)
>         at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:217)
>         at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(Axis2WebServiceContainer.java:177)
>         at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:182)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:735)
> 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.


Mime
View raw message