Java J2EE Portal
Enterprise Java Station
J2EE curve
Java News / Articles
Java News / Articles
JavaEE Architecture Using The Spring Framework
Compare Wicket Tapestry JSF Framework
Wicket, Tapestry and JSF side by side
India Java User Groups
Processing...
Buy Java, Deals On Software Technology Store
Click here for great deals on computers, laptops, software and books
Migrating a J2EE application from EJB to JDO PDF Print
Written by Tim Stapleton   
Aug 30, 2005 at 02:34 AM

EJBToJDOMy enterprise line-of-business experience has presented some specific challenges that no doubt have shaped my outlook on software development.

Here are a few points on enterprise builds:

1. They are long-living applications. Typically 10 years. This makes technology choice tricky as it's very easy to become hostage to a technology that is constantly evolving and requiring continual 'ports' to the latest releases. There will always be technology upgrades needed but this can be quite expensive in nascent technologies.

2. They are complex with far more entities and ui screens than typical BtoC applications. They tend to test the scalability of the development tools. It's an uncomfortable situation when your project is larger than anything that the tools vendor has previously dealt with.

3. Developer productivity is usually an issue. These projects typically involve replacing existing systems written in an older technology (AS400, Mainframe, 4GL etc). While these older technologies deliver applications that are much less rich than a modern Java or Java/Web application, they are very efficient from a developer perspective.

4. They usually involve training of an existing developer workforce to work with the new technologies. It's often not practical or desirable to replace the development team when implementing new technology. There is a large amount of business and domain knowledge vested in the existing developers.
In my experience EVERY company underestimates the time and effort needed to make this transistion. It's not just Java anymore; It's Java and J2EE and Web and Web services and a new IDE and the specifics of a particular application server. And in addition there's the transistion to the distributed environment. This can be quite a leap.

These experiences have drawn me towards solutions that are as simple and as effective as I can find; as can be seen in the following case study.




Add This Feed Button

Enter your Email


Java Expert Interviews
The future of the Java platform lies in the mobile world
PatrickLightBodyWebWork
Struts Action Framework 2.0 should be released by August 2006
MarcDomenig
Swing UI is mature while Ajax is still in its infancy
Processing...
Go to top of page  Home |
SiteMap

Copyright 2004 to 2008 Rightrix Solutions. All rights reserved. All product names are trademarks of their respective companies. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Rightrix Solutions and IndicThreads.com are independent of Sun Microsystems, Inc.

Views expressed at IndicThreads.com reflect the views of the authors alone, and do not necessarily reflect those of IndicThreads.com. IndicThreads.com and it's authors are not responsible for reader comments and opinions.

Enterprise Java J2EE JEE Portal >> IndicThreads.com