Yes, the advantage of using local interfaces in EJBs is avoiding the creation of stubs and skeletons, use of RMI and serialization. But what many people don't realize is that all the major containers have been doing this since 1.1 anyway, abeit in proprietary ways. You really gain no performance advantage by explicitly declaring an EJB interface local - you merely adhere to the specification.
Mark -----Original Message----- From: Kunal H. Parikh [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 8:20 PM To: 'Struts Users Mailing List' Subject: RE: ejb's and tomcat Hi Andrew, Mark, and ALL! The CMP2.x spec allows declaring EJBs as local objects. The advantage of the local EJB objects is that they don't get serialized/deserialized(I think) and pass-by-reference and not by-value. Effectively, If you use a LocalEJB, you have the flexibitly of making the REMOTE with very few changes to code. People, please correct me if I am wrong. Kunal -----Original Message----- From: Andrew Hill [mailto:[EMAIL PROTECTED] Sent: Wednesday, 8 October 2003 21:20 To: Struts Users Mailing List Subject: RE: ejb's and tomcat Nonsense! In the same way acronyms look great on resumes, they also look just super on product brochures. If you use EJBs you can proudly proclaim that your application is "based on J2EE EJB technology"! This is useful for impressing clueless manager types even if EJBs confer no actual technical advantage (and often many disadvantages) to what your trying to do. btw: afaik its not just distributed stuff but also transaction type stuff its good for (but lets face it - most dbs do enough in that regards for most apps transaction needs already) -----Original Message----- From: Mark Galbreath [mailto:[EMAIL PROTECTED] Sent: Wednesday, 8 October 2003 19:04 To: Struts Users Mailing List Subject: RE: ejb's and tomcat If you are asking these questions, you probably should not be using EJB. The ONLY reason to use EJB is if you are developing a distributed application; anything else is overkill. If you simply need data persistence, use JDBC and use DAO, or one of the persistence frameworks: Ibatus, Hibernate, or Kodo-JDO. Mark -----Original Message----- From: ajay brar [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 07, 2003 9:51 PM To: [EMAIL PROTECTED] Subject: ejb's and tomcat Hi! does tomcat support ejb's. I'm building a web app which uses struts. i'm using ejb's for the model part. can i deploy the ejb component on tomcat? what other alternate ways are there to do so? thanks cheers ajay _________________________________________________________________ ninemsn Premium transforms your e-mail with colours, photos and animated text. Click here http://ninemsn.com.au/premium/landing.asp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
