Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <12970778.1192650770579.JavaMail.jira@brutus>
Date: Wed, 17 Oct 2007 12:52:50 -0700 (PDT)
From: "Kevin Sutter (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Created: (OPENJPA-408) Improve error processing for
 openjpa.RuntimeUnenhancedClasses property settings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Improve error processing for openjpa.RuntimeUnenhancedClasses property settings
-------------------------------------------------------------------------------

                 Key: OPENJPA-408
                 URL: https://issues.apache.org/jira/browse/OPENJPA-408
             Project: OpenJPA
          Issue Type: Sub-task
          Components: kernel
    Affects Versions: 1.0.0, 1.0.1, 1.1.0
            Reporter: Kevin Sutter
            Assignee: Kevin Sutter


>From the parent Issue...

o I think the "unsupported" option for the openjpa.RuntimeUnenhancedClasses property is hiding a more meaningful message. For example, if I run with "warn" option, I get the warning message (runtime-optimization-disabled) and a null is returned. In this scenario, the processing continues and then I get this message:

<openjpa-1.1.0-SNAPSHOT-r420667:573398M nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance "..." to
PersistenceCapable failed. Ensure that it has been enhanced.

But, if I run with the "unsupported" option, then the only message I get is the (runtime-optimization-disabled) exception. Although it still indicates an error exists, it's not as clear as the "PersistenceCapable" message. Not sure if we should re-think the "warn" vs "unsupported" argument, or maybe just an update to the message text for (runtime-optimization-disabled).


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