Hi Werner!
I'll have a look at it, but for what I have seen now, there might be much I really can reuse from them.
Sorry, there is a word missing here ("there might NOT be much")If you might have a look in their cvs https://trails.dev.java.net/source/browse/trails/src/org/trails/ you will see there are "tapestry" imports all around.e.g. trails/component and trails/page do have tapestry imports all around, but they contains some of the heart of tapestry They use spring to tie hibernate and tapestry together (see: http://www.cstengel.de/tutorial/trails_firebird_tutorial/)
And they use aspect-J - not that I dont like aspect-J, but .... I wont use it now and for this project, it should make our live easier with the tools we have to handle today and not introduce new technologies.
Also I would like to get in full touch with the JSF possibilities. If you use a framework which should handle tapestry and/or other web-frameworks you have to find the least possible set of possibilites.
So, I'll get ideas how they handle the persistence stuff, but even this I'll reimplement from scratch with the possibility in mind to plugin JBoss Seam later.
Ok, this is my view today, though, if there is something happening which will revert my mind it will be fine too.
--- Mario
