I think the question your asking is the advantage of Session Beans or Stateless Beans ? you cant deploy per say standard objects ( those that dont extend EJB interfaces ).
The difference between Session and Stateless is the Session beans hold state between calls to the EJB. Stateless beans are one and done. Many prefer Stateless, myself included, b/c you want to control transaction(s), etc.. yourself in some sort of framework encapsulating the interactions instead of in the EJBs themselves. If your question is why use EJBs over a simple socket app and standard java objects..thats another issue.:) -----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. __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
