Hi-
How would one go about designing an application that requires complex business processing ( Mostly Stored Procedures ) using
EJB. Would it be sensible to still use Entity Beans and how would one go about calling Stored Procedues? ( Or Should Stored Procedures be scraped and coded as business logic in the Application - Say Business Methods using session beans? ) And would it be appropriate if Session Beans and Entity Beans co-exists ( Not necessarily Session Facade Design ) to take care of different aspects of the business ?
Using Entity Beans for all finders , updates and inserts and
using Session Beans for all complex processing and making them talk to the database without using Entity Beans ?
What are the best practices in this regard?
Please help!
Also if we have to have local component interfaces for CMR , then how can a client residing in a different JVM access the methods in the component interface ? Do we have to have both local (for CMR) and remote ( for client access) interfaces ?
Thanks
Brijesh