Hello,
the current implementation of the event observer pattern seems to be (in my opinion) unstable: the new one observer can throw an uncaught runtime exception and so prevent other observer from the reaction to this event.
Are there any fail-safe design pattern known, how we should use the Seam event model?
Thanks, Gena
Please raise a JIRA issue for this - at first glance I agree with you, but we need to carefully consider this.