geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Created: (GERONIMO-650) POJO ws should not need to implement SEI
Date Fri, 20 May 2005 20:16:11 GMT
POJO ws should not need to implement SEI

         Key: GERONIMO-650
     Project: Geronimo
        Type: Bug
  Components: webservices  
    Versions: 1.0-M3    
    Reporter: David Jencks

I have not investigated the code but based on the following stack trace I doubt we are correctly
implementing ewebsvcs-1_1-mr-spec section

The Service Implementation Bean may implement the Service Endpoint Interface as defined by
the  JAX-RPC Servlet model. The bean must implement all the method signatures of the SEI.
In addition,  a Service Implementation Bean may be implemented that does not implement the
SEI. This  additional requirement provides the same SEI implementation flexibility as provided
by EJB service  endpoints. The business methods of the bean must be public and must not be
static. If the Service  Implementation Bean does not implement the SEI, the business methods
must not be final. The  Service Implementation Bean may implement other methods in addition
to those defined by the SEI,  but only the SEI methods are exposed to the client.  

The app has a POJO implementing the same methods as but not extending the SEI.


12:01:28,427 INFO  [RPCProvider] Tried to invoke method public abstract java.lang.String
throws java.rmi.RemoteException with arguments java.lang.String.  The arguments do not match
the signature.
java.lang.IllegalArgumentException: object is not an instance of declaring class
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.apache.axis.strategies.InvocationStrategy.visit(
        at org.apache.axis.SimpleChain.doVisiting(
        at org.apache.axis.SimpleChain.invoke(
        at org.apache.axis.handlers.soap.SOAPService.invoke(
        at org.apache.geronimo.axis.server.AxisWebServiceContainer.invoke(
        at org.apache.geronimo.webservices.WebServiceContainerInvoker.service(
        at org.apache.geronimo.webservices.POJOWebServiceServlet.service(
        at org.mortbay.jetty.servlet.ServletHolder.handle(
        at org.apache.geronimo.jetty.JettyPOJOWebServiceHolder.handle(
        at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
        at org.mortbay.jetty.servlet.JSR154Filter.doFilter(
        at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
        at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(
        at org.mortbay.jetty.servlet.ServletHandler.handle(
        at org.mortbay.http.HttpContext.handle(
        at org.mortbay.jetty.servlet.WebApplicationContext.handle(
        at org.mortbay.http.HttpContext.handle(
        at org.mortbay.http.HttpServer.service(
        at org.mortbay.http.HttpConnection.service(
        at org.mortbay.http.HttpConnection.handleNext(
        at org.mortbay.http.HttpConnection.handle(
        at org.mortbay.http.SocketListener.handleConnection(
        at org.mortbay.util.ThreadedServer.handle(
        at org.mortbay.util.ThreadPool$

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message