[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402208#comment-13402208 ] Dmitry Kukushkin commented on MYFACES-3575: --- Still no good, using 2.1.8. My problem is that in public Facelet getFacelet(String uri) relative location is unconditionally cached, while in my case _resolver.resolveUrl(path) can return different URLs for the same path, depending on the application's internal state. The caching of the outcome of _resolver.resolveUrl(path) breaks this. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kukushkin reopened MYFACES-3575: --- Still no good, using 2.1.8. My problem is that in public Facelet getFacelet(String uri) relative location is unconditionally cached, while in my case _resolver.resolveUrl(path) can return different URLs for the same path, depending on the application's internal state. The caching of the outcome of _resolver.resolveUrl(path) breaks this. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402236#comment-13402236 ] Dmitry Kukushkin commented on MYFACES-3575: --- Is it not just making this _relativeLocations expiring, as it is done for _compositeComponentMetadataFacelets in the DefaultFaceletFactory class? This IMO will be more consistent instead. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402263#comment-13402263 ] Dmitry Kukushkin commented on MYFACES-3575: --- This is what I meant, why not to make _relativeLocations cache also expiring, like it is done for _compositeComponentMetadataFacelets? Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
Dmitry Kukushkin created MYFACES-3575: - Summary: Disable relative location caching in DefaultFaceletFactory Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14 Environment: Linux Reporter: Dmitry Kukushkin Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
