axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Jordahl (JIRA)" <>
Subject [jira] Commented: (AXIS-1725) Use of javax.xml.soap.SOAPEnvelope in method signature causes Exception
Date Wed, 15 Dec 2004 15:09:16 GMT
     [ ]
Tom Jordahl commented on AXIS-1725:

Actually, since this is an Axis specific thing (the message style service signatures), I don't
think I agree this is a bug.  I suppose a case could be made that we could recognize both
classes, but even that might be questionable as the Axis classes are more functional.

> Use of javax.xml.soap.SOAPEnvelope in method signature causes Exception
> -----------------------------------------------------------------------
>          Key: AXIS-1725
>          URL:
>      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
>     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>(
>         at org.apache.axis.description.JavaServiceDesc.checkMessageMethod(JavaSe
>         at org.apache.axis.description.JavaServiceDesc.createOperationForMethod(
>         at org.apache.axis.description.JavaServiceDesc.createOperationsForName(J
>         at org.apache.axis.description.JavaServiceDesc.getSyncedOperationsForNam
> e(
>         at org.apache.axis.description.JavaServiceDesc.loadServiceDescByIntrospe
> ctionRecursive(
>  ... 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:
If you want more information on JIRA, or have a bug to report see:

View raw message