RE: [rules-users] Upload Rules to BRMS at runtime

Is anybody using BRMS (4.0.7) successfully in production? If yes, how many DRLs do you have? Thanks, Vikas _____ From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Leonardo Figueiredo Sent: Wednesday, October 01, 2008 8:27 AM To: Rules Users List Subject: Re: [rules-users] Upload Rules to BRMS at runtime Hi, You mean using an api to add rules to the BRMS? If so i have the same problem. I am using an "homemade" build that have a custom Servlet that allows me to pass an DRL to be added to the BRMS. I am still searching for a better solution. Regards, Leo On Wed, Oct 1, 2008 at 7:00 AM, Asif Akram <asif.akram(a)imperial.ac.uk&gt; wrote: Hi, I was wondering if it is possible to create and upload rules at runtime to BRMS to be accessed by other users. I have only seen the examples where existing packages/rules are loaded from the BRMS. Any help and suggestion will be appreciated. Cheers Asif This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster(a)mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.