Hi,

Thanks for the clarification.

Jbossrules is not triggered on db access: it is triggered on calling an ejb
method, session or entity.  The current simpleminded examples all happen to
only have entity beans.  I'd like an example that would be more appropriate
to a session bean.

I agree that the current implementation is jboss specific, but in the
absence of any proposed spec from the jsr on rules I thought it best to
implement something that seemed like it would work.  Do you know of any
other fundamentally different way to connect an ejb container to a rule
engine?

Thanks
David Jencks

On 2001.05.08 09:17:55 -0400 Vesco Claudio wrote:
> My english is better over time? :-)))
> 
> I want a rule engine with jdo(castor)/jboss with session beans and not
> entity beans, but I can rethink this (with jeops/jbossrules) when I
> complete the implementation castor-jca.
> 
> The problem is: a remote call to a session ejb can transport data which
> must be validated with a rule engine (I think). Only when the data is
> valid then I store in db. If I remember in your implementation the rules
> are triggered by access to db.
> 
> Another problem is the triggering is jboss-specific (with interceptors),
> I want a more portable solution (but I like too much jboss to convert to
> another application server :-))) ).
> 
> Thanks you,
>       Claudio
> 
> > -----Original Message-----
> > From:       David Jencks [SMTP:[EMAIL PROTECTED]]
> > Sent:       Tuesday, May 08, 2001 3:01 PM
> > To: [EMAIL PROTECTED]
> > Subject:    RE: R: R: R: [JBoss-dev] CX + Castor
> > 
> > Hi,
> > 
> > If I understand you correctly, you do not want a ejb/jboss integrated
> > rule
> > engine but rather a jdo/castor integrated rule engine? So whether or
> > not
> > your requirements could be met by jbossrules is irrelevant, since it
> > is an
> > ejb - rule engine integration you don't want to use it?
> > 
> > Thanks
> > david jencks
> > 
> > On 2001.05.08 03:40:40 -0400 Vesco Claudio wrote:
> > > >Hi,
> > > 
> > > >I'm not sure I understand all of your description of your rule
> > engine
> > > >requirements but from what I do understand I think they can be
> > handled
> > > by
> > > >what I wrote, jbossrules.  I would be interested in seeing a more
> > > detailed
> > > >explanation of what you are trying to do and may be interested in
> > > >implementing it as a jbossrules example.
> > > 
> > > Hi and sorry for my english :-)
> > > 
> > > The project for my society is now only in my head. I dont like too
> > much
> > > JEOPS-approach of jbossrules. I want a better separation from entity
> > ejb
> > > and jdo beans. If we use jdo, the rule system can be applied to a
> > wide
> > > range of system (not only application server) and my collegues can
> > work
> > > without too much troubles. I dont like too much jess (licency), but
> > I
> > > can implementing a system evolving jeops.
> > > 
> > > For now I have another problem, jca-castor integration, when I have
> > > resolved this problem then I'll dedicate time to a rule system.
> > > 
> > >   Claudio
> > > 
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-development
> > > 
> > 
> > 
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
> 


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to