Hi, there is large application based on JDBC that should now be converted by me into an EJB/Oracle based application. Because of the complex class hierarchy that has evolved over month, it is not easy to encapsulate single classes to be the data holder for one EJB. Most of the classes extends or imports other classes that should not be deployed on the server.(GUI classes, client side caching, ...) Should I implement new classes that are simple data containers? Is it possible to deploy these new classes standalone to the server, so that EJB's that are developed later just use this class. How do I create holder and helper classes for these data container classes? (I am not yet involved in CORBA) Is there some one out there, who has made experiences with this kind of problem? Thnaks in advance Hinrich =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
