How to remove unwanted attributes from SOAPMessage generated XML
I am working with SOAP for the first time and trying to create a Java process that sends SOAP requests to a server. I have tested the requests on SoapUI which was successful, but the requests made from my Java program are failing. When comparing the exact xml between the two, I noticed that the the Java one has this at the top:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
while the SoapUI one that works and uses an imported wsdl file just has this:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
So for some reason, the message I am creating in Java is adding these 3 new attributes to the envelope header and I don't know why. I am using the javax.xml.soap API and my code to generate the SOAPMessage is this standard procedure:
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage soapMessage = messageFactory.createMessage();
When debugging, I placed a breakpoint right after the call to create a message and the SOAPMessage element already contains those unwanted attributes. Does anyone know how to get rid of them? I believe this discrepancy in the envelope is what is causing the Java process to fail while the SoapUI call works just fine.
Thank you
xml soap
asked Nov 11 at 23:16
Jriz908
62
add a comment |
I am working with SOAP for the first time and trying to create a Java process that sends SOAP requests to a server. I have tested the requests on SoapUI which was successful, but the requests made from my Java program are failing. When comparing the exact xml between the two, I noticed that the the Java one has this at the top:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
while the SoapUI one that works and uses an imported wsdl file just has this:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
So for some reason, the message I am creating in Java is adding these 3 new attributes to the envelope header and I don't know why. I am using the javax.xml.soap API and my code to generate the SOAPMessage is this standard procedure:
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage soapMessage = messageFactory.createMessage();
When debugging, I placed a breakpoint right after the call to create a message and the SOAPMessage element already contains those unwanted attributes. Does anyone know how to get rid of them? I believe this discrepancy in the envelope is what is causing the Java process to fail while the SoapUI call works just fine.
Thank you
xml soap
asked Nov 11 at 23:16
Jriz908
62
The attributes you mention are just declarations of namespace prefixes. They should not cause any problems. It would probably help if you post the complete message that you send, and what error you are getting.
– ophychius
Nov 12 at 6:44
add a comment |
I am working with SOAP for the first time and trying to create a Java process that sends SOAP requests to a server. I have tested the requests on SoapUI which was successful, but the requests made from my Java program are failing. When comparing the exact xml between the two, I noticed that the the Java one has this at the top:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
while the SoapUI one that works and uses an imported wsdl file just has this:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
So for some reason, the message I am creating in Java is adding these 3 new attributes to the envelope header and I don't know why. I am using the javax.xml.soap API and my code to generate the SOAPMessage is this standard procedure:
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage soapMessage = messageFactory.createMessage();
When debugging, I placed a breakpoint right after the call to create a message and the SOAPMessage element already contains those unwanted attributes. Does anyone know how to get rid of them? I believe this discrepancy in the envelope is what is causing the Java process to fail while the SoapUI call works just fine.
Thank you
xml soap
asked Nov 11 at 23:16
Jriz908
62
I am working with SOAP for the first time and trying to create a Java process that sends SOAP requests to a server. I have tested the requests on SoapUI which was successful, but the requests made from my Java program are failing. When comparing the exact xml between the two, I noticed that the the Java one has this at the top:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
while the SoapUI one that works and uses an imported wsdl file just has this:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
So for some reason, the message I am creating in Java is adding these 3 new attributes to the envelope header and I don't know why. I am using the javax.xml.soap API and my code to generate the SOAPMessage is this standard procedure:
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage soapMessage = messageFactory.createMessage();
When debugging, I placed a breakpoint right after the call to create a message and the SOAPMessage element already contains those unwanted attributes. Does anyone know how to get rid of them? I believe this discrepancy in the envelope is what is causing the Java process to fail while the SoapUI call works just fine.
Thank you
xml soap
xml soap
asked Nov 11 at 23:16
Jriz908
62
asked Nov 11 at 23:16
Jriz908
62
asked Nov 11 at 23:16
Jriz908
62
asked Nov 11 at 23:16
Jriz908
62
asked Nov 11 at 23:16
Jriz908
62
62
The attributes you mention are just declarations of namespace prefixes. They should not cause any problems. It would probably help if you post the complete message that you send, and what error you are getting.
– ophychius
Nov 12 at 6:44
add a comment |
The attributes you mention are just declarations of namespace prefixes. They should not cause any problems. It would probably help if you post the complete message that you send, and what error you are getting.
– ophychius
Nov 12 at 6:44
The attributes you mention are just declarations of namespace prefixes. They should not cause any problems. It would probably help if you post the complete message that you send, and what error you are getting.
– ophychius
Nov 12 at 6:44
The attributes you mention are just declarations of namespace prefixes. They should not cause any problems. It would probably help if you post the complete message that you send, and what error you are getting.
– ophychius
Nov 12 at 6:44
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254210%2fhow-to-remove-unwanted-attributes-from-soapmessage-generated-xml%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254210%2fhow-to-remove-unwanted-attributes-from-soapmessage-generated-xml%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The attributes you mention are just declarations of namespace prefixes. They should not cause any problems. It would probably help if you post the complete message that you send, and what error you are getting.
– ophychius
Nov 12 at 6:44