The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:You cannot spawn threads in EJBs.
What you can do is spawn a master engine thread from a ServletContextListener's start-listening method. That thread can do pretty much whatever it wants, including spawning sub-threads to do work for it as well as sleeping on a synchronized request queue. EJBs and JSF components can then talk to that subsystem using synchronized data methods.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:
I think that - subject to those limitations - you can use local EJB interfaces and not need remote EJB, since it's all in the same webapp/classpath and doesn't need to cross JVM boundaries or anything like that.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:
I'm presuming that you're probably only actively tracking a few users at one time. If you have 1000 users online all at once, you might need something more elaborate, since the memory requirements would be related to the number of users being actively tracked.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:You cannot spawn threads in EJBs.
You also cannot spawn threads in JSF ManagedBeans, Listeners, Validators or any other JSF component. The very concept of an "async Managed Bean" is foreign to how J2EE works. The JSF lifecycle runs under a thread assigned at random from the server's application thread pool and should not attempt to do anything "infinite" or even long-running. JSF methods should execute as quickly as possible, then return.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Hey, check out my mega multi devastator cannon. It's wicked. It makes this tiny ad look weak:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
|