This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am a developer at a company, that has been around for 35 years. The architects are "old school"... afraid to go outside their personal comfort zone. They claim to give EJB a chance, but didnt like it. I think it would solve some of our problems. Any advice to get them to reconsider EJB now that its at version 3?
Their thoughts was that it would take too much code.
There are a few things that you could do, not the least of which is to show them some code examples using EJB 3.0. When I give talks at conferences I offer comparisons of simple EJB components using EJB 2.1 and EJB 3.0 and this gives people a good idea of how easy it has become compared to the old way of defining a developing EJBs.
You might also want to show them some of the rave reviews that have been written about EJB 3, and if they still don't believe you, get them to go to a premier and trusted conference where we are doing EJB 3 talks. For example, I will be presenting at Colorado Software Summit, which is in October and is a great conference that is attended by some 'old hands' in the business (many of which are old school :-)