[jira] [Commented] (MYFACES-3789) Change default refresh period for facelets from 2 to 0 sec (=always refresh)

["Martin Kočí (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/MYFACES-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997819#comment-13997819 ] 

Martin Kočí commented on MYFACES-3789:
--------------------------------------

@Leonardo, what do you think about this ? 
Alternatively, can we always set the refresh period as -1 in Production (in FaceletViewDeclarationLanguage.createFaceletFactory) ? 

> Change default refresh period for facelets from 2 to 0 sec (=always refresh)
> ----------------------------------------------------------------------------
>
>                 Key: MYFACES-3789
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3789
>             Project: MyFaces Core
>          Issue Type: Wish
>            Reporter: Martin Kočí
>            Priority: Trivial
>         Attachments: MYFACES-3789.patch
>
>
> A typical developer works as follows
> 1) edits a facelets view  (template, composite component)
> 2) CTRL +S
> 3) refresh in browser (or LiveReload)
> but: from 2) to  3) takes it sometimes less as 2 secs and the programmer must repeat the 3)
> We can override this behaviour with context-param:
> javax.faces.FACELETS_REFRESH_PERIOD=0
> but then is for development neccesary:
> javax.faces.PROJECT_STAGE=Development
> javax.faces.FACELETS_REFRESH_PERIOD=0
> and for Production:
> javax.faces.PROJECT_STAGE=Production
> javax.faces.FACELETS_REFRESH_PERIOD=-1
> that means a configuration of 2 params instead of one (ProjectStage) (the problem is:  javax.faces.FACELETS_REFRESH_PERIOD when not default always wins  and PROJECT_STAGE=Production doesn't set FACELETS_REFRESH_PERIOD to -1)
> with default refresh period = 0 makes the method FaceletCacheFactoryImpl.getFaceletCache() the job and only javax.faces.PROJECT_STAGE=Production is necessary.
> Does anybody know why is the default 2 seconds ?



--
This message was sent by Atlassian JIRA
(v6.2#6252)