Hi James,

I haven't gotten to the MBeans yet. Do you have any good reference URLs
(tutorials) on them ?

I have downloaded JBoss and Blazix. So far, I have concentrated on porting
samples from
Weblogic stuff to Blazix. There are some minor porting issues, but it is
helping me to
understand the bigger EJB picture (what goes where and how to do it). I am
using Blazix
because my base station is Windows ME and Weblogic does NOT recommend using
it.

I went to Sun and looked at the JMX material, but so far no lights have gone
on as to how to
use it with JESS.

Rich Halsey

----- Original Message -----
From: "James Patterson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 05, 2002 7:48 AM
Subject: Re: JESS: JESS & EJB


> I believe this goes along with the scenario [EMAIL PROTECTED]
> describes a few emails back.  And [EMAIL PROTECTED] has passed along some
> insightful EJB behaviors.  All of this together makes me think JMX is the
> way to go.  So far as I understand, as an MBean, Jess will not be an EJB
and
> therefore will not have a lot of the discussed problems.  However, it will
> live as an extension to the container and therefore be a part of the J2EE
> environment (unlike the external singleton approach).
>
> So, my limited experience with JMX has been with JBoss - has anyone used
> MBean extensions to other app servers?
>
> James
>
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, March 04, 2002 5:27 PM
> Subject: Re: JESS: JESS & EJB
>
>
> >
> > A Rete instance is more like a database than an EJB -- an entity EJB
> > is like a single row of a table in a database. Therefore, my personal
> > opinion (and it's just an opinion, because I've never deployed an
> > EJB-based application) is that Jess should live in a separate server
> > app, perhaps accessed by RMI, in the same way that the database often
> > will.  Clients would contact EJBs, and the EJBs would talk to the
> > "Jess server." A generic Jess server wouldn't be hard to write, and
> > one specific to a given application would be even easier. A simple one
> > might expose only one method: executeCommand()!
> >
> >
> > I think James Patterson wrote:
> > [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > > RE: JESS: JESS & EJBTechnically I don't know the answer. My
> understanding is that a bean's life cycle is like the java GC - each
> implementation can handle it differently.  A good EJB should be service
> orientated - a request comes in, the bean is either instantiated or
reused,
> and then the left for dead.  The container may or may not "destroy" it.
So,
> even though the bsave/bload option is there, it isn't very practical (I
> think) for my problem.  We have potentially, hundreds of rules and 10's of
> thousands of facts (most of which are not short and simple).  Most
> importantly, we are looking for a good response time on the "new fact ->
> rule fires" cycle.
> > >
> > > Any comments?
> > >
> > > James
> > >
> >
> > ---------------------------------------------------------
> > Ernest Friedman-Hill
> > Distributed Systems Research        Phone: (925) 294-2154
> > Sandia National Labs                FAX:   (925) 294-2234
> > Org. 8920, MS 9012                  [EMAIL PROTECTED]
> > PO Box 969                  http://herzberg.ca.sandia.gov
> > Livermore, CA 94550
> >
> > --------------------------------------------------------------------
> > To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
> > in the BODY of a message to [EMAIL PROTECTED], NOT to the list
> > (use your own address!) List problems? Notify
[EMAIL PROTECTED]
> > --------------------------------------------------------------------
> >
>
>
> --------------------------------------------------------------------
> To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
> in the BODY of a message to [EMAIL PROTECTED], NOT to the list
> (use your own address!) List problems? Notify [EMAIL PROTECTED]
> --------------------------------------------------------------------
>
>



--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to