[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884309#action_12884309
]
Andy Jefferson commented on JDO-652:
------------------------------------
For the QueryDSL approach : a user would not have to compile their model
classes before creating the query classes. The compile triggers a visit to the
enhancer processor, which creates the query class source files, and then model
+ query classes are compiled together. A bytecode enhancer is not involved. at.
all. The user can develop their app in an IDE as they normally would ... model
is designed ... and its autocompile triggers creation of query classes ... and
then both can be used in the persistence code.
> 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.
