|
From: Michael E. M. <mm...@re...> - 2005-09-16 17:07:29
|
Start by reading Rod Johnson's book on J2EE development without EJB. http://www.springframework.org/node/23 There are some merits for using EJB, but in almost every single case I have seen, you don't need them. EJB Entity Beans (CMP) is a huge mess; don't use them. EJB containers provide distributed transaction capability; a business transaction can span multiple servers.. but I would try my very hardest not to introduce that kind of tight coupling. I'm in the process of moving a Weblogic EJB application to Spring/Hibernate. I'm almost done. The new product is less than 1/2 the code size (including config files.. like the entity bean descriptors) and it runs about 40% faster. All business logic is located in classes that depend upon nothing but J2SE.. just plain old java objects.. I can run/test the application stand alone, as a SOAP service, as an RMI service.. all I do is change a property file entry to do the switch. I can emulate dowstream services (stup them out) by swapping in a test stub in the Spring configuration. I can do all my database persistence with a single graph of java objects. Hibernate persists the graph according to my Spring transaction demarcations. Just for the fun of it, I wrapped my business POJOs with Spring's EJB abstraction, and deployed the application on JBoss. NO PROBLEMS!!! Garvey, Paul M (GE Commercial Finance) wrote: > > > > Springers: > > I need your thoughts on an architectual issue. I have an > application running on a websphere app server that uses IIOP to > communicate > > with an EJB application running on another websphere instance on > another websphere app server. I want to replace the 2 application with > Spring. > > Any suggestions on how I can have 2 spring application communicating > with each other? They will remain on 2 separtate websphere instances on > > 2 separate app servers? I am new to Spring so bear with me. I need to > know what features in Spring allows me to replace my controller > application > > to EJB application communication. > > > -Paul > |