Our AppScreen.java extend SecureScreen.java. This super SecureScreen
contains some Access related validations. AppScreens make a call to
super.doBuildTemplate(). In case of invalid access, we set the
InvalidAccess template. The way things usually work, even after the
InvalidAccess template has been set, the call is returned to the extended
screens doBuildTemplate() where the code continues the processing. This is
"wrong" by the way we want it to work - We would like the program to "quit"
once an InvalidAccess has been encountered and InvalidAccess template has
been set.
One solution we recognize is that the doBuildTemplate of the super screen
simply throw InvalidAccessException and all the extended screens catch this
exception and set the InvalidAccess template. But then this means that all
the screens need to contains this catch block and exception handling that I
would like to avoid.
Please let me know any other ways of approaching this issue.
- Akshay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
