[
https://issues.apache.org/jira/browse/OPENJPA-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1086.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: It is an idle investigation item.
openjpa-tools only has openjpa-maven-plugin and the fetch-statistics modules,
with no Eclipse tooling, and the metamodel is generated by the annotation
processor. Please reopen if this still happens with OpenJPA 4.x.
> Investigate the effort to integrate metamodel generation and refactoring in
> Eclipse IDE
> ---------------------------------------------------------------------------------------
>
> Key: OPENJPA-1086
> URL: https://issues.apache.org/jira/browse/OPENJPA-1086
> Project: OpenJPA
> Issue Type: New Feature
> Components: tooling
> Reporter: Pinaki Poddar
> Priority: Major
>
> One of the major addition in JPA 2.0 is type-aware Criteria query
> construction. A string-based JPQL can become invalid when a persistent entity
> property changes its name or type, but such error is detected only at
> runtime. On the other hand, for a Criteria query, such an error will be
> detected at compile time.
> This primary usability advantage of Criteria query can really become useful
> in an IDE with refactoring support. The native refactoring support provided
> by IDE though is not sufficient.
> For example, when a persistent property 'xyz' of entity C is renamed to
> 'abc', the native refactoring support will appropriately change all
> references to 'C.xyz' to 'C.abc'. However, a Criteria query is built with
> reference to C_.xyz and *not* C.xyz where C_ is the meta-class corresponding
> to C. Hence, a IDE plugin should expand the footprint of refactoring to
> include C_.xyz when C.xyz changes.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
