SDI <http://www.extreme.indiana.edu/%7Easlom/bnp/sdi/> aims exactly to do this - if i have some time i will post examples how to do message as DOM element and XPath manipulations.

thanks,

alek

Jacques-Olivier Goussard wrote:

Can I do this within WSIF?


AFAIK, no, not in the current version.
You have to dig into axis to do this.
I'll probably have to do the same in a
short while, as I've the same problem :)
       /jog



-----Original Message-----
From: Honorez Dylan [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 25, 2004 10:16 AM
To: [EMAIL PROTECTED]
Subject: RE: Deserialization problems


Hi,

Wouldn't it be possible to send the content of the soapmessage back as a
String, containing XML? This in case of document-literal style of
course. And how should I do this? Because I looked at the WSIF code, it
has a separate method of invoking document-literal style, but it's the
axis call that immediately tries to deserialize it, and I can't touch
the call without messing everything up.


Can I do this within WSIF?

Kind regards,
Dylan Honorez,
[EMAIL PROTECTED]

-----Original Message-----
From: Jacques-Olivier Goussard [mailto:[EMAIL PROTECTED] Sent: woensdag 24 november 2004 15:56
To: [EMAIL PROTECTED]
Subject: RE: Deserialization problems


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.



















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



Reply via email to