It's a bit silly to reply after so long, but I was looking over my old
posts and figured I'd tie this one up in case someone else with this
problem stumbles along.
I ran into trouble because we decided to deploy our .war and our
EJB.jar separately and use a remote interface instead of packaging
them together in an .ear. So, I was using @Remote but wanted a
container managed entity manager. This was our first EJB3 project and
while cribbing examples of remote beans I copied the @PersistenceUnit
annotation, which supplied an application managed entity manager, when
I really wanted @PersistenceContext.
It was a totally a boneheaded move on my part, which took way too long
to sort out. Really, it's a wonder the thing worked at all, Glassfish
v3 choked on it, but v2 would deploy and run...
On Thu, Jul 16, 2009 at 12:21 PM, <glassfish_at_javadesktop.org> wrote:
> same problem here, no way to find a solution.
>
> loren_, did you make progress ?
> [Message sent by forum member 'sciacallo' (sciacallo)]
>
> http://forums.java.net/jive/thread.jspa?messageID=356061
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>