[
https://issues.apache.org/jira/browse/GORA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Dobromyslov updated GORA-371:
----------------------------------------
Attachment: gora-jdom-xerces.patch
Attached proposed patch.
> Exception setXIncludeAware UnsupportedOperationException
> --------------------------------------------------------
>
> Key: GORA-371
> URL: https://issues.apache.org/jira/browse/GORA-371
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
> Affects Versions: 0.4, 0.5, 0.6
> Environment: Gentoo Linux, Oracle JDK 1.7.0.51-r1
> Reporter: Viacheslav Dobromyslov
> Attachments: gora-jdom-xerces.patch
>
>
> I've started learning gora-tutorial and created a separate Maven project with
> gora-core and gora-hbase dependencies only.
> When I try to run the project the following exception raises:
> {code}
> Failed to set setXIncludeAware(true) for parser
> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@2662e5cf:java.lang.UnsupportedOperationException
> {code}
> And then found a workaround on the StackOverflow:
> {code}
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> <version>2.11.0</version>
> </dependency>
> </dependencies>
> </dependencyManagement>
> {code}
> Then I looked for the roots of the problem in dependency graph and found out
> that:
> # The same issue was created rarely:
> https://issues.apache.org/jira/browse/GORA-69
> # There was proposed a workaround with <dependencyManagement>
> But Maven dependency graph reflets the real root of the problem:
> # Several Gora modules depending on old org.jdom:jdom-1.1.2 package:
> ** gora-dynamodb
> ** gora-dynamodb
> ** gora-cassandra
> ** gora-cassandra
> ** gora-hbase
> ** gora-mongodb
> ** gora-tutorial
> # jdom-1.1.2 depends on jaxen:jaxen-1.1.3
> # jaxen-1.1.3 depends on xerces:xercesImpl-2.6.2
> # xercesImpl-2.6.2 does not support setXIncludeAware(true) method.
> I propose to solve this issue just upgrading org.jdom:jdom upto 1.1.3 which
> does not pull old xerces 2.6.2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
