Consider introducing "open" and "closed" state for a number of expressions
beeds and aggregate
beeds. In the open state, we can "build" the beed (design time in JavaBeans).
Then we "close" it, and
after that, structural changes (adding or removing operands or components)
throws an exception.
This can then also be used in the visual tool as the separation between design
time and runtime.
Original issue reported on code.google.com by jandockx on 26 Apr 2007 at 11:01
Original issue reported on code.google.com by
jandockx
on 26 Apr 2007 at 11:01