> -----Original Message----- > From: Scot Mcphee [mailto:[EMAIL PROTECTED]]
> First Session EJBs are usually used to implement the 'Facade > Pattern'. This is definitely A Good Idea. Plain old java > objects will not have access to the declarative transactions > of the EJB container, therefore even if you used POJOs to > facade your calls to the Entities, each and every call to > each individual entity method is a separate transaction. > The original poster just stated that they're using 'DAO pattern', which sounds like they're *probably* not using Entity beans. *If* this is the case, it may mean your arguments about multiple EJB calls don't apply. Israel, are you using Entity EJBs or not? If the system is simple, then transactions may not be required; it may be enough just to handle the commit / rollback on each JDBC call in the DAO. It depends on the system requirements. <snip/> > It is my opinion that non-use of the Facade Pattern is the > number one cause of performance problems in EJB systems. Again, it sounds like the original poster was debating whether to use [session EJB -> DAO object] versus [POJO -> DAO object]; if so, then the above isn't relevant. If the system is more complex & requires transaction support, then I entirely agree with your approach. Regards, Al. > -----Original Message----- > From: Israel Ayala [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 17, 2003 1:40 PM > To: jdjlist > Subject: [jdjlist] Sessions Bean vs Objects. > > > Hello. > > I want to know the advantages of Sessions Bean instead > of simple objects java. > > The scenery of my application is: > - Only one WebLogic server (NO clusters). > - DAO pattern to access to the data. > - Oracle RDBMS. > > > Thanks. --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
