You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2011/03/08 22:43:59 UTC
[jira] Commented: (OPENJPA-1956) Add an error message in case of
bad class and/or attribute in fetchPlan.addField(class, field);
[ https://issues.apache.org/jira/browse/OPENJPA-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004238#comment-13004238 ]
Michael Dick commented on OPENJPA-1956:
---------------------------------------
+1. Will take a look when I get a few free cycles.
> Add an error message in case of bad class and/or attribute in fetchPlan.addField(class, field);
> -----------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1956
> URL: https://issues.apache.org/jira/browse/OPENJPA-1956
> Project: OpenJPA
> Issue Type: Improvement
> Components: validation
> Reporter: Jean-Baptiste Briaud - Novlog
>
> 2 persistent classes :
> A
> B extends A.
> A have the primary key : id.
> I was using fetch plan to include id but with the wrong class.
> I badly added a fetch plan for B.class, id.
> id was null, because it was finally not included in the fetch plan.
> This is OK but when I build the fetch plan, why not raising an error message with something like :
> "no attribute id on B".
> It took me ages to find my error.
> After I added the correct fetch plan : A.class, id, everything works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira