Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <11305772.1186512239176.JavaMail.jira@brutus>
Date: Tue, 7 Aug 2007 11:43:59 -0700 (PDT)
From: "Patrick Linskey (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-137) Perform parameter validation for
 annotated callback methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Linskey updated OPENJPA-137:
------------------------------------

    Fix Version/s:     (was: 1.0.0)

> Perform parameter validation for annotated callback methods
> -----------------------------------------------------------
>
>                 Key: OPENJPA-137
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-137
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: jpa
>            Reporter: Kevin Sutter
>            Priority: Minor
>
> This is a follow-on Issue to OPENJPA-133.  Issue 133 was concerned with properly processing the xml configuration of callback methods.  As I was experimenting with that scenario, I discovered that our processing for annotated callback methods and xml callback methods is not consistent.  While we do parameter validation for the xml-configured callbacks, we do not do any validation of the annotated callback methods.  We just assume that the signature is valid.  An incorrectly configured annotated callback method is not detected until runtime and then the user will get an IllegalArgumentException.  It's good that we eventually catch and log this condition, but if we could do the validation earlier like we do for xml-configured callbacks, the user will know about the problem much earlier in the process.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.