I'm curious what type of applications you guys are
using the engine for. We are investigating the JMX route because of the
"normal" EJB rules.
For example, how do manage state? The engine use
we are working toward is going to be a run-all-the-time service. Just
because the engine maybe quite for a given time, I can't have the container
running around trying to kill it off. Now, I admit to being a bit
under-acquainted with J2EE as a whole, but how else does one use/model the
engine? I suppose if your rule base were small enough and a persistent state was
not required for long periods of time, things might be more straight
forward? Comments?
James
|
Title: RE: JESS: JESS & EJB
- RE: JESS: JESS & EJB Eyassu, Daniel
- Re: JESS: JESS & EJB James C. Owen
- RE: JESS: JESS & EJB Moore, David (GXS)
- RE: JESS: JESS & EJB James Patterson
- RE: JESS: JESS & EJB Bryan Talbot
- Re: JESS: JESS & EJB rhalsey007
- Re: JESS: JESS & EJB rhalsey007
- Re: JESS: JESS & EJB rhalsey007
- Re: JESS: JESS &... James Patterson
- Re: JESS: JESS &... kkonaka
- Re: JESS: JE... michel denis @+33.6.72.87.17.50
- Re: JESS: JE... kkonaka
- Re: JESS: JESS &... ejfried
- Re: JESS: JE... rhalsey007