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

CAMEL-11927 - Improve support for soap header transformations - [Than… #2055

Merged
merged 2 commits into from
Nov 2, 2017

Conversation

onderson
Copy link
Contributor

…ks for the PR - Richard Groote(helping to raise a github PR by onders)]

…ks for the PR - Richard Groote(helping to raise a github PR by onders)]
@richardgroote
Copy link
Contributor

Thanx, for creating the pull request

@onderson
Copy link
Contributor Author

@richardgroote , however I am not sure if this is needed OOTB. Because spring-ws component already allows to have custom filter and bind via messageFilter endpoint option. This seemed t like a custom implementation to me.
I would go with -1 for this PR.

@richardgroote
Copy link
Contributor

Yes, it's possible to define your own message filter. But it would be nice if Apache Camel would support the functionality to transform the soap header before sending the soap message OOTB.

I've seen a lot of use cases by our customers where only adding the headers was not enough.
The soap header contained a lot of extra information when communicating with the external systems.

The solution for our customers was to use the header transformation filter which i supplied in the issue and i thought it might be useful for other users of Apache Camel

@onderson
Copy link
Contributor Author

This was just my first sight. If the community sees the value, it will be good to go. Thanks for the contribution. Keep up the good work

@davsclaus
Copy link
Contributor

You need to update the documentation as well.
https://github.com/apache/camel/blob/master/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc

Also I suggest to add javadoc to that filter class where you say that its using XSLT only, which otherwise can take people by surprise. eg to do some transformation using simpler ways.

@onderson
Copy link
Contributor Author

@richardgroote , do you mind adding javadoc so that we can update PR and have it merged?

@richardgroote
Copy link
Contributor

See issue for the javadoc

@onderson
Copy link
Contributor Author

@richardgroote , thanks. I have not yet found a time slot to reflect your changes. I will try to look and update and possibly merge your changes at the soonest I can. (sorry i am extremely busy with other stuff at the moment.) thanks

@onderson
Copy link
Contributor Author

onderson commented Nov 2, 2017

@richardgroote reflected your changes. @davsclaus wdyt?

@davsclaus
Copy link
Contributor

Yeah this looks fine, thanks

@onderson onderson merged commit e57b19f into apache:master Nov 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants