> Most of my JSF-problems seem to have a Tapestry-solution, that's fine. But, > oh no, what is this "ValueEncoder"-thing??? Don't say it is what I'm > afraid of it might be ...
One reason WebObjects wasn't popular is that it was a total resource hog. It made no real attempts at scalabilty; it would just keep loads of objects live in the session. That's great for simplifying things for the coder, but bad for the user (bookmarkable, pretty URLs anyone)? Tapestry cuts a middle path; for some thing you have to get your hands a little dirty to help out Tapestry on the things it can't automatically do. Those are few and far between, but when it comes for dealing with database entities, you do need to get involved. On the other hand, the Hibernate integration will grow, in the future, to handle this automatically for you (much as Trails can do today, in Tapestry 4). -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
