![]() So the problem isn't with liferay-faces-bridge, it's actually an incompatibility between $ntime() and the tag, which utilizes WebKeys.PAGE_TOP for adding resources to the section of the portal page. And that's the JSP that refers to the WebKeys.PAGE_TOP request attribute for adding resources to the section of the portal page. Servlets primefacesiTextPdf servlets pdf itext Servlets Javaservletcookie servlets cookies Servlets jax-rsjeeHttpServlet servlets jakarta-ee Servlets servletserver. But because the "runtime" portlet is added dynamically via Velocity, the portlet lifecycle for the runtime portlet isn't run until AFTER the $top_head_include (top_head.jsp) is executed. PrimeFaces is an open source JSF component suite with various extensions. In a normal portlet scenario, all of the portlets undergo the portlet lifecycle prior to this Velocity template getting run. PrimeFaces is a popular open source framework for JavaServer Faces featuring over 100 components, touch optimized mobilekit, client side validation, theme engine and more. I think maybe the best way to understand the problem, is to take a look at a typical Liferay theme portal_normal.vm Velocity Template: issue was first reported in the forums here: Public class NormalActionListener implements void processAction(ActionEvent event) Between these two, I would recommend going with PrimeFaces, it is much more mature. JSF is the framework, and PrimeFaces and BootsFaces are two component libraries for it (components as in ui controls). None of the things you listed here is a framework. Implementation of ActionListener interface Answer: You’re messing things here a lot. In button or link component, add a “ f:actionListener” tag inside, and specified an implementation class of ActionListener interface, and override its processAction(). Two-thirds of the imported components saw significant code change associated with feature enhancements or bug fixes. And since Primefaces is the original one and is super active project Id say without a doubt is the right choice. ![]() (they took the entire primefaces source code.) INMO, you better stick to one of them only. The method which interacts action event should accept a ActionEvent parameter.īuttonId = event.getComponent().getClientId() Of the 28 PrimeFaces components integrated, 100 were subject to modifications and/or refactoring needed for them to work within the ACE environment (including code generation), the ICEfaces Framework, and our QA processes. but be aware that the latest Icefaces is actually a 100 wrapped Primefaces. In button or link component, you can specified a bean’s method directly in the “ actionListener” attribute. We integrated popular component elements from PrimeFaces, jQuery and YUI projects into the ICEfaces framework and combined. In constructing the ACE library, ICEsoft sourced components from the very best open source solutions we could find. Do not confuse these two tags, actions is used to perform business logic and navigation task While action listeners are used to perform UI interface logic or action invoke observation.Ĭommon use case of this action listener is used to get back the attribute value that’s attached to a component, see this JSF 2 f:attribute example. ICEsoft is proud of its new ACE library and the advancements it represents to the open source community.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |