Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1293033751.1216056991677.JavaMail.jira@brutus>
Date: Mon, 14 Jul 2008 10:36:31 -0700 (PDT)
From: "Marc Logemann (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Commented: (OPENJPA-659) No state snapshot is available on
 @Embedded class when using runtime enhancement via spring-tomcat-weaver
In-Reply-To: <2073337099.1216056871724.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OPENJPA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613383#action_12613383 ] 

Marc Logemann commented on OPENJPA-659:
---------------------------------------

The problem doesnt occur when relying on build time enhancement via PCEnhancerTask. 

> No state snapshot is available on @Embedded class when using runtime enhancement via spring-tomcat-weaver 
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-659
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-659
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.1.0
>         Environment: Tomcat6, Java6, Mac OS X, Spring 2.5
>            Reporter: Marc Logemann
>
> i am getting this exception:
> org.springframework.orm.jpa.JpaSystemException: No state snapshot is available for instance of type "de.logentis.bwh.model.Payment", but this instance uses state-comparison for dirty detection.; nested exception is <openjpa-1.1.0-r422266:657916 fatal general error> org.apache.openjpa.persistence.PersistenceException...
> Here are the relevant pieces of the casses:
> @Entity
> @Table(name = "orders")
> @VersionColumn(name = "_version")
> public class Order {
> ...
>    @Embedded
>    Payment payment;
> }
> @Embeddable
> public class Payment {
>    @Basic
>    @Enumerated(EnumType.STRING)
>    @Column(name = "paymenttype")
>    PaymentType type;
>    @Column(name = "currency")
>    String currency;
>    @Column(name = "pricing")
>    String pricing;
>    @Column(name = "cost")
>    int cost;
> }
> The point is, persisting is no problem at all, the exception will be thrown by issueing:
> Query query = getEntityManager().createQuery("select o FROM Order o");
> query.getResultList();

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