Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Make a p:calendar readonly

I want to make <p:calendar> readonly so that users can only choose a date from the calendar because of this issue (this is not a solution though).

For this to be so, I'm doing readonly="#{facesContext.renderResponse}" as mentioned by this answer like,

<p:calendar id="calendarId" 
        value="#{bean.property}" 
        converter="#{jodaTimeConverter}" 
        pattern="dd-MMM-yyyy hh:mm:ss a" 
        showOn="button" 
        readonly="#{facesContext.renderResponse}" 
        effect="slideDown"
        required="true" 
        showButtonPanel="true" 
        navigator="true"/>

This works but when the page is loaded (typing the URL in the address bar and then pressing the enter key), facesContext.renderResponse returns false and the calendar is no longer readonly. It evaluates to true, when I submit the form by pressing <p:commandButton>.

So, how to make the calendar readonly, when the page is loaded?

P.S : I'm using PrimeFaces 3.5 and Mojarra 2.1.9.

like image 268
Tiny Avatar asked Jul 14 '13 12:07

Tiny


People also ask

How do I make my p calendar readonly?

When setting the attribute readonly="true", mode="popup", showOn="focus", the date selection dialog still opens as soon as the text input component gains focus. From there, the user can select a date/time and the p:calendar text input value is changed accordingly.


1 Answers

The behavior has indeed changed since JSF 2.0. The FacesContext#getRenderResponse() only returns true if FacesContext#renderResponse() is explicitly been called. Previously this happened during restore view phase of every GET request. However, since the introduction of <f:viewParam>, JSF will not do that anymore when at least one view parameter is present, it will just continue executing every single phase without skipping any phase in order to properly process the view parameters.

You apparently have a <f:viewParam> in your page. That's totally fine, but as a test, try removing it and you'll see that it returns true on a plain GET request as well.

You've basically 2 options to get around it:

  1. Check the FacesContext#isPostback() as well. It always returns false on GET requests.

    readonly="#{not facesContext.postback or facesContext.renderResponse}"
    
  2. Check the FacesContext#getCurrentPhaseId() instead. You only end up with uglier code (magic numbers).

    readonly="#{facesContext.currentPhaseId.ordinal eq 6}"
    

    If you're using OmniFaces, you could make it less ugly.

    <o:importConstants type="javax.faces.event.PhaseId" />
    ...
    readonly="#{facesContext.currentPhaseId eq PhaseId.RENDER_RESPONSE}"
    
like image 189
BalusC Avatar answered Oct 15 '22 07:10

BalusC