We have a communication problem, im not a native english speaker so
maybe Im not explaining myself well.
I know what the issue is, I'm using threads and using the wrong context,
thats why I dont find the resources.
Since threads shouldnt be used in EJB's I want to change my code to use
the Work Manager API. So what I'm asking is if the worker manager api is
available in tomee, and if there is any documentation for it somewhere,
I have looked for it and havent found anything.
On 5/24/2013 9:48 AM, Romain Manni-Bucau wrote:
it should be available but not sure that's the issue
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/5/24 Fawzib Rojas <[email protected]>
Created a sample and when I ran it, it worked so the problem is on my
side. After looking around is because I'm doing the lookup from a thread
and the context is the wrong one. Looking around for a solution noticed
that threads should not be used in EJBs (didnt knew that), also thet
there's an api for usong threads in EJB, the Worker Manager API. Is that
available in tomee? Googling about it I see a WorkManager class on openejb,
but havent found any samples.
On 5/22/2013 10:15 AM, Romain Manni-Bucau wrote:
do you have a sample reproducing it?
*Romain Manni-Bucau*
*Twitter: @rmannibucau
<https://twitter.com/**rmannibucau<https://twitter.com/rmannibucau>
*
*Blog:
**http://rmannibucau.**wordpress.com/*<http://rmannibucau.wordpress.com/*>
<http://**rmannibucau.wordpress.com/ <http://rmannibucau.wordpress.com/>>
*LinkedIn:
**http://fr.linkedin.com/in/**rmannibucau*<http://fr.linkedin.com/in/rmannibucau*>
*Github: https://github.com/**rmannibucau*<https://github.com/rmannibucau*>
2013/5/22 Fawzib Rojas <[email protected]>
Ok, i renamed them to "java:global/jdbc/MSIM", again works in webapp, not
in EJB. I'll try both "java:openejb/Resource/" and "openejb:Resource/"
I just wanted to have a standard name usable between different
implementations and using the "openejb" ones defeat the purpose.
