thanks. i'd like to report that using a maven exclusion for the orientdb-object artifact seems to solve the problem (but I am unsure if it is needed somewhere since it comes with the orientdb-graph maven).
On Friday, February 13, 2015 at 3:46:47 PM UTC+1, xvik wrote: > > I faced objectdb - validator issue too and solved it with simple hack. > Please read javadoc for problem/solution description > > https://github.com/xvik/dropwizard-orient-server/blob/master/src/main/java/ru/vyarus/dropwizard/orient/OrientServerBundle.java#L84 > > пятница, 13 февраля 2015 г., 20:21:35 UTC+6 пользователь Aris Alexis > написал: >> >> any update on this? i am using the hibernate validator for other reasons >> in my program. i use maven >> >> INFO: Can't parse 'META-INF/persistence.xml' :Something goes wrong while >> parsing persistence.xml >> >> i get this message since i started using orient. i tried to exclude >> orientdb-object but i still get it. >> >> >> On Tuesday, June 10, 2014 at 1:53:58 PM UTC+2, alexander anguiano wrote: >>> >>> I don't use play, but i saw your threads. I also don't use jpa. I'm >>> using dropwizard that uses hibernate for validation. The hibernate in >>> dropwizard is somehow causing the jpa to activate. I have no fix for >>> this. >>> >>> On Tuesday, June 10, 2014 2:54:18 AM UTC-5, Carlo Polisini wrote: >>>> >>>> Thanks Alexander, are you also using Orient with Play? How did you >>>> remove jpa2 ? I do not have dependencies in Maven, or you are just telling >>>> that you do not use jpa annotations and so the jpa features. >>>> >>>> In Play the problem happens when you bind a request to a Form object >>>> that is jpa annotated, therefore I going to do manual binding and check >>>> manually the constraints to solve this problem. >>>> >>>> On Monday, June 9, 2014 10:36:06 PM UTC+2, alexander anguiano wrote: >>>>> >>>>> I'm having this problem too. How do i fix it? i don't use jpa2 >>>>> >>>>> On Monday, June 9, 2014 11:14:33 AM UTC-5, Carlo Polisini wrote: >>>>>> >>>>>> I upgraded to OrientDB 1.7.1 but still I have this problem. I >>>>>> realized that is due to the fact that OrientDB now come with JPA 2.0 >>>>>> support and Play is trying to use this interface, the exception is >>>>>> raised >>>>>> when any Validation on a Bean is performed by Play Framework through >>>>>> the SpringValidatorAdapter, at aa certain point it is calling the >>>>>> method getProviderUtil in OJPAPersistenceProvider that is not >>>>>> implemented >>>>>> and raise an UnsupportedOperationException("getProviderUtil"). >>>>>> >>>>>> So, I am asking if not implemeting this method of PersistenceProvider >>>>>> interface is a temporary solution in OrientDB or it will be permanent. >>>>>> >>>>>> PS >>>>>> I also opened time ago a cross post on Play Framework group to >>>>>> understand if would be possible to override the default Validation >>>>>> settings >>>>>> but still no solution >>>>>> https://groups.google.com/forum/#!topic/orient-database/Mtk8pRD3TxI >>>>>> >>>>>> On Friday, March 14, 2014 3:09:47 PM UTC+1, Carlo Polisini wrote: >>>>>>> >>>>>>> I am using Play 2.2.1 with OrientDB (www.orientdb.org). >>>>>>> After upgrading the Java drivers of OrientDB from 1.4.1 to 1.6.1 >>>>>>> (and then also to 1.7-rc2) I get a javax.validation.ValidationException >>>>>>> whenever >>>>>>> Form.bindFromRequest() (a Play API) is called. >>>>>>> >>>>>>> The stacktrace is: >>>>>>> >>>>>>> [info] c.o.o.o.j.OJPAPersistenceProvider - Can't parse >>>>>>> 'META-INF/persistence.xml' :Something goes wrong while parsing >>>>>>> persistence.xml >>>>>>> [error] play - Cannot invoke the action, eventually got an error: >>>>>>> javax.validation.ValidationException: HV000041: Call to >>>>>>> TraversableResolver.isReachable() threw an exception. >>>>>>> [error] application - >>>>>>> >>>>>>> ! @6gd13a6b7 - Internal server error, for (POST) >>>>>>> [/1/users/password/forgot] -> >>>>>>> >>>>>>> play.api.Application$$anon$1: Execution >>>>>>> exception[[ValidationException: HV000041: Call to >>>>>>> TraversableResolver.isReachable() threw an exception.]] >>>>>>> at play.api.Application$class.handleError(Application.scala:293) >>>>>>> ~[play_2.10.jar:2.2.1] >>>>>>> at play.api.DefaultApplication.handleError(Application.scala:399) >>>>>>> [play_2.10.jar:2.2.1] >>>>>>> at >>>>>>> play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$2$$anonfun$applyOrElse$3.apply(PlayDefaultUpstreamHandler.scala:261) >>>>>>> >>>>>>> [play_2.10.jar:2.2.1] >>>>>>> at >>>>>>> play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$2$$anonfun$applyOrElse$3.apply(PlayDefaultUpstreamHandler.scala:261) >>>>>>> >>>>>>> [play_2.10.jar:2.2.1] >>>>>>> at scala.Option.map(Option.scala:145) [scala-library.jar:na] >>>>>>> at >>>>>>> play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$2.applyOrElse(PlayDefaultUpstreamHandler.scala:261) >>>>>>> >>>>>>> [play_2.10.jar:2.2.1] >>>>>>> Caused by: javax.validation.ValidationException: HV000041: Call to >>>>>>> TraversableResolver.isReachable() threw an exception. >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.ValidatorImpl.isReachable(ValidatorImpl.java:1316) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:1292) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:475) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForDefaultGroup(ValidatorImpl.java:424) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:388) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:340) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> Caused by: java.lang.UnsupportedOperationException: getProviderUtil >>>>>>> at >>>>>>> com.orientechnologies.orient.object.jpa.OJPAPersistenceProvider.getProviderUtil(OJPAPersistenceProvider.java:80) >>>>>>> >>>>>>> ~[orientdb-object-1.6.1.jar:1.6.1] >>>>>>> at javax.persistence.Persistence$1.isLoaded(Persistence.java:78) >>>>>>> ~[hibernate-jpa-2.0-api-1.0.0.Final.jar:1.0.0.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:56) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableResolver.java:130) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.resolver.SingleThreadCachedTraversableResolver.isReachable(SingleThreadCachedTraversableResolver.java:46) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> at >>>>>>> org.hibernate.validator.internal.engine.ValidatorImpl.isReachable(ValidatorImpl.java:1307) >>>>>>> >>>>>>> ~[hibernate-validator.jar:5.0.1.Final] >>>>>>> [info] c.o.o.o.j.OJPAPersistenceProvider - Can't parse >>>>>>> 'META-INF/persistence.xml' :Something goes wrong while parsing >>>>>>> persistence.xml >>>>>>> [info] c.o.o.o.j.OJPAPersistenceProvider - Can't parse >>>>>>> 'META-INF/persistence.xml' :Something goes wrong while parsing >>>>>>> persistence.xml >>>>>>> >>>>>>> so seems that OrientDB force the update of some Hibernate libraries, >>>>>>> I did a comparison of the dependency list but still cant figure out why >>>>>>> updated version of hiberante/JPa library gives me that error. >>>>>>> >>>>>>> only differences are: >>>>>>> >>>>>>> .classpath for orientDB 1.4.1: >>>>>>> >>>>>>> <classpathentry kind="lib" >>>>>>> path="/home/carlo/opt/play/framework/../repository/cache/ >>>>>>> *net.java.dev.jna/jna/jars/jna-3.5.2.jar*"/> >>>>>>> <classpathentry kind="lib" >>>>>>> path="/home/carlo/opt/play/framework/../repository/cache/ >>>>>>> *net.java.dev.jna/platform/jars/platform-3.5.2.jar*"/> >>>>>>> - <classpathentry kind="lib" >>>>>>> path="/home/carlo/opt/play/framework/../repository/cache/ >>>>>>> *org.xerial.snappy/snappy-java/bundles/snappy-java-1.0.5.jar*"/> >>>>>>> >>>>>>> .classpath for OrientDB 1.6.1 and above: >>>>>>> >>>>>>> <classpathentry kind="lib" >>>>>>> path="/home/carlo/opt/play/framework/../repository/cache/ >>>>>>> *net.java.dev.jna/jna/jars/jna-4.0.0.jar*"/> >>>>>>> <classpathentry kind="lib" >>>>>>> path="/home/carlo/opt/play/framework/../repository/cache/ >>>>>>> *net.java.dev.jna/jna-platform/jars/jna-platform-4.0.0.jar*"/> >>>>>>> + <classpathentry kind="lib" >>>>>>> path="/home/carlo/opt/play/repository/local/ >>>>>>> *net.java.dev.jna/platform/3.4.0/jars/platform.jar*"/> >>>>>>> >>>>>> -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
