A more feasible way could be to sublcass ListenerInterfaceRequestTarget so that the getTarget() method will return a proxy intercepting the Seam annotations. <br><br>Or subclassing the RequestListenerInterface to override the invoke() method always to swap the component target with a proxied instance. <br>
<br>I will try to provide an example.<br><br>// Paolo<br><br><div class="gmail_quote">On Mon, May 12, 2008 at 5:08 PM, Pete Muir <<a href="mailto:pmuir@bleepbleep.org.uk">pmuir@bleepbleep.org.uk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I did consider forcing creation of seam-enabled wicket components through a factory and just returning a proxy, however this struck me as fairly un-wicket-like as it seemed to me that the simplicity of Wicket was that you could use new and anonymous inner classes. Maybe we do a POC using factories for now, and look at classloading tricks or Paolo's idea as a second step.<div>
<div></div><br></div></blockquote></div>