can you provide a unit test for this? "end" is not so easy, but duration
should be fine, as it only appears in the attributes part of the rule.
On 4/15/06, Mitch Christensen <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> As (bad) luck would have it I ran into yet another java property<->DRL
> reserved word collision. Last time I had a java property called 'end',
> this
> time the culprit was 'duration'.
>
> The problem I have is that there is no parse exception, or any other error
> report for that matter, the rule just simply won't fire.
>
> It is a pain to be troubleshooting your code only to discover that the
> whole
> problem stems from the fact that you've inadvertently selected a java
> property name that collides with elements of the DRL syntax.
>
> I understand that eventually we will be able to overcome the situation by
> specifying full method names (i.e. getEnd() in stead of 'end') within
> conditinons, but is there any way we can be notified of such syntax errors
> so that we might find these conditions earlier?
>
> FWIW, In both cases it would have been totally nonsensical from a DRL
> perspective to have those keywords ('end' and 'duration') reside deep
> within
> a condition. It seems that the parser could have picked up such an error.
>
> -Mitch
>
>
