users@glassfish.java.net
Re: RE: Re: Surprising JPA (Toplink) Behaviour (glassfish v1 UR1)
This message
: [
Message body
] [ More options (
top
,
bottom
) ]
Related messages
: [
Next message
] [
Previous message
] [
In reply to
] [
Next in thread
]
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]
From
: <
glassfish_at_javadesktop.org
>
Date
: Sat, 17 Mar 2007 03:25:37 PST
> with the new TopLink is a bug (
https://glassfish.dev.java.net/issues/show_bug.cgi?id=2643
).
I have seen this exception even when application does *not* use ApplicationManaged EMF and ContainerManaged EMF on same PU.
I see this exception when i undeploy the WAR which uses ApplicationManaged EMF only, usually following not clean undeployment because of JarLocking.
I will try and code up a replication.
-Prashant
[Message sent by forum member 'cprashantreddy' (cprashantreddy)]
http://forums.java.net/jive/thread.jspa?messageID=208561
This message
: [
Message body
]
Next message
:
glassfish_at_javadesktop.org: "Re: persistence-unit-ref issue"
Previous message
:
glassfish_at_javadesktop.org: "EclipseLink: Oracle Open Sources TopLink. Any consequences for GlassFish?"
In reply to
:
glassfish_at_javadesktop.org: "Re: RE: Re: Surprising JPA (Toplink) Behaviour (glassfish v1 UR1)"
Next in thread
:
glassfish_at_javadesktop.org: "Re: Surprising JPA (Toplink) Behaviour (glassfish v1 UR1)"
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]