Make sure you're doing all work in the JSF component, and none in a JSP tag handler. The tag handler should simply assign properties set on the tag to the component.
That will take care of the problem in general. There are specific cases where no component exists that have to be handled by writing an equivalent facelet tag handler (such as updateActionListener). On Wed, Jan 28, 2009 at 12:40 PM, Hazem Saleh <[email protected]> wrote: > Hello, > > I was digging in the exporter defect with Facelets[1], After a little > investigation, > I found that Facelets needs a special implementation for the listener tag > handler[2]. > > Is this correct? and Are there any possible better ways for solving this > defect? > > Thanks! > > [1] https://issues.apache.org/jira/browse/MFCOMMONS-3 > [2] > https://facelets.dev.java.net/source/browse/*checkout*/facelets/src/java/com/sun/facelets/tag/jsf/core/ActionListenerHandler.java?rev=1.3.2.1. > -- > Hazem Ahmed Saleh Ahmed > > Author of (The Definitive Guide to Apache MyFaces and Facelets): > http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370 > > Web blog: http://www.jroller.com/page/HazemBlog > > [Web 2.0] Google Maps Integration with JSF: > http://code.google.com/p/gmaps4jsf/ > http://www.theserverside.com/tt/articles/article.tss?l=IntroductiontoGMaps4JSF >
