Java Application Frameworks (Not Only Client Side …)

GWT? I love it, but it's really not more than a widget toolkit, spiced up with some nifty facilities for doing RPC and I18N...

Swixml dead? I really like that thing! I thought it was the neatest thing. You define your gui in xml (for which you could create a tool - which people don't seem to do and instead keep editing xml raw - WHY), and through introspection it would interface with your code. It's actually more brilliant then what meets the eye.                                                   ps. this rich text editor that I'm typing my message in right now isn't behaving correctly in Opera it seems. When I hit return, it *inserts* a paragraph instead of append, weird.

Three other open source offerings that are missing from that list:

• JMatter - JMatter is a software framework for constructing workgroup business applications based on the Naked Objects Architectural Pattern.
• MetaWidget - Metawidget is a 'smart User Interface widget' that populates itself, at runtime, with UI components to match the properties of your business objects.
• OpenXava - OpenXava is a productive way for creating AJAX Enterprise Applications with Java. Indeed, it's faster developing with OpenXava than with Ruby On Rails, Spring MVC, or any other MVC framework. This is because in OpenXava you only have to write the Model. The Controllers are reused, and the View are generated automatically.

An addtional tidbit about Griffon, it can be seen as a polyglot programming desktop/RIA framework as it supports 5 JVM languages at the moment: Java, Groovy, Scala, Clojure and JavaFX. It also lets you embed JavaFX components on Swing containers.

The Genesis project would also seem to fit your critearia of an application framework: http://genesis.dev.java.net/nonav/3.2/maven-site/en/index.html

The same question raises for OpenXava: Will the client need the jvm or a browser?

> http://incubator.apache.org/pivot/

Thanks a lot for this!! I added this!

> Not sure exactly what your criteria is

Making RIA development easier (in any sense for db, swing, whatever). But the rich client should not require a browser. So it should run within the jvm.

> The tox 

 Sorry, I cannot understand, but does this really match the criteria defined above? (on client side no browser/ajax required?)

You may want to add Jt to your list (jar top 25).
http://freedom.lunarpages.com/Jt

 

 Jt - Java Pattern Oriented Framework (Jt 4.2)

 Jt is a pattern oriented framework for the rapid implementation of Java applications. Jt has been utilized in several large mission critical systems. Jt implements many well-known patterns including Data Access Objects (DAO), GoF design patterns and J2EE patterns.


The framework addresses the following goals and requirements:
A) The pattern oriented framework implements and facilitates the implementation of well-known design patterns like GoF design patterns and J2EE Design patterns. The framework itself is conceived and implemented based on design patterns (from the ground up). The framework facilitates and accelerates the implementation of applications based on design patterns.
B) The framework architecture is based on a messaging design pattern: framework objects are able to interchange information and perform computations by sending, receiving and processing messages. A messaging API provides strong encapsulation and loose coupling; framework components can be easily plugged into complex framework applications using a "lego/messaging" architecture. The framework takes full advantage of the power and simplicity of the messaging design pattern.
C) The framework lego/messaging architecture provides transparent access to remote components: remote framework objects is treated as local objects. Design patterns implemented by the framework (adapters, remote proxies and facades) make this posible by hiding the complexities associated with remote APIs.
D) The framework provides transparent integration with other technologies via framework adapters, proxies and the implementation of related design patterns. These technologies include BPM, DAO implementations, MVC implementations, EJBs, JMS, XML and Web Services.
E) The framework is designed to be lightweight and fast in terms of performance (low overhead).
F) The framework messaging/lego architecture should improve and simplify design/development efforts. There should be a tight correspondence between UML design diagrams and the framework messaging based applications and components needed for the implementation. Ideally, the framework provides wizards and automated capabilities for generating framework applications. Framework components should be easily added to BPM process diagrams. In future versions of the framework, it should be possible for applications to be generated directly from the UML design diagrams.
G) The framework messaging architecture facilitates testing and debugging efforts. The framework provides capabilities for testing components independently (each component as a unit) by sending messages and verifying the reply (output) messages.
H) In order to provide additional productivity benefits, the framework is integrated with open source IDEs.

 

 

> Jt

Hmmh, this really matches the criteria defined above? (on client side no browser/ajax required?)