I guess the container is giving you the same ejb thats why have some state.
2014-03-06 10:42 GMT-06:00 Martin Funk mafulaf...@gmail.com:
Hi again,
still at a very early stage of conquering the domain of TomEE+.
I have a question on javax.ejb.Stateless. In the specs I read that in the
area
Hi
stateless means dont expect the same instance to be used twice (if
you store a value and call twice your ejb the second time the value
can be different).
However it is thread safe (pooled) and it allows you to handle
transaction and security as any ejb
Romain Manni-Bucau
Twitter: @rmannibucau
actually if you stress a bit your app you'll see it is not the case,
in a single threaded case you can be lucky :)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-03-06
Romain, I think there has been some [recent] discussion on this user/mail
list, and I think it was mentioned that there is 3 async thread/instances
in the pool, and/so it may be likely that @Stateless beans may be
used/referenced.
in the past, earlier versions of tomee [1.6.0 final and snapshot
Hi,
such a compact statement, but still a lot to wrap my head around.
My prejudgement was so solid that I didn't bother to search for any
explanations on the net
and good explanations are not that far away:
http://en.wikipedia.org/wiki/Enterprise_JavaBeans#Stateless_Session_Beans
thnx,
Martin
