Under 5.0b7 several issues make runtime editing of .oss files less friendly
than it should be:
1) A syntax error in a .oss file causes the exception page to come up and the app to become in
operable. Worse, even after the error is corrected, the rule reload does not
fix the app -- a
restart is required.
2) If rules fail to resolve a component to display in a given context, a scary exception is
displayed
Would be better if:
1) .oss syntax errors resulted in error bar on UI (no exception) and left old rules in place until
problem was corrected
2) Missing component resulted in rendering error information *inline* where component should
appear (and no exception page)
Original issue reported on code.google.com by Ariba...@gmail.com on 16 Feb 2009 at 9:02
Original issue reported on code.google.com by
Ariba...@gmail.com
on 16 Feb 2009 at 9:02