I'm afraid that you're not going to be able to use hibernate in the way
that you expect to. You're also not going to like the fact that the
hibernate/datanucleus change will be the least of your worries if
converting from a relational database. I advise that if you're serious
about using Google App Engine then you switch your code to using the low
level API or a simple abstraction (such as Objectify or Twig) instead of
JPA or JDO because they'll help you to change your mindset away from the
relational DB model you're use to. If however you're not serious about
using GAE - I recommend that you give up at this point.
Mat.
On 9 February 2012 11:04, oneTETSUO wrote:
> some yrs ago, i developed an gwt and it worked well so far.
>
> now i wanted to connect my backend with a gwt.based.app and ive used
> jpa with hibernate for it. ive compiled the sources so far, to start
> them on a tomcat instance localy, but the datanucleus.provider just
> kicking it out of the way and try to parse and use the persistence.xml
> instead of the hibernate persistence provider. it reminds me very
> strong to the messy overhead of jboss seam, but in another way.
>
> 1. its a deep shit, that one cant develop gwt based app in connection
> to a usual relational database. one is pushed to use fakedate, during
> the development, which makes it not even better.
>
> 2. if it runs on the tomcat, the provider still override the
> configuration, as it wants or what. the persistence.xml shows
>
> org.hibernate.ejb.HibernatePersistence
>
>
> but the result is
>
>
> 11:48:12,551 WARN [DataNucleus.MetaData] - MetaData Parser
> encountered an error in file "file:/home/mschulz/workspace/
> _dwh_frontend/build_two/war/WEB-INF/classes/META-INF/persistence.xml"
> at line 4, column 63 : cvc-complex-type.3.1: Value '2.0' of attribute
> 'version' of element 'persistence' is not valid with respect to the
> corresponding attribute use. Attribute 'version' has a fixed value of
> '1.0'. - Please check your specification of DTD and the validity of
> the MetaData XML that you have specified.
>
>
> no one asked datanucleus to manage the persistence, on which point it
> overtakes the focus on that ? i want to kick it out or should i move
> my whole persistence layer from hibernate to datanucleus, which makes
> another unnecessary workload on this point. if i want to speed it up
> later on, i may use datanucleus for this issue, but actualy i just
> want to develop the business case :/
>
> iam kind of sick to workaround the behaviour of this all the time, the
> plugin should give the oppurtunity to switch/case the usage of
> dependend packages to take the pain away :/ in fact, iam not in the
> scope of gae, its running on tomcat and the appenmgine dependencies
> wont realize this change. its a bit mess, to figure out, on which
> point what is used, coz no log output will give a point to dive into
> the debugger ...
>
> in the past, ill switched workspaces between front/backend
> development, but this isnt the way to work fluently with it, so one
> got an idea, how to merge/hybrid use that case.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> google-appengine-java@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
