So its more of a using SOAP as a transport layer for an old style xml
based API. e.g. we have a home grown xml (pre-soap) api and have to do
our own http request parsing, but an XFire document-centric api would
allow us to hand off lots of the donkey work to XFire.
Dan Diephouse wrote:
Hi Stuart,
That is more for working with documents over SOAP style services. We
don't have support for REST style queries at the moment. Its definitely
on the TODO list, but hasn't made it up there yet :-). You're welcome to
help though and do some XFire hacking ;-)
- Dan
Stuart Barlow wrote:
Is this how you would put together a REST style api using XFire?
Or am I barking up the wrong tree as I guess that REST requires the
use of HTTP GET, POST, DELETE etc.
Dan Diephouse wrote:
SOA Work wrote:
Hi,
does XFire support document-centric web services?
I mean creating a service without xml-2-java mapping? I want to
access the message like a dom tree or something.
Yes, we support that. Just declare a Document in your operations
instead of some other object:
public void doOperation(Document doc) {
}
thx
Dominik
p.s.: XFire supports 3 different encodings of the message: rpc-lit,
doc-lit and wrapped right?
There would be rpc/envoded which should be avoided (WS-I) and
doc-encoded which normally isn't used
Correct. We don't support RPC/encoded as its deprecated by WS-I.
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
--
Stuart
