Richard Lewis-Shell <rlewisshell <at> mac.com> writes:

> I was actually thinking of nested annotations to declare a component. 

I added an initial version of using nested annotations to configure contained
components. The syntax is almost identical to the one you provided: 

http://paloalto.laughingpanda.com/svn/tapestry-annotation/trunk/
tapestry-annotation/src/test/fi/ri/tapestry/annotation/
TestComponentContainingComponents.java

Like Geoff pointed out, it may mean that you lose the "hot deploy" feature of
Tapestry though. Tomcat should be able to pick up changes to classes and reload
the classes by throwing away the original classloader which loaded the class.
This should be fine but I use Sysdeo tomcat plugin and its DevLoader do not seem
to have this kind of reload feature.

http://paloalto.laughingpanda.com/mediawiki/index.php/Tapestry_Annotations



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to