axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pankaj Kumar (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-1725) Use of javax.xml.soap.SOAPEnvelope in method signature causes Exception
Date Thu, 16 Dec 2004 19:48:02 GMT
     [ http://nagoya.apache.org/jira/browse/AXIS-1725?page=comments#action_56790 ]
     
Pankaj Kumar commented on AXIS-1725:
------------------------------------

Well, as a developer, I thought SOAPEnvelope (in the Axis User Guide) meant javax.xml.soap.SOAPEnvelope
and not org.apache.axis.message.SOAPEnvelope.

I think it makes sense to stick with the standard javax.xml.soap.SOAPEnvelope for message
style services. This will be in line with other signatures for message style services that
use W3C dom classes. If someone want to use additional capabilities of org.apache.axis.message.SOAPEnvelope
class then they can always to downcast and be aware of the fact that they are using non-standard
capabilities. 

> Use of javax.xml.soap.SOAPEnvelope in method signature causes Exception
> -----------------------------------------------------------------------
>
>          Key: AXIS-1725
>          URL: http://nagoya.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
>     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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message