0

I have the following method that accepts xml and I do some data feeding with the content. I am supposed to return a SOAP message as well, something along these lines:

<ow-e:Envelope revision='2.0' xmlns:ow-e='http://www.url.com/test-envelope'>
   <ow-e:Header>
      <ow-e:Properties>
         <ow-e:SentAt>2004-12-14T13:54:36</ow-e:SentAt>
         <ow-e:Topic>SOME_STRING</ow-e:Topic>
      </ow-e:Properties>
   </ow-e:Header>
</ow-e:Envelope>

So right now what I am doing is the following:

String some_string = "qwe";
String response = "";

response = "<ow-e:Envelope revision='2.0' xmlns:ow-e='http://www.url.com/test-envelope'><ow-e:Header><ow-e:Properties><ow-e:SentAt>2004-12-14T13:54:36</ow-e:SentAt><ow-e:Topic>" + some_string + "</ow-e:Topic></ow-e:Properties></ow-e:Header></ow-e:Envelope>";

return response;

Which is absolutely terrible. Any idea how I can actually make it more bearable? Using a framework is not an option at the moment.

This is the first time I am dealing with SOAP messages/responses and it feels like hell coming from REST. I probably need to create some kind of hierarchy to populate the values correctly, but I am not sure how it can be done just by using Java without any frameworks.

A.J
  • 1,140
  • 5
  • 23
  • 58

1 Answers1

1

You mentioned using frameworks is not an option, but something more lightweight may be available in your platform:

  • JAXB. JAXB allows you to map Java classes to XML representations using annotations. It's far better than doing marshaling and unmarshaling by hand or by concatenating or parsing strings. With properly structured and annotated POJOs, JAXB can handle things for you. You might even be able to cheat and use xjc with your WSDL file to create annotated classes with the -wsdl option (experimental though).
  • SAAJ. Bluntly put, SAAJ is just like a specific builder and parser for SOAP messages. It will handle the structure and namespaces for you. Speaking of which...

... the example you are showing isn't really valid SOAP message. SOAP is a protocol. You need to properly format it and use the right namespaces otherwise you are just returning some XML messages that look like SOAP, but aren't.

Bogdan
  • 23,890
  • 3
  • 69
  • 61
  • Thank you, I will give it a go now. Which one of the two would you say is more simple and has less of a learning curve? I don't see myself doing SOAP again so I would probably just rather choose the one that will take less time learning/implementing. And thank you for the heads up regarding the invalid SOAP, I will make sure to go over that as well. – A.J Apr 27 '21 at 16:36
  • 1
    If you worked with JSON using the Jackson library for example, then JAXB would look more familiar. You just need to get the right Objects to XML mapping right. SAAJ on the other hand has an uglier API but it is less error prone because it deals only with SOAP messages. JAXB might be easier. – Bogdan Apr 27 '21 at 19:53
  • Thanks for the details, will go with JAXB. Accepted the answer – A.J Apr 28 '21 at 07:31