DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36659>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36659 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-16 09:44 ------- (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > (In reply to comment #1) > .. > > For this issue, the underlying problem is that your LoadBundle > > implementation > > doesn't make the messages available at component creation time. > > That's true. This component should come with a disclaimer. I added a note > in > the javadoc that warned against the rendered attribute stating that the > component is not immune to the rendered property like the JSP loadBundle tag. > > I suspect that that's why the JSF loadBundle is implemented as a JSP tag and > doesn't have a corresponding JSF component. > > I don't think that we can play by the same rules. But maybe a solution would > be to create a handler that could be associated to a meta-component > definition > that has callback methods similar to the shale view controller or the tiles > controller. It could be added to the component metadata and fired by the > chain used to build the component tree? > > <component preCreate=#{managed-bean-name.preCreate} postCreate=#{managed- > bean-name.postCreate} .> Or use the patch from bug #35935. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
