Does anyone have 1.7.2 working with dropwizard, play or jpa?

[alexander anguiano]

Does anyone have 1.7.2 working with dropwizard, play or jpa? 

Also, I create a single jar and with 1.6.4 my jar was 13meg.  With 1.7.4 it jumped up to 25.5 meg. 

(Sorry for the redundancy , there are several threads in  the forum with no solutions. )

Here's the stack trace i get with dropwizard

INFO: Can't parse 'META-INF/persistence.xml' :Something goes wrong while parsing persistence.xml

Exception in thread "main" javax.validation.ValidationException: HV000041: Call to TraversableResolver.isReachable() thr

ew an exception.

        at org.hibernate.validator.internal.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:1230)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:438)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForDefaultGroup(ValidatorImpl.java:3

87)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:3

51)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:303)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validate(ValidatorImpl.java:133)

        at com.yammer.dropwizard.validation.Validator.validate(Validator.java:58)

        at com.yammer.dropwizard.validation.Validator.validate(Validator.java:40)

        at com.yammer.dropwizard.config.ConfigurationFactory.validate(ConfigurationFactory.java:92)

        at com.yammer.dropwizard.config.ConfigurationFactory.build(ConfigurationFactory.java:64)

        at com.yammer.dropwizard.config.ConfigurationFactory.build(ConfigurationFactory.java:48)

        at com.yammer.dropwizard.cli.ConfiguredCommand.parseConfiguration(ConfiguredCommand.java:83)

        at com.yammer.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:51)

        at com.yammer.dropwizard.cli.Cli.run(Cli.java:53)

        at com.yammer.dropwizard.Service.run(Service.java:61)

        at com.netiq.assets.AssetService.main(AssetService.java:17)

Caused by: java.lang.UnsupportedOperationException: getProviderUtil

        at com.orientechnologies.orient.object.jpa.OJPAPersistenceProvider.getProviderUtil(OJPAPersistenceProvider.java:

80)

        at javax.persistence.Persistence$1.isLoaded(Persistence.java:78)

        at org.hibernate.validator.internal.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.ja

va:57)

        at org.hibernate.validator.internal.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableRes

olver.java:130)

        at org.hibernate.validator.internal.engine.resolver.SingleThreadCachedTraversableResolver.isReachable(SingleThre

adCachedTraversableResolver.java:46)

        at org.hibernate.validator.internal.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:1221)

        ... 15 more

I found this link

https://github.com/orientechnologies/orientdb/wiki/JPA-Configuration

And tried putting a persistent.xml  file and still no luck.

Exception in thread "main" javax.validation.ValidationException: HV000041: Call to TraversableResolver.isReachable() thr

ew an exception.

        at org.hibernate.validator.internal.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:1230)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:438)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForDefaultGroup(ValidatorImpl.java:3

87)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:3

51)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:303)

        at org.hibernate.validator.internal.engine.ValidatorImpl.validate(ValidatorImpl.java:133)

        at com.yammer.dropwizard.validation.Validator.validate(Validator.java:58)

        at com.yammer.dropwizard.validation.Validator.validate(Validator.java:40)

        at com.yammer.dropwizard.config.ConfigurationFactory.validate(ConfigurationFactory.java:92)

        at com.yammer.dropwizard.config.ConfigurationFactory.build(ConfigurationFactory.java:64)

        at com.yammer.dropwizard.config.ConfigurationFactory.build(ConfigurationFactory.java:48)

        at com.yammer.dropwizard.cli.ConfiguredCommand.parseConfiguration(ConfiguredCommand.java:83)

        at com.yammer.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:51)

        at com.yammer.dropwizard.cli.Cli.run(Cli.java:53)

        at com.yammer.dropwizard.Service.run(Service.java:61)

        at com.netiq.assets.AssetService.main(AssetService.java:17)

Caused by: java.lang.UnsupportedOperationException: getProviderUtil

        at com.orientechnologies.orient.object.jpa.OJPAPersistenceProvider.getProviderUtil(OJPAPersistenceProvider.java:

80)

        at javax.persistence.Persistence$1.isLoaded(Persistence.java:78)

        at org.hibernate.validator.internal.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.ja

va:57)

        at org.hibernate.validator.internal.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableRes

olver.java:130)

        at org.hibernate.validator.internal.engine.resolver.SingleThreadCachedTraversableResolver.isReachable(SingleThre

adCachedTraversableResolver.java:46)

        at org.hibernate.validator.internal.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:1221)

        ... 15 more

Thanks

[Carlo Polisini]

It seems you are getting same exception of me, infact getProviderUtil in OJPAPersistenceProvider it'is not implemented and raise an  UnsupportedOperationException("getProviderUtil") whenever is called.

https://groups.google.com/forum/#!topic/orient-database/n03vpYocia4

[alexander anguiano]

I just tried this with 1.7.3 and it still doesn't work.  Is there a way to override this somehow?

[alexander anguiano]

I finally figure out what i have to do to make this work.

My problem is that i don't use jpa but dropwizard was activating the logic.  What you have to do is exclude orientdb-object.  Here are the relevant parts of my maven file

<properties>

<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

<orientdb.version>1.7.7</orientdb.version>

</properties>

<dependencies>

<dependency>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

<version>3.8.1</version>

<scope>test</scope>

</dependency>

<dependency>

<groupId>com.orientechnologies</groupId>

<artifactId>orient-commons</artifactId>

<version>${orientdb.version}</version>

</dependency>

<dependency>

<groupId>com.orientechnologies</groupId>

<artifactId>orientdb-core</artifactId>

<version>${orientdb.version}</version>

</dependency>

<dependency>

 <groupId>com.orientechnologies</groupId>

 <artifactId>orientdb-graphdb</artifactId>

 <version>${orientdb.version}</version>  

<exclusions>

    <exclusion>

      <groupId>com.orientechnologies</groupId>

      <artifactId>orientdb-object</artifactId>

    </exclusion>

  </exclusions> 

 

</dependency>

<dependency>

<groupId>com.orientechnologies</groupId>

<artifactId>orientdb-client</artifactId>

<version>${orientdb.version}</version>

</dependency>

</dependencies>

[Carlo Polisini]

Obviously! All people that are not using Orient-Object can get rid of the problem excluding that jar, but not me since I am using almost exclusively Object database Interface.

--

---
You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/7GbAGtPAPXg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Carlo Polisini

[Yun Zhi Lin]

If you are trying to embed Orient DB into Dropwizard, there an up to date example project here: https://github.com/xvik/dropwizard-orient-server