• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JSR-94, JMS, and EJB's

 
Ranch Hand
Posts: 83
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
reply
    Bookmark Topic Watch Topic
  • New Topic