I know a way to do this (but the code is WSIF-based and proprietary, so I can't just post it). I was attempting to answer the OP's question.
There is quite a bit of information on the wsif-user list on this subject. I looked in the archives on marc.theaimsgroup.com and found a few threads using the words "dynamic invoker complex type" The techniques apply to axis also. Jeff ----- Original Message ----- From: "Davanum Srinivas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, May 15, 2004 2:31 PM Subject: Re: Generic invocation with complex document types > Jeff, > > If you can find a simple webservice/wsdl in the wild (one that i can > access) that you'd like to use as an example, i'd be happy to hack > DynamicInvoker to work with it. It'd take me a few days to get to it > and you will have to open an enhancement request in JIRA (with the > wsdl), just so that we don't forget this. > > thanks, > dims > > On Sat, 15 May 2004 12:23:18 -0700, Jeff Greif > <[EMAIL PROTECTED]> wrote: > > > > You would crack the wsdl for the operations. Determine the types of the > > parts (or the elements in doc/lit), find out if they are complex types, and > > if so, register an ElementSerializer or Deserializer (depending on whether > > an input or return part) for the corresponding xml type or element name. > > > > Then you would pass in an Element (or subclass) for each complex input part, > > and get back an Element for each complex return. > > > > Jeff > > > > > > ----- Original Message ----- > > From: "Tom Oinn" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Saturday, May 15, 2004 10:03 AM > > Subject: Re: Generic invocation with complex document types > > > > > Davanum Srinivas wrote: > > > > > > > Tom, > > > > > > > > You will need to traverse the symbol table and register say the > > > > ElementSerializer/ElementDeserializer or your own custom ser/deser > > > > before invoke. It should not be very difficult. > > > > > > Dims, > > > > > > That's what I was guessing but I haven't had much luck finding more > > > information, could you point me in the right direction? I assume you > > > mean to determine in the first stage what type axis is going to want a > > > serializer for and then registering the ElementSerializer explicitly for > > > that type? > > > > > > Cheers, > > > > > > Tom > > > > > > btw - anyone fancy hacking on an open source workflow project? > > > > > > > >
