I posted this same question on a local northern virginia java forum that is very active. The java guys don't get my transaction control concerns. Just curious if anyone here has used them.
I think session EJBs and message driven EJBs may be useful. My concern is with entity beans. I don't see any advantage whatsoever with them over data access objects accept that 'they are in the J2EE standard' and they have a catchy name. They are alot harder to implement, code, and test. The expert one on one book from wrox press for java is pretty negative on them also.
Am I missing something?
Also, am I jumping to conclusions that they might have transaction control issues? When you do a dml statement with entity beans, you do not directly make a database call, you update the bean in memory and the application server decides when to make the database change. This implies that some other user may not see your change.
I saw that with weblogic you can implement isolation levels in the application server, but a java guy on the forum said they have performance problems... so why use it?
am i missing something? Data access objects seem to be tried, true, tested, and they work. I don't see any upside for entity beans. I am a novice with them so I don't want to jump to conclusions.
On the other hand session beans seem to be useful for logic out of the presentation layer(layer that your screens are on).
anyone have experience here or comments?
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Apr 05 2005 - 14:27:38 CDT
