AxiomSoapHeaderElement has no convenient way to access child elements of the header element [SWS-243]

[gregturn]

Jim Cummings opened SWS-243 and commented

If you are using Axiom-based messages and you are trying to inspect complex SOAP header elements (say in an interceptor), then it is not easy to access the child elements of a AxiomSoapHeaderElement.

Ideally the general SoapHeaderElement interface would allow this. But the AxiomSoapHeaderElement does not either. The getAxiomHeaderBlock() method is protected too.

To get access to the underlying Axiom elements you have to go all the up to the AxiomSoapMessage and use getAxiomMessage() and drill down from there.

At a minimum it would be nice if the various AxiomSoap* classes had public methods to access the underlying Axiom elements.

---

Affects: 1.0.2

Issue Links:

• Important classes are package-private [SWS-153] #307 Important classes are package-private

[gregturn]

Arjen Poutsma commented

There is a good reason I made these classes non-public: I cannot guarantee that the interface will stay the same, as new Axiom versions are released. Therefore, I am resolving this as won't fix.

Also, the org.sfrwk.ws.soap package lacks an abstraction for individual elements. We could add this, but that impose large requirements on future implementations (besides SAAJ and Axiom).

[gregturn]

Arjen Poutsma commented

Closing 1.5 M2 issues.