Re: WSIF Invocation of document/literal Web Service
Philipp Leitner <[email protected]> Sat, 07 Jul 2007 12:03:24 +0200
| Newsgroups | gmane.comp.apache.webservices.wsif.user |
|---|---|
| Message-ID | <[email protected]> |
Sidenote: I just recognized that I am having the same problems with RPC
and services that take an array of Strings as argument. Is anybody aware
of this problems? Am I doing something wrong here?
/philipp
Philipp Leitner wrote:
> Hi all,
>
> I have deployed a Web Service using Apache Axis2. The service uses
> document/literal with "wrapped" parameter style and provides a few
> simple test methods. You can find the WSDL definitions at
> http://www.mines-of-moria.de/OrderService.wsdl .
>
> I used the Apache Axis (v1) WSDl2Java tool to generate an "interface"
> for the Web Service and tried to invoke this interface using WSIF.
> Unfortunately the following exception is thrown:
>
> Exception in thread "main" org.apache.wsif.WSIFException: Method
> getString(class java.lang.String) was not found in portType
> {http://service.pojo.sample}DADocTestServicePortType
> at
> org.apache.wsif.base.WSIFClientProxy.findMatchingOperation(Unknown Source)
> at org.apache.wsif.base.WSIFClientProxy.invoke(Unknown Source)
> at $Proxy1.getString(Unknown Source)
> at
> at.ac.tuwien.infosys.dsg.dacoss.eval.v2.WSIFRunner.doStringInvocation(WSIFRunner.java:96)
>
> at
> at.ac.tuwien.infosys.dsg.dacoss.eval.v2.WSIFRunner.main(WSIFRunner.java:56)
>
>
> Analogous exceptions are thrown if I try to invoke any other operation
> in this service using WSIF... as you can see in the WSDL as posted above
> the method that WSIF seems not to be finding is available just fine in
> the service ...
>
> I tried to redeploy the same service using rpc/encoded, and with this
> encoding style the WSIF invocation worked smoothly ...
>
> Is there any known limitation with WSIF and document/wrapped ?
>
> thanks,
> philipp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]