Re: Changes to Logic at Runtime

2011-02-13 Thread Mark
> Maybe you should try with Java rule based inference engines with "production > rules" - like JESS (one I have used in the past) and maybe something like > Drools (of which I have only heard about). > Thanks for the suggestion. I ended up using MVEL, which is the expression language used by Droo

Re: Changes to Logic at Runtime

2011-02-12 Thread Vangel V. Ajanovski
On 07.02.2011 18:25, Mark wrote: - Buy a blue widget and get 10% off a white widget. - Buy two white widgets and get $5 off your entire order - Buy white and blue widget before 2/15 and get a green widget for free. Maybe you should try with Java rule based inference engines with "production rul

Re: Changes to Logic at Runtime

2011-02-07 Thread Thiago H. de Paula Figueiredo
I guess you need a rule engine. Tapestry's live class reloading wouldn't be an option as you said you don't want to recompile classes. Tapestry works on compiled bytecode, so using Groovy or Java or Scala wouldn't make a difference. On Mon, 07 Feb 2011 15:25:21 -0200, Mark wrote: I have

Changes to Logic at Runtime

2011-02-07 Thread Mark
I have a situation where I need to be able to change the logic that occurs on a page at runtime without recompiling or redeploying the app. For example, imagine a shopping cart for a site that offers all kids of constantly changing promotions. Examples would be: - Buy a blue widget and get 10% of