Web Service Response Format (1.4 JAX/RPC)

Question

Hi, i have built a WS using a JDeveloper wizard to create a Java (1.4 JAX/RPC)Web Service.
The problem is i need to be very specific about the format of the response. A typical response would be something like
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://tempuri.org/">
<env:Body>
<ns0:SubmitMessageResponse>
<ns0:SubmitMessageResult>Response String</ns0:SubmitMessageResult>
</ns0:SubmitMessageResponse>
</env:Body>
</env:Envelope>
This is a perfectly accepted example of XML, however the system that makes the call is not happy with the namespace tags.
does anyone know of a way to format the response so it does not use namespacce tags.
The result would be something similar to
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://tempuri.org/">
<env:Body>
<SubmitMessageResponse>
<SubmitMessageResult>Response String</SubmitMessageResult>
<SubmitMessageResponse>
</env:Body>
</env:Envelope>
I know this can be achieved by generating a web service that complies to the 1.3 standard, ideally i'd like to avoid this. Additionaly, altering the calling system is not an option.
Many thanks
Chris

Answer 1

Hi,
I cannot confirm whether or not this is a known issue or even a defect. Out of instinct I am building Web Services proxies in their own project because it generates artifacts e.g. for the return types that I don't want to see lying around in my Web Services project. So I assume that it is considered best practices to not put them into the same project to avoid file overrides
Frank