No WSIF is not dynamic in that sense. Every schema complex
object must be mapped to a predefined java bean, so that
AXIS can use its bean de/serializer on it.
You could dynamically generate those beans using AXIS
WSDL2Java tool, i.e. 'a la' JSP compilation, but I
guess that's not what you are looking for.
There has been some talks here to give access to the
SOAP message directly, so that you could get a DOM,
but then that makes WSIF API dependent of the provider
(IMHO).
Alternatively, you can dig into AXIS and create a
de/serializer that generates a DOM or some kind of generic
holder (hashmap) from the SOAP messages.
/jog
-----Original Message-----
From: Honorez Dylan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004 9:34 AM
To: [EMAIL PROTECTED]
Subject: RE: Deserialization problems
Yes, I looked at the complexSoap sample, because it uses
document-literal. And before invoking, it makes a mapping, which makes
it not dynamic anymore...
I also tried mapping the response to an object, but that doesn't work.
"Unexpexted element in getIntResponse".
Seems like WSIF is dynamic for rpc-encoded, but not for
document-literal?
Kind regards,
Dylan Honorez,
[EMAIL PROTECTED]
-----Original Message-----
From: Jeff Greif [mailto:[EMAIL PROTECTED]
Sent: woensdag 24 november 2004 15:20
To: [EMAIL PROTECTED]
Subject: Re: Deserialization problems
Have you looked at the DynamicInvoker sample in the WSIF distribution?
Jeff
----- Original Message -----
From: "Honorez Dylan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 24, 2004 2:25 AM
Subject: RE: Deserialization problems
Doesn't making a mapping make it static instead of dynamic? That's just
what I don't want to do. What I want to do is having the BPEL process
invoke any service with WSIF.
