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 "Venkat Reddy (JIRA)" <ax...@ws.apache.org> on 2005/04/24 16:17:23 UTC

[jira] Commented: (AXIS-1725) Use of javax.xml.soap.SOAPEnvelope in method signature causes Exception

     [ http://issues.apache.org/jira/browse/AXIS-1725?page=comments#action_63608 ]
     
Venkat Reddy commented on AXIS-1725:
------------------------------------

I think this enhancement involves too deep changes to commit at this time. Getting WSDL in browser is not difficult - can be accomplished by adding an extra case block to the JavaServiceDesc.checkMessageMethod() for handling the javax.xml.soap.SOAPEnvelope. But this not enough. The Call interface on client side doesn't support passing a javax.xml.soap.SOAPEnvelope and the server-side runtime also doesn't support this.

Venkat

> Use of javax.xml.soap.SOAPEnvelope in method signature causes Exception
> -----------------------------------------------------------------------
>
>          Key: AXIS-1725
>          URL: http://issues.apache.org/jira/browse/AXIS-1725
>      Project: Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.2RC2
>  Environment: Encountered on Windows XP, J2SE1.5 but will show up on all platforms
>     Reporter: Pankaj Kumar
>     Assignee: Venkat Reddy
>     Priority: Minor

>
> A message style service implementation file such as
> ---------------------------------------------------
> import javax.xml.soap.SOAPEnvelope;
> public class MessageService {
>     public void process(SOAPEnvelope req, SOAPEnvelope resp){
>     }
> }
> ---------------------------------------------------
> cuases the following Exception (during a View from Browser, after successful deployment):
> INFO: Server startup in 3645 ms
> - Exception:
> java.lang.Exception: Method 'process' does not match any of the valid signatures
>  for message-style service methods
>         at org.apache.axis.InternalException.<init>(InternalException.java:71)
>         at org.apache.axis.description.JavaServiceDesc.checkMessageMethod(JavaSe
> rviceDesc.java:802)
>         at org.apache.axis.description.JavaServiceDesc.createOperationForMethod(
> JavaServiceDesc.java:1184)
>         at org.apache.axis.description.JavaServiceDesc.createOperationsForName(J
> avaServiceDesc.java:1107)
>         at org.apache.axis.description.JavaServiceDesc.getSyncedOperationsForNam
> e(JavaServiceDesc.java:1079)
>         at org.apache.axis.description.JavaServiceDesc.loadServiceDescByIntrospe
> ctionRecursive(JavaServiceDesc.java:929)
>  ... More stuff omitted ...
> Looking at the source file of class org.apache.axis.description.JavaServiceDesc, I( noticed that it imports org.apache.axis.message.SOAPEnvelope and uses SOAPEnvelope.class for matching the argument class. I verified this by replacing "import javax.xml.soap.SOAPEnvelope" with "import org.apache.axis.message.SOAPEnvelope" (the replacement causes the problem to go away).
> As the service developer should use only JAX-RPC interfaces in the method signature, I concluded that this is a bug.

-- 
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