I've used the ignore option in the past. I referred to it as a problem because that's not what I wanted to happen in this case.
On my first attempts I did use an IoC service but it seems better to call component methods. If you want to call an IoC service it's easy enough to do that from the component. Also I've used GWT in Tapestry pages before and it seems much nicer to just say <t:helloComponent zone="counterZone" value="hello1" name="literal:test1"/> instead of all the stuff you need to get GWT to work. So the idea is you write a GWT module wrap a Tapestry component around it and use it just like any other Tapestry component. While this is not the typical use of GWT it allows you to write sophisticated client side Tapestry components in Java. For example I'd like to write one to display images and allow the user to zoom in. I could write that in Javascript/Prototype but I'd rather use Java. Barry --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
