This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Probably best to create a CinemaException and use it as a superclass for all other Exceptions. It is very easy to create your own Exceptions; in 99% of cases you only need to create 4 constructors, as in the Exception class itself. You can decide whether it is checked or unchecked by correctly choosing the superclass for CinemaExpression.