Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support (Un)Marshalling of SOAP Headers [SWS-934] #1006

Open
gregturn opened this issue Jan 11, 2016 · 2 comments
Open

Support (Un)Marshalling of SOAP Headers [SWS-934] #1006

gregturn opened this issue Jan 11, 2016 · 2 comments

Comments

@gregturn
Copy link
Member

@gregturn gregturn commented Jan 11, 2016

Marten Deinum opened SWS-934 and commented

Currently it is only allowed to use @SoapHeader on a SoapHeaderElement or a List<SoapHeaderElement>.

We have a custom soap header which is mapped using JAXB. It would be nice for this case if we could use this directly in the method signature ie. @SoapHeader OurCustomHeader header. This would save some code to retrieve it from the SoapHeaderElement and transform it into our own object.


Affects: 2.2.4

@gregturn
Copy link
Member Author

@gregturn gregturn commented Jan 19, 2016

Greg Turnquist commented

Given that this is new functionality, it is out of scope for the 2.3 release.

@gregturn
Copy link
Member Author

@gregturn gregturn commented Jun 9, 2016

Marten Deinum commented

Duplicates: #955 (also by me)

@gregturn gregturn added this to the 3.1 milestone Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.