"Anderson Jonathan" <[EMAIL PROTECTED]> wrote:...
No longer are we using java2wsdl to simply provide a RMI over http -
the mentality of "take your Java class and expose it as a web
service" should be combated wherever encountered.
I'm slowly understanding the shift that WS-I and document/literal
imply. But I'm left wondering a philosophical point; what value is
SOAP really offering? Why not dispense with Axis entirely and just go
straight to the DOM when implementing a web service?
And I ask the same. Why do we need all the overhead of SOAP, WSDL, and friends when we're just
sending an XML doc back and forth that's going to be interpreted by the receiving part?
(apart from, perhaps, schema validation...)
And in case we want to do this... nobody responded to my somewhat lengthy message from a few
days ago http://marc.theaimsgroup.com/?l=axis-user&m=107913683223407&w=2
Basically... what's the proper, nice and WS-I-sanctified way to return an XML doc withouth having
non-standard "apachesoap:Document" types or stuff like that.
We finally did it using a combination of custom-made WSDL, plus <wsdlFile> deployment tag, plus
a responseFlow handler that changes the operation's returnType to
{http://www.w3.org/2001/XMLSchema-instance}anyType right after the pivot point.
It feels a little hacky though.
BarZ
Nueva forma de conectarse a internet en URUGUAY ------------- Cuanto gasta hoy ? -------------- Tel. 0909.20.30 => Acceso 100% digital 56K! Promocion lanzamiento: $0,10 mas IVA el minuto. =============================================== http://www.internet.com.uy - Internet en serio.
