July 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13077) Allow programatically configure Resource Mapping by exposing a service interface

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13077?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13077: ---------------------------- Component/s: resource handling > Allow programatically configure Resource Mapping by exposing a service interface > -------------------------------------------------------------------------------- > > Key: RF-13077 > URL: https://issues.jboss.org/browse/RF-13077 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: resource handling > Reporter: Lukáš Fryč > > A concept of a service should allow to programatically provide a mapped URL for a resource, either local one (JSF resource) or remote (on static server, CDN, etc.). > {code:java} > public interface ResourceMapper { > /** > * @return null when no mapping should be involved > public ResourceMapping mapResource(ResourceKey key); > } > public interface ResourceMapping { > URL getURL(FacesContext context); > } > public interface StaticURLResourceMapping implements ResourceMapping { > URL getURL(); > } > public class FacesResourceMapping implements ResourceMapping { > public ResourceKey getResourceKey() { > ... > } > } > {code} > This way people may decide e.g. move all resources from given resource library to another library. > This is related to RF-11543. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13077) Allow programatically configure Resource Mapping by exposing a service interface

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13077?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13077: ---------------------------- Affects Version/s: 5.0.0.Alpha2 > Allow programatically configure Resource Mapping by exposing a service interface > -------------------------------------------------------------------------------- > > Key: RF-13077 > URL: https://issues.jboss.org/browse/RF-13077 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > A concept of a service should allow to programatically provide a mapped URL for a resource, either local one (JSF resource) or remote (on static server, CDN, etc.). > {code:java} > public interface ResourceMapper { > /** > * @return null when no mapping should be involved > public ResourceMapping mapResource(ResourceKey key); > } > public interface ResourceMapping { > URL getURL(FacesContext context); > } > public interface StaticURLResourceMapping implements ResourceMapping { > URL getURL(); > } > public class FacesResourceMapping implements ResourceMapping { > public ResourceKey getResourceKey() { > ... > } > } > {code} > This way people may decide e.g. move all resources from given resource library to another library. > This is related to RF-11543. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13078) Map all 'org.richfaces' resources (and other RF resources) to ResourceServlet

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13078: ------------------------------- Summary: Map all 'org.richfaces' resources (and other RF resources) to ResourceServlet Key: RF-13078 URL: https://issues.jboss.org/browse/RF-13078 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: resource handling Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč Some resources heavily uses relative resource links, e.g. font-awesome references fonts. We could provide static-resource-mapping.properties file We could leverage a mapping service proposed in RF-13077. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13077) Allow programatically configure Resource Mapping by exposing a service interface

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13077: ------------------------------- Summary: Allow programatically configure Resource Mapping by exposing a service interface Key: RF-13077 URL: https://issues.jboss.org/browse/RF-13077 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Lukáš Fryč A concept of a service should allow to programatically provide a mapped URL for a resource, either local one (JSF resource) or remote (on static server, CDN, etc.). {code:java} public interface ResourceMapper { /** * @return null when no mapping should be involved public ResourceMapping mapResource(ResourceKey key); } public interface ResourceMapping { URL getURL(FacesContext context); } public interface StaticURLResourceMapping implements ResourceMapping { URL getURL(); } public class FacesResourceMapping implements ResourceMapping { public ResourceKey getResourceKey() { ... } } {code} This way people may decide e.g. move all resources from given resource library to another library. This is related to RF-11543. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13076) r:push should verify that there are all preconditions for using Push functionality met

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13076: ------------------------------- Summary: r:push should verify that there are all preconditions for using Push functionality met Key: RF-13076 URL: https://issues.jboss.org/browse/RF-13076 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-push/poll Reporter: Lukáš Fryč Following should be checked: * is PushServlet initialized * are Atmosphere jars on classpath? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12270) Allow RichFaces to bring new CSS/JS resources into the page after AJAX request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12270?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12270: --------------------------------- Note that workaround is using [Resource Optimization|http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/e...] feature which serves aggregated resources. > Allow RichFaces to bring new CSS/JS resources into the page after AJAX request > ------------------------------------------------------------------------------ > > Key: RF-12270 > URL: https://issues.jboss.org/browse/RF-12270 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core, resource handling > Affects Versions: 4.2.2.Final > Reporter: Tomasz Kurpios > Fix For: 5-Tracking > > > Quoting the extract from official documentation (3.5 Restrictions): > ??JSF 2 does not allow resources such as JavaScript or Cascading Style Sheets (CSS) to be added if the element requiring the resource is not initially present in the JSF tree. As such, components added to the tree via Ajax must have any required resources already loaded. In RichFaces, any components added to the JSF tree should have components with corresponding resources included on the main page initially. To facilitate this, components can use the rendered="false" setting to not be rendered on the page.?? > > Setting rendered="false" is OK when components are in the tree. However, if there are lots of components on a single view, for performance reasons some parts might be excluded by means of <c:if> or <c:choose> tags. > That's at least what could be done in 3.3.3. It worked fine back then. However, the JSF2 AJAX mechanism does not support this feature. This makes usage of aforementioned tags impossible in some cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12270) Allow RichFaces to bring new CSS/JS resources into the page after AJAX request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12270?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12270: ---------------------------- Summary: Allow RichFaces to bring new CSS/JS resources into the page after AJAX request (was: Restore adding resources in AJAX requests) > Allow RichFaces to bring new CSS/JS resources into the page after AJAX request > ------------------------------------------------------------------------------ > > Key: RF-12270 > URL: https://issues.jboss.org/browse/RF-12270 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core, resource handling > Affects Versions: 4.2.2.Final > Reporter: Tomasz Kurpios > Fix For: 5-Tracking > > > Quoting the extract from official documentation (3.5 Restrictions): > ??JSF 2 does not allow resources such as JavaScript or Cascading Style Sheets (CSS) to be added if the element requiring the resource is not initially present in the JSF tree. As such, components added to the tree via Ajax must have any required resources already loaded. In RichFaces, any components added to the JSF tree should have components with corresponding resources included on the main page initially. To facilitate this, components can use the rendered="false" setting to not be rendered on the page.?? > > Setting rendered="false" is OK when components are in the tree. However, if there are lots of components on a single view, for performance reasons some parts might be excluded by means of <c:if> or <c:choose> tags. > That's at least what could be done in 3.3.3. It worked fine back then. However, the JSF2 AJAX mechanism does not support this feature. This makes usage of aforementioned tags impossible in some cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12270) Allow RichFaces to bring new CSS/JS resources into the page after AJAX request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12270?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12270: --------------------------------- The solution is tracking what resources were already rendered to the page. > Allow RichFaces to bring new CSS/JS resources into the page after AJAX request > ------------------------------------------------------------------------------ > > Key: RF-12270 > URL: https://issues.jboss.org/browse/RF-12270 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core, resource handling > Affects Versions: 4.2.2.Final > Reporter: Tomasz Kurpios > Fix For: 5-Tracking > > > Quoting the extract from official documentation (3.5 Restrictions): > ??JSF 2 does not allow resources such as JavaScript or Cascading Style Sheets (CSS) to be added if the element requiring the resource is not initially present in the JSF tree. As such, components added to the tree via Ajax must have any required resources already loaded. In RichFaces, any components added to the JSF tree should have components with corresponding resources included on the main page initially. To facilitate this, components can use the rendered="false" setting to not be rendered on the page.?? > > Setting rendered="false" is OK when components are in the tree. However, if there are lots of components on a single view, for performance reasons some parts might be excluded by means of <c:if> or <c:choose> tags. > That's at least what could be done in 3.3.3. It worked fine back then. However, the JSF2 AJAX mechanism does not support this feature. This makes usage of aforementioned tags impossible in some cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-10963) a4j:commandButton doesn't update the hidden javax.faces.ViewState from render form

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-10963?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-10963: ------------------------------------ Scheduling to 5.0.0.Alpha2 for review. > a4j:commandButton doesn't update the hidden javax.faces.ViewState from render form > ---------------------------------------------------------------------------------- > > Key: RF-10963 > URL: https://issues.jboss.org/browse/RF-10963 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Final > Environment: S.O.: Ubuntu 10.04 > Browser: Chrome > JSF Impl: JSF 2.0.2 > Reporter: Guilherme Moreira > Labels: community_contributor_needed > Fix For: 5.0.0.Alpha2 > > > A a4j:commandButton that's render another form causes this other form lost it's hidden input viewState. > Example > {code} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j"> > <f:view contentType="text/html" /> > <h:head> > </h:head> > <h:body> > <h:form id="aaa"> > </h:form> > <h:form id="bbb"> > <a4j:commandButton render=":aaa"/> > </h:form> > </h:body> > </html> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-10963) a4j:commandButton doesn't update the hidden javax.faces.ViewState from render form

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-10963?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-10963: ------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5-Tracking) > a4j:commandButton doesn't update the hidden javax.faces.ViewState from render form > ---------------------------------------------------------------------------------- > > Key: RF-10963 > URL: https://issues.jboss.org/browse/RF-10963 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Final > Environment: S.O.: Ubuntu 10.04 > Browser: Chrome > JSF Impl: JSF 2.0.2 > Reporter: Guilherme Moreira > Labels: community_contributor_needed > Fix For: 5.0.0.Alpha2 > > > A a4j:commandButton that's render another form causes this other form lost it's hidden input viewState. > Example > {code} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j"> > <f:view contentType="text/html" /> > <h:head> > </h:head> > <h:body> > <h:form id="aaa"> > </h:form> > <h:form id="bbb"> > <a4j:commandButton render=":aaa"/> > </h:form> > </h:body> > </html> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2013