[ https://issues.apache.org/jira/browse/CAMEL-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530303#comment-13530303 ]
Benjamin Truitt commented on CAMEL-5109: ---------------------------------------- This appears to be broken again in Camel 2.10.2. The change the re-introduced this issue was revision 1356481: http://svn.apache.org/viewvc/camel/trunk/parent/pom.xml?r1=1356480&r2=1356481&diff_format=h > axiom 1.2.12 can't work with abdera 1.1.2 > ----------------------------------------- > > Key: CAMEL-5109 > URL: https://issues.apache.org/jira/browse/CAMEL-5109 > Project: Camel > Issue Type: Bug > Affects Versions: 2.8.4, 2.9.1 > Reporter: Freeman Fang > Assignee: Freeman Fang > Fix For: 2.8.5, 2.9.2, 2.10.0 > > > CAMEL-4192 upgrade to axiom 1.2.12, and we have camel-atom feature which use > latest axiom 1.2.12 and abdera 1.1.2 together, however, actually abdera 1.1.2 > need work with axiom 1.2.10. > In org.apache.abdera.parser.stax.util.FOMExtensionIterator(abdera code), it > need use a field currentChild which inherit from > org.apache.axiom.om.impl.traverse.OMAbstractIterator(axiom code), but field > currentChild was removed from axiom 1.2.12, so that we can see exception like > java.lang.NoSuchFieldError: currentChild > at > org.apache.abdera.parser.stax.util.FOMExtensionIterator.hasNext(FOMExtensionIterator.java:74) > at org.apache.abdera.parser.stax.util.FOMList.buffer(FOMList.java:60) > at org.apache.abdera.parser.stax.util.FOMList.size(FOMList.java:77) > As abdera 1.1.2 already the latest version so that I think we need rollback > to axiom 1.2.10 utill next abdera version which can work with axiom 1.2.12 > Btw I believe this is the reason that why CXF still use axiom 1.2.10. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira