You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsif-user@ws.apache.org by Miguel Alves <mi...@wedoconsulting.com> on 2005/03/30 01:00:58 UTC

Dynamic Invocation with complex types

Hi,
 
I'am trying create a service that invoke any Webservice without knowing
that input/output types. The examples for dynamic invocation only work
with simple types, if I mention any complex type I receive the fowlloing
error
org.xml.sax.SAXException: Deserializing parameter 'return': could not
find deserializer for type {urn:GoogleSearch}GoogleSearchResult

In this case the GoogleSearch type. I know that I could use WSDL2Java to
generate the interfaces and so on...however my problem is that this
should work for any webservice so I can't write any code before invoking
a new service. 

I also tried XSUL, http://www.extreme.indiana.edu/xgws/xsul/ WSIF
implementation and it works fine showing the results without any problem

I guess I can solve this problem by writing a generic deserialization
class, that for example, put the return object in a DOM object. Does
anyone wrote something similiar ?

 

Thanks in Advance

Miguel


Re: Dynamic Invocation with complex types

Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Miguel Alves wrote:

> Hi,
>  
> I'am trying create a service that invoke any Webservice without 
> knowing that input/output types. The examples for dynamic invocation 
> only work with simple types, if I mention any complex type I receive 
> the fowlloing error
>
> org.xml.sax.SAXException: Deserializing parameter 'return': could not 
> find deserializer for type {urn:GoogleSearch}GoogleSearchResult
>
> In this case the GoogleSearch type. I know that I could use WSDL2Java 
> to generate the interfaces and so on...however my problem is that this 
> should work for any webservice so I can't write any code before 
> invoking a new service.
>
> I also tried XSUL, http://www.extreme.indiana.edu/xgws/xsul/ WSIF 
> implementation and it works fine showing the results without any problem
>
> I guess I can solve this problem by writing a generic deserialization 
> class, that for example, put the return object in a DOM object.
>
hi Miguel,

yes that should work and i think somebody worked on something like that 
and posted about it in axis-dev.

HTH,
alek

-- 
The best way to predict the future is to invent it - Alan Kay