Naked Objects 3.0 for Java

Naked Objects ?
Naked Objects is an open source Java-based application development platform.
It’s called Objects because all you need to develop are your domain objects - the Naked Objects platformNaked auto-creates an object-oriented user interface (giving you the choice of
different styles) and the underlying database (using Hibernate).

Can I use Naked Objects to prototype an application that will be deployed on a different architecture?. Absolutely - in fact most people start to use Naked Objects initial for prototyping only and only later consider using it as a full deployment platform. The domain objects that you create for Naked Objects are Plain Old Java Objects (POJOs) - they aren't tied to Naked Objects in any way. So if you want to develop a hand-crafted user interface to invoke the objects' functionality, you can.

To what type of applications is Naked Objects best (and worst!) suited?. The auto-created user interfaces give the user a great deal of flexibility and control, but the corollary is that it does take a short while to get to know that user interface. So Naked Objects is best suited to the kind of in-house application that people use intensively; it is not at all suited to applications intended to be used by people with no training (for example a public web-site). However, per the previous question, there is nothing to stop you from developing a Naked Objects application for internal users, then building a more conventional tightly-scripted interface to the same domain objects, for use by external parties.

Do I have to use Hibernate?. No, it is possible to write alternative object stores to work with Naked Objects. For example, the download includes a simple 'XML Object Store' that is useful for prototyping purposes.