Head First EJB

The problem with isCallerInRole()...

the Bean Provider hard codes a role name, but how does he know what roles the App Assembler will use? And what if there’s more than one Bean Provider?

The App Assembler must map between the programmer’s hard-coded (completely fake) role name, and the abstract role she wants to define for this application.

abstract role name: KeyAccounts

bean A role name: VIPCustomer

bean B role name: Enlightened-Customers

Note

three different names for the SAME role!! Annie wants the deployer to map REAL customer groups to “KeyAccounts” and not those other two names, but those names are in code, and she can’t touch the Java source code!