Jos van den Oever wrote:
On Thursday 26 August 2004 20:11, Aleksander Slominski wrote:
Matthieu RIOU wrote:
I was wondering if you plan to include the
functionality of invoking by directly passing the XML
message to send and directly extracting the XML from
the response, without object
serialization/deserialization in WSIF.
absolutely yes and to make things smoother to have also DOM API
implemented on top of WSIFMessage and allow easy execution of XPATH
queries on WSIFMessage as well !
I was wondering if it is now possible to invoke web services by providing all
input as XML. This would be very useful in XML oriented frameworks. I'm
working on code where I have all data in a DOM node and don't want to map to
Java objects and back. I would think that since XML is the language of Web
Services should be very easy. It turns out, however, that it's not easy at
all to do this. Or is WSIF only meant to work from Java objects?
hi Jos,
in ancient times (few years ago) there was big push to hide XML and to
do aggressive XML-Java type-mapping.
now it seems we entered more XML as-it-is friendly era and definitely it
is one of the places where i think WSIF needs improvements - it should
be easy to send XML to any service described in WSDL *regardless* where
it is and what is its binding alas WSIF2 is designed not around XML
Infoset but around Java types that are used internally to make
invocations ...
still i think it should be possible to extend WSIFMessage API to allow
passing DOM object directly as a part (WSIFMessage.setObjectPart(name,
Element)) or even better as i was experimenting with WSIF API n XSUL2:
make WSIFMessage implement DOM::Element or in general terms XML Element
Information Item so you send any XML inside WSIFMessage ...
alek
--
The best way to predict the future is to invent it - Alan Kay
