When importing CSS stylesheets by <h:outputStylesheet>, the stylesheet is imported and processed by the FacesServlet through /javax.faces.resource/*. Look at the generated <link> element pointing to the stylesheet in question and you’ll understand. You have to change all url() dependencies to use #{resource[‘library:location’]} instead. JSF will then auto-substitute it with the right path. Given your folder … Read more
In short, @ManagedBean makes sense for applications that use JSF but do not use JSR 299 (whatever the reason is). Below a longer explanation from Gavin King: Re: Comparisons to @ManagedBean annotations in JSF2?: While looking through the Weld examples, and the older WebBeans documentation, it looks like a competitor to the new @ManagedBean JSF … Read more
Either just mention the URL directly in <a> or <h:outputLink>. <a href=”https://stackoverflow.com”>Go to this site!</a> <!– or –> <h:outputLink value=”https://stackoverflow.com”>Go to this site!</h:outputLink> Or, if you need to to invoke a bean action using <h:commandLink> like below, <h:form> <h:commandLink value=”Go to this site!” action=”#{bean.redirect}” /> </h:form> then use ExternalContext#redirect() in action method. public void redirect() … Read more
Use <o:deferredScript> Yes, it is possible with the <o:deferredScript> component which is new since OmniFaces 1.8.1. For the technically interested, here’s the involved source code: The UI component: DeferredScript The HTML renderer: DeferredScriptRenderer The JS helper: deferred.unminified.js Basically, the component will during the postAddToView event (thus, during the view build time) via UIViewRoot#addComponentResource() add itself … Read more
Introduction JSF generates HTML. HTML is in Java terms basically one large String. To represent Java objects in HTML, they have to be converted to String. Also, when a HTML form is submitted, the submitted values are treated as String in the HTTP request parameters. Under the covers, JSF extracts them from the HttpServletRequest#getParameter() which … Read more
You should realize that jQuery works with the HTML DOM tree in the client side. jQuery doesn’t work directly on JSF components as you’ve written in the JSF source code, but jQuery works directly with the HTML DOM tree which is generated by those JSF components. You need to open the page in webbrowser and … Read more
To the point, it has to be accessible by a public URL. Thus, the <img src> must ultimately refer a http:// URI, not something like a file:// URI or so. Ultimately, the HTML source is executed at enduser’s machine and images are downloaded individually by the webbrowser during parsing the HTML source. When the webbrowser … Read more
You probably already know that PrimeFaces is using jQuery under the covers. PrimeFaces Selectors are based on jQuery. Anything which you specify in @(…) will be used as jQuery selector on the current HTML DOM tree. For any found HTML element, which has an ID, exactly this ID will ultimately be used in the update. … Read more
You could register an instance of java.util.Date as a request scoped bean in faces-config.xml. <managed-bean> <managed-bean-name>currentDate</managed-bean-name> <managed-bean-class>java.util.Date</managed-bean-class> <managed-bean-scope>request</managed-bean-scope> </managed-bean> This way it’s available as #{currentDate} without the need for a custom backing bean class. Update: the JSF utility library OmniFaces has such a bean already registered as #{now}. So if you happen to use OmniFaces … Read more
Exceptions which are thrown during ajax requests have by default totally no feedback in the client side. Only when you run Mojarra with project stage set to Development and use <f:ajax>, then you will get a bare JavaScript alert with the exception type and message. But other than that, and in PrimeFaces, there’s by default … Read more