Client Access to Enterprise JavaBeans
Like it or not, how your clients access your Enterprise JavaBeans has some effect on the design of your EJB. Ideally, you want to design your enterprise beans to be immune to changing client designs. That is, if you decide to write a new client that accesses data in a drastically different way, you don't want to change any EJBs. It's the same way in the database world. After you set up your database schema, you don't want to rearrange the data just because you must access it differently.
You can take steps to make your EJBs as flexible as possible, but don't be disappointed if you eventually find yourself redesigning some of the beans or adding new beans. As you often find with applications, the act of developing ...
Get Special Edition Using Java™ 2 Enterprise Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
