A common approach is to use DTOs as the objects that the rule engine works on.
You can then build a facade which works with these DTOs and invokes the rule engine. This facade can then be exposed remotely, via EJB/RMI, or web services (whatever works for you). If you want a stateless rule engine (ie the DTOs you pass contain all the data you need) then it is very simple. If you want to keep state between remote invocations, then it is a little more complicated (but still not that complex). The advantage of the web service approach is that any client can access the rules. You can either build bottom up, from the DTOs to the facade, or else you can define you "objects" as XML Schema with WSDL (document based messsaging works best), and then use an XML binding technology like Castor, JAXB etc to generate your DTOs from your schema definitions. Michael. On 12/14/05, Keith Marshall <[EMAIL PROTECTED]> wrote: > > We are looking at options to handle entity specific logic in an > application. Drools is a consideration in that we are standardizing on > JBoss, it would appear. I have yet to find confirmation on the remote > accessibility of the drools engine at runtime. Can someone explain or > point me in the direction of that info? > > Thank You > > Keith A. Marshall > Ext: 1089 > > >
