I've been a bit bored lately so I recently decided to go back and really get a grip on Tapestry. I started out stepping through a bunch of tapestry examples and in general trying to get my head around the framework using the docs on the website which are actually pretty good. I picked up the manning book also and have read most of it now, the book is pretty spot on though I think the web docs are almost as good so I'm not completely sure I needed it but I'm addicted to buying books so I'll live.
Here are my problems so far:
URL's are very messy and awkward, why do they have so much Tapestry state in them that I have to implement an interface to create bookmarkable URL's?
why do I have to create an extra value property in my page to be updated while looping in a @Foreach? seems like this should be created dynamically for me.
rewriting/hacking any bits of JSTL that I'm used to and are missing into Tapestry components . I guess I feel a little vulnerable and outside of my comfort zone not using JSP/JSTL
the whole Visit object thing is kind of weird. I think I prefer directly operating on the Session and Request
Why prefix Interfaces with 'I'? Looks weird and is not very Java like.
Here's what I like:
clean html
possibility to easily create really nice reusable component libraries
dynamic javascript components are kind of cool.
line precise error reporting is very nice especially if you name your component usages name@TextField.
