You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Freeman Fang (Created) (JIRA)" <ji...@apache.org> on 2012/03/21 06:21:41 UTC

[jira] [Created] (CAMEL-5109) axiom 1.2.12 can't work with abdera 1.1.2

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
            Reporter: Freeman Fang
            Assignee: Freeman Fang


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CAMEL-5109) axiom 1.2.12 can't work with abdera 1.1.2

Posted by "Freeman Fang (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang updated CAMEL-5109:
--------------------------------

    Affects Version/s: 2.8.4
                       2.9.1
    
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CAMEL-5109) axiom 1.2.12 can't work with abdera 1.1.2

Posted by "Freeman Fang (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang resolved CAMEL-5109.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.9.2
                   2.10.0
                   2.8.5

commit fix
http://svn.apache.org/viewvc?rev=1303301&view=rev for trunk
http://svn.apache.org/viewvc?rev=1303304&view=rev for 2.9.x branch
http://svn.apache.org/viewvc?rev=1303306&view=rev for 2.8.x branch
                
> 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.10.0, 2.9.2
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Work started] (CAMEL-5109) axiom 1.2.12 can't work with abdera 1.1.2

Posted by "Freeman Fang (Work started) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-5109 started by Freeman Fang.

> 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
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira