We are developing a serious tapestry application (not by size, but by
purpose) and the information given to us by your source code is
invaluable.
Big large thanks to you and good luck to your efforts:)
as for now it is:
1. using managers instead of just DAO (yes, as for now our pages use
only DAO)
2. dev/prod properties in external files taken through spring (we had
many thoughts about "how do we..." and here is one of the answers that
works)
3. security-related components that operate in terms of domain
4. 404 error from tapestry :) (you know, of course, there are not much
of errors in tapestry without some hacking)
5. clarification about testing (tapestrys own testing is a bit
complicated to understand for me), we are still on our way to fully
test our project
i can't remember more for now, but assimilation with wookis ideas is
in progress :)
we use jquery too -- already managed to use javascriptstack, but you
have some examples of components that use it (for now it is very sadly
done in my project :))
There is a thing I did not like: why do you use HQL while there is
Criteria API? This requires you to cope with injections and I think
criteria api is better overall. Why? :)