Jim Alateras wrote:
I have been able to get axis2 to correctly generate the actionMapping
and outputActionMapping uris in the service.xml and client stub files.
The actionMapping seems to be picked up from the soapAction attribute
in the wsdl:binding section of the wsdl document.
I have been able to get axis2 to correctly generate the actionMapping
and outputActionMapping uris in the service.xml and client stub files.
The actionMapping seems to be picked up from the soapAction attribute in
the wsdl:binding section of the wsdl document.
wsdl:binding
Hi,
When I use wsdl2code to generate my services.xml, stubs and skeletons
how do i control the actionMapping uris that are generated and used in
these files.
For instance the default actionMapping elements generated for my service
are shown below
operation name=SetupStartElement
