> A lot of the power of Tapestry is now coming from the OGNL library, so its > worth checking it out more carefully: http://www.ognl.org
Yes, so it seems. After reading through your various comments on this, it's clear that I'm going to have to spend some quality time with OGNL. In the Tapestry tutorial and docs, it was portrayed as a handy way to access beans, but it's clearly a lot more. BTW, I'm keeping my own list of Tapestry feedback, coming at this as a newbie. It was interesting reading Christian's observations. I share a couple, but differ on some others. For instance, I agree that having three files (markup, Java, and XML bindings) per page is a bit cumbersome. I understand the value, though, and I'm willing to live with it, as I don't see a really good way around it. In particular, I find that one of Tapestry's greatest strengths is the way it deals with the HTML side. With just a few changes, you get something that both Tapestry and an HTML editor can still deal with. That is something JSPs definitely don't have. I'm not sure whether the Tapestry Lite direction described on the Wiki is good or not. The syntax looked pretty tortured, though I understand the desire. Being able to eliminate the XML file would be handy. Anyway, when I get further along, I'll write up my experiences and post to the list, too. -- Dave ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
