Tapestry is definitely looking promising for me. I've spent the day looking it over, and I'm liking it a lot... the templating system really is quite neat. Still... I like working with velocity templates, myself... ;)
I like Velocity myself. We use it for "snippets", big chunks of text on a page like legalese and instructions. Clients like to have control over that stuff on the fly. So we have snippets in a database table. And an @Snippet Tapestry component to render them.... similar to how message resources work in Tapestry. So you can really have your cake and eat it too!
There are a few warts with Tapestry:
- J2EE security - doing declarative path-based security doesn't really work. There are some hacks, but nothing that I'm satisfied with. I'm going to explore using servlet filters to work around it more elegantly soon.
- Unit testing - well you're coming from Struts, so you probably didn't unit test actions either :)
- Lifecycle - it is tricky to wrap your head around how the lifecycle of components work and the event order that is fired. I still don't quite get it.
- Some awkward conventions that take some experience to get used to.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
