[EMAIL PROTECTED] wrote:
> I had a (very) quick look at jeops and from a first glance it looks pretty similar
>to jrules (a commercial product).
> Making the choice of using it instead of javascript (or even tcl)
could suddently transform xmlBlaster
> into a rules engine or even a complete wor
I had a (very) quick look at jeops and from a first glance it looks pretty similar to
jrules (a commercial product). Making the choice of using it instead of javascript (or
even tcl) could suddently transform xmlBlaster into a rules engine or even a complete
workflow engine. This would broaden
There are several rule-based systems out there. Another name is
Production Rules or
Workflow. One written in java is JEOPS. I took a look at it and plan
to do some
work with in the near future.
Mark
Heinrich Götzger wrote:
>Hi,
>
>I'm planning to have a client connected to xmlBlaster wh
Heinrich Götzger wrote:
> Hi,
>
> I'm planning to have a client connected to xmlBlaster which subscribes a
> certain number of messages. This client is able to publish some other
> messages. However the content of these published messages should be
> dependent on the content of the subscribed mes
Hi,
I'm planning to have a client connected to xmlBlaster which subscribes a
certain number of messages. This client is able to publish some other
messages. However the content of these published messages should be
dependent on the content of the subscribed messages.
I imagine a list of rules wh
