Hi, everyone.
There was a long discussion when this problem was brought up. Has there
been any resolution on a fix?
In using the new EmbeddedTomcat submission, this problem is enhanced.
Instead of having to add JNDI entries to the root bean (the one invoked
on entering the container), the JNDI entries must be added to those of
the web application (in web.xml).
This may be due to some of the JNDI integration work I've done, but I
think my problem would be solved if it was fixed in jBoss.
If there is something (quick and dirty or not) that I can do to fix this
problem, I would appreciate a description.
Thanks!
> -----Original Message-----
> From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 11, 2000 4:17 PM
> To: jBoss User List
> Subject: [jBoss-User] JNDI Problem
>
>
> I've got a session bean that changes an entity bean.
> The session
> bean has no data sources defined, though the entity does.
> When my call to
> the session finishes, the TxCapsule calls the
> EntitySynchronizationInterceptor which calls the BMPPersistenceManager
> which calls store on the entity. When the entity tries to
> look up its DB
> pool to get a connection, it fails. However, if I add a resource
> reference to the session bean, then the entity succeeds. So
> it looks like
> the java:comp/env environment is not being reset to that of the entity
> when the entity is stored - it stays set to the session bean's
> environment. Any thoughts?
>
> Thanks,
> Aaron
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
