DataNucleus JPA implementation was just the first to create a wrapper
over their DataStore interface. I bet Hibernate won't let that stand
for long ( or I question their resolve ). :)
But tapestry should have a good tapestry-jpa just like it does with
tapestry-hibernate anyhow to give people options. JDO is slowly
languishing (sadly because we're still using it), so I would not
encourage people to put too much effort behind JDO, just JPA. :)
Thiago H. de Paula Figueiredo (JIRA) wrote:
[ https://issues.apache.org/jira/browse/TAP5-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697158#action_12697158 ]
Thiago H. de Paula Figueiredo commented on TAP5-634:
----------------------------------------------------
Don't forget that GAA also supports JPA. This is very nice, as I guess it'll be
a easier transition from Hibernate.
Google App Engine Support: disable code that creates new threads
----------------------------------------------------------------
Key: TAP5-634
URL: https://issues.apache.org/jira/browse/TAP5-634
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core, tapestry-ioc
Affects Versions: 5.1.0.3
Reporter: Howard M. Lewis Ship
Right off the bat, the restriction in GAA that no threads be created will
affect a few, small sections of Tapestry.
In the larger scheme of things, a tapestry-googleappengine library may require
a few things:
- Make the GAA services (such as UserService) injectable
- Support for JDO (much like tapestry-hibernate, today)
- Other, unforseen
Also, depending on the license of GAA (and availabilty through Maven) may need
to host such a library at Tapestry360.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
