Why another J2EE framework?
There are already many J2EE based frameworks available as listed at this link. Each of them seem to address a particular aspect of a J2EE system better than others. The framework I’m presenting here has some strong aspects that none of those frameworks seem to offer. What is the value proposition? Briefly here is my value proposition… • Integrate Struts and Java Blueprints frameworks. Struts with its strong presentation tier model and wide following, BluePrints with a solid business tier model make a good platform for building J2EE applications when combined. • Making the BluePrints business tier simple and lightweight without losing the design flexibility . • Provide a way to build a Swing based UI client along with web clients with minimal extra effort and at the same time without making the web system design complex. The extra effort needed is to – • code the JDialogs to implement the View • lay out Swing components • re-code the client side validations implemented in JavaScript i
Related Questions
- The Sun ONE Application Framework has the notion of a display field. This isn like the J2EE Blueprints or other J2EE architectures Ive seen--why not just pull values directly from a helper bean?
- How is the Sun ONE Application Framework different from other J2EE frameworks?
- Why will sea level rise when the Arctic ice is already in the sea?
