{{ message }}
This repository was archived by the owner on Feb 4, 2024. It is now read-only.
First approach to fix issue #106#107
Merged
Merged
Conversation
Member
Author
Member
danielwegener
added a commit
that referenced
this pull request
Jul 9, 2015
Make soap cxf dependency optional. fixes #106
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is a constant value attached to the exchange if the type of the message is a REST message. Instead of the class, I check for the value in the hashmap.
Found the approach a few weeks ago in a CXF discussion as workaround, so I think it's the best practise how we can solve this.