Hi Mike,
I think Cayenne support for exposing meta data and object validation
methods already provides the infrastructure for the development of data
aware controls/components in J2EE web applications. I think this can give
you some of the productivity benefits people are seeing with RoR, if the
web stack on top of Cayenne leverages these features.
With Click I have been building data aware controls for Cayenne (which
will be included in the next release) and I am seeing a really RAD stack
emerging. Being able to add a couple of columns to a table in the Cayenne
Modeller and associated object, regen the parent classes and run the
generated SQL scripts in less than a minute enables you to move very
quickly.
An example of a Cayenne data aware control is provided below.
CayenneForm form = new CayenneForm("form", Address.class);
QuerySelect querySelect = new QuerySelect("state", "State:");
querySelect.setQueryValueLabel("system.states", "VALUE", "LABEL");
form.add(querySelect);
In this example we have a CayenneForm for editing an Address data object.
To the form we are adding an HTML select control which renders a list of
states derrived from a Cayenne named query "system.states". When the form
is posted the Address state property will automatically be updated with
the submitted value.
regards Malcolm Edgar
"Mike Kienenberger" <[EMAIL PROTECTED]>
26/03/2006 05:04 AM
Please respond to
[email protected]
To
[EMAIL PROTECTED]
cc
Subject
RoR'ing Cayenne
I haven't used Ruby On Rails, but here's an interesting comment that
might give Cayenne some future direction goals. Of course, I'm not
entirely certain what he's talking about :)
Java Web Framework Sweet Spots - by Matt Raible
JavaWebFrameworkSweetSpots.pdf
http://www.virtuas.com/files/JavaWebFrameworkSweetSpots.pdf
WebWork
6. What do you think of Ruby on Rails?
• The integrated stack is amazing. They did a great job here, and
there is room for Java to
offer something similar. WebWork could easily be the web stack, but
the persistence
solutions aren't very promising right now. The biggest issue is that
while WebWork and
SiteMesh, for example, support configuration reloading and even dynamic
class
reloading, Spring, iBatis, and Hibernate do not. They need to step up
to the plate and at
a minimum support configuration reloading before a good stack similar
to Rails can be
offered. Similarly, Hibernate and iBatis offer poor hooks into the guts of
their
framework like WebWork does. With a single class, I was able to get rid of
the
requirement for xwork.xml in WebWork. That cannot be said for the
persistence
libraries. Once they get their act together, perhaps a complete stack
can be pushed out
that does all the things Rails does.
----
This email is intended for the named recipient only. It may contain information
which is confidential, commercially sensitive, or copyright. If you are not the
intended recipient you must not reproduce or distribute any part of the email,
disclose its contents, or take any action in reliance. If you have received
this email in error, please contact the sender and delete the message. It is
your responsibility to scan this email and any attachments for viruses and
other defects.
To the extent permitted by law, Zurich and its associates will not be liable
for any loss or damage arising in any way from this communication including any
file attachments. We may monitor email you send to us, either as a reply to
this email or any email you send to us, to confirm our systems are protected
and for compliance with company policies. Although we take reasonable
precautions to protect the confidentiality of our email systems, we do not
warrant the confidentiality or security of email or attachments we receive.
