RB doesn't seem to throw an error if you call an undefined method on a bean. This seems like a very dangerous omission. It's not like fields which get checked with the database. There should at least be an option to make the check happen.
Looked into this however the architecture is geared to this principle right now. FUSE events rely on the fact that these methods may not exist. It could be solved by adding a mechanism to identify the FUSE methods, but that would restrict the whole architecture too much.
I don't think this issue is severe enough to revise the architecture.
Changed my mind about this.
Gonna treat this more like a 'feature'.
Allowing devs to set error handlers on beans...
Optional error handling FUSE, Close #406.