I have already made strides toward this in WebWork... it is much harder in WebWork than it seems it would be in Click ;)
Nonetheless, this sort of stuff has provided me a ridicilous return on productivity, and I've only scratched the surface. I think we should definitely explore this kind of strategy... as long as everybody promises to never call it RAD! Cris On 3/26/06, Andrus Adamchik <[EMAIL PROTECTED]> wrote: > > > > 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. > > Cayenne does that already - > > http://objectstyle.org/confluence/display/CAYDOC/Generic+Persistent > +Class > > Somebody tell Matt Raible ;-) > > I was also going to make a comment about Click. It shows lots of > promise as far as providing the integrated stack based on Cayenne > model (something I hoped would occur with Tapestry). I used it on two > projects and even in its current form it is an excellent simple-to- > use platform for writing custom Cayenne-aware controls. And the > library of standard controls is growing. > > Also what's important is that unlike DataViews technology that was > literally thrown over the wall to us by a retired committer, Click > project is very active and is building the community. > > Seriously though, the above shows that Cayenne naturally moves in the > right direction already. If anyone thinks that we can (or should) > make this a formal development strategy, please share your thoughts > at a more specific technical level. > > Andrus > > > On Mar 25, 2006, at 9:04 PM, Mike Kienenberger wrote: > > > 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. > > > >
