EJB programming & troubleshooting: Coarse-Grained EntityBeans
Im reading some books about EJB and J2EE desing patterns. Each of this books told me that I should not use Fine-Grained EntityBeans.
Ok, but what does Coarse-grained mean? Does it mean to use one EntityBean for two or more tables? Tabels which are related?
In that case I think it is not possible to keep business logik out of EntityBeans, as often-mentioned.
Welcome to the wonderful world of EJB.
Yeah, basically you've got to write a sort of "universal" bean that knows which type of object it is dealing with.
And can save dependency trees. Woohoo.
Go with Hibernate instead if you can.