tag:blogger.com,1999:blog-14415229.post2330096282730417330..comments2023-10-10T16:55:02.139+02:00Comments on Chase The Devil: Why are you not using Entity EJB 1.1?Fabienhttp://www.blogger.com/profile/07288327695801480778noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-14415229.post-62566277204447927802007-02-19T11:33:00.000+01:002007-02-19T11:33:00.000+01:00compared to the present ejb 3 or hibernate, ejb 1....compared to the present ejb 3 or hibernate, ejb 1.1 is no match. Some of the biggest reasons for not to use ejb 1.1 are <BR/>1. Limitations in EJBQL. It is pretty naive. Complex queries are almost impossible<BR/>2. n+1 problems will show its ugly face for anything but the most trivial of applications<BR/>3. If i remember right, EJB 1.1 didnt have local interfaces, so EJB to EJB communication is also implicitly remote even though application servers optimized it if the EJBs were collocated.<BR/>4. Features like session cache, second level cache, inheritance mapping etc are either very difficult or impossible <BR/><BR/>and much much more...<BR/><BR/>So, if you have a choice my sincere recommendation would be to move to some modern orm framework like hibernate.Ganeshji Marwahahttps://www.blogger.com/profile/01919214182520822111noreply@blogger.comtag:blogger.com,1999:blog-14415229.post-32583745642031008382007-02-08T16:31:00.000+01:002007-02-08T16:31:00.000+01:00I'm with Deniz on this one, plus the following: ...I'm with Deniz on this one, plus the following:<BR/> * Modifying an EJB means recreating and deployiung the whole EAR. Not a nice thing to do with IBM tools (depending on you memory availability and number of EJB, this process can take longer than an hour).<BR/> * If you have a transaction that involves several EJB instances, all of them are kept in memory. There was no way to finetune this.<BR/> * Forget about doing batch processing when EJBs are involved.Sorontharhttps://www.blogger.com/profile/06217294233651527468noreply@blogger.comtag:blogger.com,1999:blog-14415229.post-24866013875894069322007-02-07T19:48:00.000+01:002007-02-07T19:48:00.000+01:00Hi,
We were using EJB 1.1 at 2002 with Websphere ...Hi,<br /><br />We were using EJB 1.1 at 2002 with Websphere Application Developer & WS Application Server. Testing components that use Entity Beans at the back was more difficult than the parts that make use of DAOs. IBM's tool was not stable, for example it was not giving proper error messages when something is wrong in mapping files. Also IBM's deployment tools was sometimes failing with unknown reasons. Since that time I hate XML, an I try to keep out of XML as much as I can.Denizhttps://www.blogger.com/profile/11990645642854464268noreply@blogger.com