-
Notifications
You must be signed in to change notification settings - Fork 14
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
Different instance of TextImpl causes XmlAnyTypeImpl to be returned instead of response object #12
Comments
priitliivak
pushed a commit
that referenced
this issue
May 7, 2017
aanikinhotee
pushed a commit
to aanikinhotee/j-road
that referenced
this issue
Oct 11, 2017
aanikinhotee
pushed a commit
to aanikinhotee/j-road
that referenced
this issue
Oct 11, 2017
aanikinhotee
pushed a commit
to aanikinhotee/j-road
that referenced
this issue
Oct 12, 2017
aanikinhotee
pushed a commit
to aanikinhotee/j-road
that referenced
this issue
Oct 12, 2017
aanikinhotee
pushed a commit
to aanikinhotee/j-road
that referenced
this issue
Oct 12, 2017
…h fixes jroad issue nortal#12
Merged
priitliivak
pushed a commit
that referenced
this issue
Oct 12, 2017
* jroad issue #12 fix and version * junit test for StandardXRoadConsumerMessageExtractor, which fixes jroad issue #12 * added more unit tests for StandardXRoadConsumerMessageExtractor, which fixes jroad issue #12 * refactoring StandardXRoadConsumerMessageExtractorTest * changed version back to 4.2.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
In StandardXRoadConsumerMessageExtractor extractData method kehaNode is checked for instanceof com.sun.xml.messaging.saaj.soap.impl.TextImpl
I am getting an instance of com.sun.xml.internal.messaging.saaj.soap.impl.TextImpl.
So instead of response object
XRoadMessage<XmlAnyTypeImpl>
is returned.That causes an error in databaseImpl:
java.lang.ClassCastException: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl cannot be cast to com.nortal.jroad.client....
Maybe kehaNode should be checked for an instance of com.sun.xml.internal.messaging.saaj.soap.impl.TextImpl:
The text was updated successfully, but these errors were encountered: