Hey all!
For my project I've written a Rules Application Service (RAS) following the application service design
pattern (Alur, Crupi, Malks: 357). In the core directory I've created a Rules Communication Service that currently includes both an RMI and a JMS interface. These types of communications work well because they decouple the JSR-94 compliant rules engine from its client services. Unfortunately, there is a possibility that this RAS could be deployed within an
EJB container such as
JBoss or Weblogic, probably instanteated within the ServletContextListener. The reason we're deploying it this way is that we have to give our rules engine the ability to work in its own multi-threaded environment. It can't do this if deployed in its own EJB.
Both JMS and RMI are great for communicating with "remoted" objects or services. However, is there a better way for communication with a JSR-94 compliant rules engine when deployed inside of an EJB container that is lighter weight? Unfortunately, the solution cannot rely on a specific rules-engine, otherwise Jess would have an answer.
I've coded myself into a corner, anyone have any ideas?
Mike Van
If at first you don't succeed, try, try again. Unless you really suck at it. Then, you might just want to try something else, if you dont' want to be a loser I mean.
