[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884423#action_12884423
]
Timo Westkämper commented on JDO-652:
-------------------------------------
Matthew, could you give some code examples how a fluent Query API using the not
implemented Java features could look like?
If I understand correctly it provides only typesafe shortcuts to direct fields
and methods. So you end up with a static metamodel like in JPA 2 Criteria.
Using a static metamodel for query construction is quite verbose as you will
know if you have used JPA 2 Criteria.
> Provision of a statically-typed refactor-friendly query capability for JDOQL
> ----------------------------------------------------------------------------
>
> Key: JDO-652
> URL: https://issues.apache.org/jira/browse/JDO-652
> Project: JDO
> Issue Type: New Feature
> Components: api, specification, tck
> Reporter: Andy Jefferson
> Fix For: JDO 3 maintenance release 1
>
>
> There are various querying capabilities of this type around. JPA2 has its
> Criteria query API. Third party solutions like QueryDSL also exist, in its
> case providing a JDOQL implementation (as well as JPQL, and HQL). We should
> seriously consider introducing something along these lines in the JDO2.4
> timeframe.
> There is a comparison of JPA Criteria with QueryDSL over at
> http://source.mysema.com/forum/mvnforum/viewthread_thread,49
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
