I've just tried your code (I commented your second addMessage, put @RequestScoped and remove composition) and it works great on Primefaces 5.1 and Mojarra 2.2.8! I noticed that your log output is: client Id :bcr_form_2:bcrId_tabview:saveDemandId_cmdbutton But pay attention to log line code: log.info("client Id :" + myMessageCId.getClientId(context)); The leading semicolon...
I reproduced your problem. This is the consequence of issue 3021 which was applied since Mojarra 2.2.5. The locale is now determined during view build time. Previously, at time of writing the answer you found, the locale was determined during view render time which allowed the code to find view's...
jsf,jsf-2.2,omnifaces,graphicimage
As stated in its documentation and showcase, In case the property is a method expression taking arguments, each of those arguments will be converted to a string HTTP request parameter and back to actual objects using the converters registered by class as available via Application.createConverter(Class). So, most of standard types...
The <f:viewAction onPostback="true"> applies only on postbacks on the very same view. I.e. it runs only when a <h:form> in the very same view has been submitted. The <f:viewAction> is never intented to be executed upon POST navigation triggered by a submit of a <h:form> of another view. Moreover, the...
Considering that I have not found the right answer to the concrete question, and after consultation with some of the people I have come to the conclusion that I will solve the problem if I disable printing of the page before submiting it. So, when the page is printed after...
jsf,file-upload,initialization,jsf-2.2
You can't. This restriction is already in HTML side. You can't preset the value of an <input type="file"> field. That would be a major security hole as that would allow web pages to unaskingly upload completely arbitrary files from the client to the server. You would as enduser not be...
But maybe there is another CDI way with producers or something Indeed, you could use a producer. Kickoff example: @SessionScoped public class SessionBean { @Produces @Named("foo") @SessionScoped public SessionBean getAsFoo() { return new SessionBean(); } @Produces @Named("bar") @SessionScoped public SessionBean getAsBar() { return new SessionBean(); } // ... }...
jsf,resources,java-ee-6,jsf-2.2,mojarra
Answering the question based on @Tarik's comment. I added this to my faces-config.xml: <application> <resource-handler>my.package.MyResourceHandlerImplementation</resource-handler> </application> MyResourceHandlerImplementation looks like this: import com.sun.faces.application.resource.ResourceHandlerImpl; public class MyResourceHandlerImplementation extends ResourceHandlerImpl { @Override public String getRendererTypeForResourceName(String resourceName) { if (hasQueryString(resourceName)) { resourceName =...
authentication,ldap,jboss7.x,jsf-2.2,wildfly
i presumed that this security realms were meant to authenticate the application server console access You're partially correct there. The name="ManagementRealm" does indeed specify a realm config for accessing admin functions. name="ApplicationRealm" would be the attribute to specify for securing a web application Your current realm config is missing...
As you can see on the TagDecorator page you linked to, the 'html5 friendly' markup is only relevant to 'basic' inputs, buttons and links. PrimeFaces has some counterparts of these to, but if you take a closer look at the real advantage of this 'html5 friendly' notation, it mainly on...
ok the answer is simple guys.. i had the same issue ! just be sure to follow it =). its indeed a bug of glassfish 4.1. nucleus Grizzly jar file has a problem and there is a patch for it. Just replace this file in your glassfish jar files. with...
To work, <p:dataTable> has to be inside a <h:form>.
html,jsf,jsf-2.2,valuechangelistener
In the first example where you use simple HTML, the reason behind the navigation after submit is related to the action attribute, which is specified with the name of the page you want to send your data to it <form action="success.html" >, so your this.form.submit() will send the form data...
What about you make a single unauthorized page that acts like a entry point now on his page redirect to required pages 403.jsp <shiro:hasRole name="admin"> <c:redirect url="adminAuthPage.xhtml"/> </shiro:hasRole> <shiro:hasRole name="user"> <c:redirect url="abortPage.xhtml"/> </shiro:hasRole> Or better if you just want admin has another page then <shiro:hasRole name="admin"> <c:redirect url="adminAuthPage.xhtml"/> </shiro:hasRole> <shiro:lacksRole...
Below is the syntax for calling a method call node in FacesFlow - <flow-definition id="someFlow"> <start-node>start</start-node> <method-call id="start"> <method>#{bean.init}</method> <default-outcome>success</default-outcome> </method-call> <view id="initSuccess"> <vdl-document>/pages/init.xhtml</vdl-document> </view> </flow-definition> where #{bean.init} returns outcome as "initSuccess" upon which init.xhtml is rendered. success is the default outcome...
This is not a JSF specific behavior, when Enter is pressed the first <input> with type="submit" is used. This has been discussed on SO (see this or this), I'll put here some of the suggestions from those threads. Javascript solution: Use <h:form id="thisform" onkeypress="if( event.keyCode == 13){event.keyCode=0;}"> on your form....
As per the EG discussion, there's agreement on Mojarra behavior being correct as it's in line with how actionListener/action work. The MyFaces guy has created an issue on it and it's expected that this will be fixed for next MyFaces release. And, the JSF spec should be more explicit in...
jsf,annotations,jsf-2.2,custom-component,embedded-tomcat-8
Alright, I figured out what was causing the issue. This morning I sat down to think about the differences between my working Servlet 3.1 version of the code, and the broken Spring Boot version. The main difference was how the code was being run. Embedded server vs. Standalone. Spring Boot's...
jsf,deployment,richfaces,jsf-2.2
Frontend artifacts don't belong in EAR's /lib. They belong in WAR's /WEB-INF/lib. It would otherwise make the backend (the EJB) totally unreusable on other frontends (other WARs), such as Spring MVC, JAX-RS RESTful, "Plain vanilla" JSP/Servlet, etc..etc.. Using/importing JSF FacesContext and friends such as Servlet's HttpServletRequest in an EJB class...
This is caused by statefulness of the <f:viewParam>. JSF utility library OmniFaces has solved this with its <o:viewParam>. See also: Process f:viewParam only on page load ...
JSP is deprecated since JSF 2.0. It's succeeded by Facelets (XHTML). Therefore, JSF 2.0 compatible component libraries like RichFaces 4+ and PrimeFaces 2+ do not support JSP anymore. Those component libraries do not contain JSP taglibs anymore. Hence this error. Migrate JSP to its successor Facelets. See also: Migrating from...
java,model-view-controller,cdi,jsf-2.2
Foo implements Serializable is necessary but not sufficient for Foo to be serializable. All members of Foo also have to be serializable. In your case, ProfileController is serializable, but its UserService member is not....
If it needs to transcend the session, then I'd suggest not storing it in the session at all. Use a separate cookie.
As getViewRoot() only return elements which are written on xhtml file I've decided to save dynamic components in a map and when I place this dragabble component in the right site the I pass css style and other properties through managed bean properties, so every time a new panel is...
It's consequence of a bugfix in Weld implementation of WildFly 9. As per issues CDI-525, WELD-1941 and WFLY-4877, the CDI spec appears to be not consistent with JavaBeans specification as to default managed bean name in case the unqualified classname starts with more than two capitals. CDI spec merely stated...
Here username is the property of UserBean.java class. As a result, you must have to call the username variable through a object of the parent(UserBean.java) class.So, try it, mbean.getUsername() instead of only username.
java,jsf,redirect,jsf-2.2,java-ee-7
1st question I see two options here. You can check on page a.xhtml that user has been there (and entered information) and redirect it to normal.xhtml You can switch to programmatic login, make a custom jsf page and execute backing bean method similar to this String login(){ HttpServletRequest request =...
Possible solution: Write your own CommandLink-Renderer (Mojarra: com.sun.faces.renderkit.html_basic.CommandLinkRenderer) which evaluates a href-Param and sets it as a href="JF-Outcome" instead of the href="#" <h:commandLink value="Klick me" action="#{beanAction}"> <f:param name="href" value="JSF-Outcome" /> </h:commandLink> Non JavaScript users follow the link, the others post the form....
Seems like this is because it scales based on width. In tabview width of panelgrid is much smaller, than outside. In this case, I would suggest to create css styles for each component and apply them, rather then making them stretch automatically
As you already noticed, the page event is being fired before the selected number of rows has been applied to the table. At the moment, there is no event being fired after changing the number of rows. However, there is a possible workaround: bind your datatable to the backing bean...
jsf,jsf-2.2,myfaces,prettyfaces
The URL in the browser isn't going to change automatically. PrettyFaces maps pretty URLs to internal URLs. So if you request: http://localhost:9080/projectName/login You would actually see the /pages/unsecure/login.jsf page as specified in the configuration. Navigation using JSF navigation or internal redirects to this page will automatically use the pretty URL....
The outcome attribute should be completely omited: <h:link value="self link" /> ...
Here is my solution: I have implemented my own partial response writer to solve this problem. Now I'm able to set the tag to the partial response. (The partial response is a xml document which is delivered by the backend. this document contains a set of commands and data, which...
Found the problem, I was trying to start the flow calling the initial node using a link, like this: <h:link id="link1" styleClass="link" value="Link" outcome="/signup/signup.xhtml"></h:link> Instead I replaced the link with a commandButton and in the action parameter I used the flow name, like this: <h:commandButton id="start" value="Signup User" action="signup"/> And...
this work for me My file in folder path WEB-INF\pages\forms cod in xhtml file <h:commandLink value="Download" action="#{formBean.downloadFile('FileName.doc')}" styleClass="link"/> beans public String downloadFile(String fileName) { try { FacesContext facesContext = FacesContext.getCurrentInstance(); HttpServletResponse response = ((HttpServletResponse) facesContext.getExternalContext().getResponse()); String reportPath = facesContext.getExternalContext().getRealPath("\\pages\\forms") + File.separator + fileName;...
With JSF 2.2 you can pass the values as method parameters. public void HRCESS(String employeeCode, String reqNo) ...
jsf,file-upload,jsf-2.2,multipartform-data
JSF won't save the file in any predefined location. It will basically just offer you the uploaded file in flavor of a javax.servlet.http.Part instance which is behind the scenes temporarily stored in server's memory and/or temporary disk storage location which you shouldn't worry about. In order to save it to...
I found a way to get this jar. Following are the steps : Download the source for WildFly 8.2.0. Go to location : <WILDFLY_SOURCE_ROOT>/jsf/multi-jsf-installer. Run below command - mvn -Djsf-version=2.2.7 -Pmyfaces clean assembly:single This will create .zip file which should be renamed to .cli. Please follow the link - here...
As per the comments, you declared the XML namespace xmlns:jsf on URI http://java.sun.com/jsf, based on the old java.sun.com host. This has a bug in older Mojarra versions. New JSF 2.2 specific features such as <f:viewAction> and "HTML5 friendly markup" weren't initially available on XML namespace with the old java.sun.com host...
As @BalusC wrote in his comment this exception occurs when backend tree is changed while UI tree is building. When p:treeTable builds it calls getTree() method really many times, at least once for each category. If one of these calls receives a TreeNode object which does not equal the others...
Solved the problem. As commented the problem was with the template Engine that it wasn't able to understand some of the operators. By putting it in a cdata filed i solved the problem. Solution: <script type="text/javascript"> //<![CDATA[ var span = $("[id='span#{component.clientId}']"); var linkShow = $("<a/>"); linkShow.attr("id", "linkShow#{component.clientId}"); linkShow.attr("style", "color: #07A0DD;");...
validation,jsf,jsf-2.2,conditional-rendering
You can make use of FacesContext#isValidationFailed(). It will return true if validation has failed in the current JSF lifecycle. The current instance of FacesContext is available also in EL as #{facesContext}. Just check it in the rendered attribute and update its parent placeholder component. Do note that you can't conditionally...
html5,jsf,facelets,jsf-2.2,passthrough-attributes
No, this is caused by the XHTML standard: XML does not support attribute minimization. Attribute-value pairs must be written in full. Attribute names such as compact and checked cannot occur in elements without their value being specified. From http://www.w3schools.com/tags/att_input_autofocus.asp Differences Between HTML and XHTML In XHTML, attribute minimization is forbidden,...
jsf,file-upload,jsf-2.2,passthrough-elements
From the jsf tutorial <input type="file" jsf:id="myFile" jsf:value="#{bean.file}"/> Is the adviced way...
Solved. On beans.xml with bean-discovery-mode="annotated" doesn't work. Then change to bean-discovery-mode="all" and works fine....
javascript,jquery,datepicker,jsf-2.2
I finally resolved to use this workaround; I changed my code like this: <f:ajax execute="@form" render="@all"> Instead of: <f:ajax execute="@form" render="@form"> This way, all the page is loaded. ...
I just forgot to add <Context> <Resource name="BeanManager" auth="Container" type="javax.enterprise.inject.spi.BeanManager" factory="org.jboss.weld.resources.ManagerObjectFactory" /> </Context> to the context.xml....
You can't ajax-update a plain HTML element. You can only ajax-update a JSF component. Simple reason is that the target must be resolveable by UIViewRoot#findComponent(), so that JSF can find it in the component tree and render the updated HTML into the Ajax response. Replace <div id="addedBooksTable"> by <h:panelGroup layout="block"...
After the page has been fully rendered, the @RequestScoped bean is destroyed along with all its instance variables (including the user). I presume this is the point at which you then attempt to execute editUser() which results in an NPE. Use a @ViewScoped bean instead, to ensure your instance variables...
jsf,jsf-2.2,mojarra,programmatically-created
Component IDs are not stored in JSF view state. They are like components themselves thus basically request scoped. Only stuff which is stored in JSF view state is basically view scoped. I.e. the stuff which components put/get via getStateHelper() method. The getId()/setId() methods doesn't do that. When JSF needs to...
Closest you can get is the referer header via ExternalContext#getRequestHeaderMap(): String referrer = externalContext.getRequestHeaderMap().get("referer"); // ... You should only keep in mind that this is a client-controlled value and can thus be fully spoofed from client side on (i.e. the enduser can easily edit or even remove it). Even then,...
jsf,jsf-2.2,omnifaces,graphicimage
I can store all the images in the database with no problem. This was thus actually not true. Those images appear to be empty or filled with only zeroes. How to grab the uploaded file content from a <p:fileUpload>, head to the following answers: How to use PrimeFaces p:fileUpload?...
As part of safeguard against tampered/hacked requests, the disabled attribute is also evaluated during apply request values phase of the form submit. So basically you need to make sure that #{switchMB.isTrue} evaluates exactly the same as it did during rendering the form. The easist way is to put the #{switchMB}...
The <o:graphicImage> sets a default content type of image, but your browser apparently didn't swallow that for SVG images. As per this commit, I've for OmniFaces 2.1 added SVG support for <o:graphicImage dataURI="true"> and I've added a new type attribute which allows you to explicitly specify the image type via...
jsf,datatable,el,jsf-2.2,setpropertyactionlistener
You kind of coded your self into a corner with your fancy bean implementation. Take a look at the processing steps for the f:setActionPropertyListener. Your code is choking at step 3: If the value of the "value" expression is not null, call getType() on the "value" and "target" ValueExpressions to...
ajax,jsf-2,jsf-2.2,composite-component
java.lang.NullPointerException at com.sun.faces.facelets.tag.jsf.core.AjaxHandler.applyAttachedObject(AjaxHandler.java:333) Let's check the source of AjaxHandler#applyAttachedObject(): 332 Collection<String> eventNames = bHolder.getEventNames(); 333 if (!eventNames.contains(eventName)) { 334 throw new TagException(this.tag, 335 getUnsupportedEventMessage(eventName, eventNames, parent)); 336 } Aha, getEventNames() returned null. That method was implemented on UIComponentBase whose javadoc says the following: This is a default...
Web fragment JARs belong in WAR/WEB-INF/lib and absolutely not in EAR/lib nor Server/lib. See also a.o. chapter 8.1 of Servlet 3.0 specification (emphasis mine): 8.1 Annotations and pluggability In a web application, classes using annotations will have their annotations processed only if they are located in the WEB-INF/classes directory, or...
jsf,migration,jsf-2.2,nosuchmethoderror
That method was introduced in JSF 2.2. This problem will thus happen when the webapp's runtime classpath is polluted with multiple different versioned JSF API libraries. In other words, you've still a JSF 2.0 or 2.1 API somewhere in the runtime classpath. This suggests that you're trying to upgrade JSF...
javascript,jquery,html,checkbox,jsf-2.2
You need to use nextAll and prevAll (along with the firstpseudo selector) as you have anchors in between your checkbox and textbox. I would also change the click event to change $(function () { $("input[type=checkbox]").on('change', function () { $(this).nextAll('.ckval:first').val($(this).is(':checked') ? '1' : '0'); }); $("input[type=text]").on('keyup', function () { if ($(this).val())...
When an suscribe or unsuscribe action is completed, you should actualize the DataGrid trough its ID, it is, set an ID to the DataGrid and put such id in the update property of the buttons. For example: <p:dataGrid id="datalist" .../> <p:commandButton action="#{packageView.Unsubscribe}" update="datalist" .../> And when the action of the...
jsf,jsf-2.2,wildfly-8,prettyfaces
Have you tried a more recent version of Wildfly or PrettyFaces? Please see the updated installation instructions here: http://ocpsoft.org/prettyfaces/ (Note: PrettyFaces is now an extension of rewrite.)...
validation,jsf,facelets,jsf-2.2,uiinclude
There's no way of handling an exception from the view side on when it's the view itself who is causing the exception. You can use ViewDeclarationLanguage#viewExists() to check if a given view exists. You should do this before setting the srcPage and if necessary get hold of the wrong value...
jsf,primefaces,jsf-2.2,blacklist
There's no such thing in standard JSF/PrimeFaces API. Quick'n'dirty workaround would be overriding the component registration in webapp's faces-config.xml whereby you set the component class to a non-UIComponent class (it will ultimately throw ClassCastException on usage), or to a custom UIComponent which throws e.g. IllegalArgumentException in its constructor. E.g. if...
jsf-2,viewstate,jsf-2.2,myfaces
This is specified/expected behavior when using client side state saving. The JSF view state is not saved in the session, but in its entirety in a hidden input field in the HTML form in the client side. Only when using server side state saving, the JSF view state will invalidate...
spring-boot,jsf-2.2,prettyfaces
When you're using Spring Boot with an embedded container web.xml and web-fragment.xml are ignored. You need to register the PrettyFaces filter in your application's Java configuration: @Bean public FilterRegistrationBean prettyFilter() { FilterRegistrationBean prettyFilter = new FilterRegistrationBean(new PrettyFilter()); prettyFilter.setDispatcherTypes(DispatcherType.FORWARD, DispatcherType.REQUEST, DispatcherType.ASYNC, DispatcherType.ERROR); prettyFilter.addUrlPatterns("/*"); return prettyFilter; } Spring Boot could be improved...
jsf,redirect,error-handling,jsf-2.2,viewparams
When I add required="true", nothing happens You need <h:message(s)> to show faces messages associated with a given (input) component. You probably already know how to do that for <h:inputText>. You can do exactly the same for <f:viewParam>. <f:metadata> <f:viewParam id="foo" ... required="true" /> </f:metadata> ... <h:message for="foo" /> Сan...
ajax,jsf,jsf-2,jsf-2.2,wildfly
This is a bug in Mojarra. I've just reported it as issue 3968. For now, one work around is to pass them as EL method arguments instead. <h:form enctype="multipart/form-data"> <h:commandButton value="Submit" action="#{bean.action(true)}"> <f:ajax execute="@this" render="@this"/> </h:commandButton> </h:form> public void action(boolean myparam) { // ... } ...
ajax,jsf,exception-handling,jsf-2.2
This problem is known and fleshed out in among others the OmniFaces FullAjaxExceptionHandler showcase. Basically, you need to create a custom ExceptionHandler as standard JSF doesn't provide one out the box (at least, not a sensible one). Therein you will be able to get hands on the Exception instance causing...
You are using both @ManagedBean and @Named annotations, you must use only one of them. As you are using javax.enterprise.context.SessionScoped for the @SessionScoped which mean that you are using CDI Managed beans, then you should only use @Named to make your bean CDI managed. You can check BalusC's answer for...
To address the core of your question, implement a ViewHandler, within which you can take control of the RESTORE_VIEW and RENDER_RESPONSE phases/processes. You'll save the view during the RENDER_RESPONSE and selectively restore, during the RESTORE_VIEW phase. Your view handler could look something like the following public class CustomViewHandlerImpl extends ViewHandlerWrapper{...
Better to use the omnifaces generic enum converter. It keeps your code cleaner compared to 'manually' doing conversions of lists etc...
I solved restarting NetBeans and GlassFish Server. I didn't add the name property to @ManagedBean: package firstcup.web; import javax.ejb.EJB; import javax.faces.bean.ManagedBean; import javax.faces.bean.SessionScoped; @ManagedBean @SessionScoped public class DukesBDay { and everything works, so it isn't necessary (according to naming convention, you can refer to the bean using the uncapitalized short...
java,xhtml,increment,jsf-2.2,instance-variables
Is your bean request scoped ? In that case the variables will be created again after each click
Only use it if you want to use a @FlowScoped bean on a given set of views. In other words, only use it if you want a managed bean which should live as long as you're navigating through the specified collection of views registered in the flow configuration file. There...
jsf,converter,jsf-2.2,passthrough-elements
Just the same way as when you would be using a normal JSF <h:inputText> component instead of plain HTML, with either the converter attribute <input jsf:value="#{...}" jsf:converter="fooConverter" /> or the <f:converter> tag. <input jsf:value="#{...}"> <f:converter converterId="fooConverter" /> </input> Table 8-4 of the Java EE 7 tutorial lists which JSF component...
jsf-2,primefaces,tags,jsf-2.2,custom-component
Why not rewrite/modify it's JavaScript functions (in autocomplete.js) ? code & functions of interest : bindStaticEvents bindStaticEvents: function() { var $this = this; this.bindKeyEvents(); this.dropdown.mouseover(function() { $(this).addClass('ui-state-hover'); }).mouseout(function() { $(this).removeClass('ui-state-hover'); }).mousedown(function() { if($this.active) { $(this).addClass('ui-state-active'); } }).mouseup(function() { if($this.active) { $(this).removeClass('ui-state-active'); $this.search(''); $this.input.focus(); }...
apache,jsf,authentication,jsf-2.2,shiro
Okay... I did a little more digging and it seems I can't use CDI injection directly into the Shiro JDBC realm like I tried to do above... There is an conflict between the management Shiro is doing with it's own beans, and CDI with its own. I did find this...
ajax,jsf,file-upload,jsf-2.2,commandlink
I updated JSF 2.2.4 to JSF 2.2.6. If I choose a file and click on link "upload", then sending is not working. But if I click again, then sending is working. I changed <f:ajax event="blur" render="fileMessage"/> to <f:ajax event="change" render="fileMessage"/>. And sending is working with the first click....
Basically, this can be achieved like this: use a hidden input field (like h:inputHidden) in the filter facet to hide the default filter input field put a p:calendar in the header facet add a dateSelect event onto your calendar. In onstart replace the value of your hidden input by the...
java,java-ee,jsf-2.2,oracle-adf
If the user is closing ONLY the tab containing the application, but not the browser, the user doesn't need to login again - this is how authentication works with Java Servlet API and ADF is built on this API. This happens because all browser tabs share the same http session...
You can specify the ordering via <ordering> in faces-config.xml of the JAR. E.g. if you want your utility library to be loaded after all others, then just do so: <ordering> <after> <others /> </after> </ordering> If you want to force an explicit ordering, then hook on specifically PrimeFaces, which has...
jsf,facelets,jsf-2.2,uirepeat,outputstylesheet
The <h:outputStylesheet> (and <h:outputScript>) needs to be present during view build time in order to let the JSF resource management to properly pickup them. The <ui:repeat>, however, runs during view render time only, it would be too late for JSF to perform relocation actions (moving to bottom of head or...
Here, <p:commandButton ... ajax="false" /> Ajax is turned off. Thus a full page refresh is performed after submitting the form. That the checkbox got unchecked suggests that the bean doesn't properly keep its state, or that you're performing business logic in a getter method, which causes it to return a...
Use the <f:passThroughAttribute/> to set custom attributes. The th can be rendered by setting rowHeader="true" on an <h:column/> <h:dataTable> <h:column rowHeader="true"> <h:outputText value="Header Column"/> <f:passThroughAttribute name="my-attribute" value="myattributevalue"/> </h:column> </h:dataTable> ...
The <option> element is by default not recognized as a passthrough element. It's not listed in table 8.4 of Java EE tutorial chapter 8.9 'HTML5-Friendly Markup'. You'd need to explicitly tell the underlying JSF component. You can do that using the jsfc attribute, which is surprisingly not mentioned in the...
Don't wan't to disagree with BlagusC (the one and only here ;-) ) but for normal changes "hotdeployment" should work fine. Only if you change backing beans structure (e.g.: add methods, add classes) restart is needed. Important thing is that you start the server in debug mode - here are...
jsf,el,jsf-2.2,methodexpression
JSF doesn't permit that kind of actionlistener binding, simple. The only semblance to what you have in the JSF world, is a standalone implementation of the ActionListener interface, with which you can then supply a FQN: <h:commandButton> <f:actionListener type="com.you.YourActionListenerImpl" /> </h:commandButton> Where YourActionListenerImpl will be a class implementing ActionListener as...
jsf-2,jsf-2.2,wildfly,picketlink,resource-contracts
I was able to solve my problem with the following security configuration: .forPath("/javax.faces.resource/*.png.xhtml").unprotected() I've seen in my Firefox Inspector that the browser tried to load the image from /MyTestProject/javax.faces.resource/logo-main.png.xhtml?con=TemplateBlue, so trying the above seemed logical and it works!...
jsf-2,jsf-2.2,composite-component
Digging deeper, I found some evidence of a bug, so I reported it. I'll update the answer to see if it is really a bug or some big misconception from me.
jsf,redirect,navigation,jsf-2.2,prettyfaces
Your Join looks strange. You should not use query parameters in the to() part. Rewrite automatically converts all path parameters to query parameters. So instead of: .addRule(Join.path("/page1/{param}").to("/view/page1.jsf?product={param}")) You should try: .addRule(Join.path("/page1/{product}").to("/view/page1.jsf")) Now your navigation should work. But please include the redirect element. That’s required for the URL to change....