Hi:
Axis2 .net could publish a PortType with Http-Binding in WSDL.
That's to say: when user write a service business logical, the user could
choose to publish the service interface to be a Soap-Binding Webservice or a
Http-Binding Webservice without changed the definition of java /.net
thanks sergei.
in the case of enterprise where a payload has just one namespace, a prefix
seems redundant.
and yes , the response payload is huge..:(
how does one add a defaultNamespace property for incoming messages?
regards
--
View this message in context:
