[JBoss JIRA] (RFPL-2331) collapsible panel: add section about headerCollapsed and headerExpanded facets
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2331?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2331:
--------------------------------
Sprint: 4.3.0.CR1 Doc Corrections
> collapsible panel: add section about headerCollapsed and headerExpanded facets
> -------------------------------------------------------------------------------
>
> Key: RFPL-2331
> URL: https://issues.jboss.org/browse/RFPL-2331
> Project: RichFaces Planning
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.0.0.Final, 4.1.0.Final
> Reporter: Lance Sloan
> Labels: collapsiblePanel, docs, headerCollapsed, headerExpanded
> Fix For: 4.3-Tracking
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> While attempting to use collapsiblePanels, I found it extremely frustrating that the "header" facet doesn't work for it like it does for most components. After searching, I learned from the forum that the facets to use are "headerCollapsed" and "headerExpanded". There's no mention of that in the documentation. Please update the documentation and examples.
--
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, 9 months
[JBoss JIRA] (RFPL-2080) Developer guide - resource mapping/optimization - small typos
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2080?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2080:
--------------------------------
Sprint: 4.3.0.CR1 Doc Corrections
> Developer guide - resource mapping/optimization - small typos
> -------------------------------------------------------------
>
> Key: RFPL-2080
> URL: https://issues.jboss.org/browse/RFPL-2080
> Project: RichFaces Planning
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.2.0.Final
> Environment: Developer guide
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Trivial
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> I have found these small typos in the _Developer guide_, for part dealing with _resource mapping/optimization_:
> _RESOURCE OPTIMIZATION_
> CURRENT: resources are not compressed in a development and during an unit-test to enable a client-side debugging
> MAYBE: resources are not compressed in a development *stage* and during *a unit-testing* to enable a client-side debugging
> CURRENT: resources are compressed in a production and during a system-test to minimize a network bandwidth
> MAYBE: resources are compressed in a production *stage* and during a *system-testing* to minimize a network bandwidth
> _RESOURCE MAPPING_
> CURRENT: This feature can help to solve of following cases:
> MAYBE: This feature can help to *solve following* cases:
> CURRENT: providing alternative versions of a resource
> MAYBE: providing alternative versions *of resources*
> CURRENT: moving resources to servers with static content
> MAYBE: moving resources to servers *serving* static content
> _RESOURCE MAPPING CONFIGURATION FILE_
> CURRENT: A following sample shows a JSF resource with name resourceLibrary:resourceName relocated to a resource anotherResourceLibrary:anotherResourceName:
> MAYBE: A following sample shows a JSF resource with *a* name resourceLibrary:resourceName relocated to a resource anotherResourceLibrary:anotherResourceName:
> CURRENT: It is possible to define additional resource mapping configuration files using a contextual parameter identifying class-path locations where files resides: org.richfaces.resourceMapping.mappingFile (a comma-separated list of class-path files).
> MAYBE: It is possible to define additional resource mapping configuration *files, by using* a contextual parameter identifying *the* class-path locations where files resides: org.richfaces.resourceMapping.mappingFile (a comma-separated list of *the* class-path files).
--
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, 9 months
[JBoss JIRA] (RFPL-2079) Component reference - rich:hotKey - small typos
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2079?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2079:
--------------------------------
Sprint: 4.3.0.CR1 Doc Corrections
> Component reference - rich:hotKey - small typos
> -----------------------------------------------
>
> Key: RFPL-2079
> URL: https://issues.jboss.org/browse/RFPL-2079
> Project: RichFaces Planning
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.2.0.Final
> Environment: Component reference
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Trivial
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> I have found these small typos for _rich:hotKey in Component Reference_, which should be IMHO fixed:
> CURRENT: attach it with selector attribute to all the elements defined using this selector. This attribute uses syntax for CSS rule selector defined by W3C consortium with some jQuery extensions.
> MAYBE: *attach it to the specific elements by defining selector attribute*. This attribute uses syntax *of the CSS selectors* defined by W3C consortium with some jQuery extensions. *(e.g. which one ?)*
> CURRENT: The key attribute defines the hot key itself which is processed by the component.
> MAYBE: The key attribute defines the hot key *itself, which* is processed by the component.
> CURRENT: The preventDefault attribute specifies whenever hot key binding should prevent default browser-specific actions to be taken (e.g. Ctrl+A hot key selecting all available text, Ctrl+B opening bookmarks bar, etc.).
> MAYBE: The preventDefault attribute specifies *whether the* hot key binding should prevent default browser-specific actions to be taken (e.g. Ctrl+A hot key selecting all available text, Ctrl+B opening bookmarks bar, etc.).
> CURRENT: keydown (default event) is fired when hot key sequence is initiated (keys are down)
> MAYBE: keydown (default event) is fired when *the* hot key sequence is initiated (*the* keys are down)
--
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, 9 months
[JBoss JIRA] (RFPL-2592) Example 9.7. Keyword-based switching in Component Referance Guide has wrong value @previous
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2592?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2592:
--------------------------------
Sprint: 4.3.0.CR1 Doc Corrections
> Example 9.7. Keyword-based switching in Component Referance Guide has wrong value @previous
> -------------------------------------------------------------------------------------------
>
> Key: RFPL-2592
> URL: https://issues.jboss.org/browse/RFPL-2592
> Project: RichFaces Planning
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.2.2.Final
> Reporter: Mark Bloomfield
> Priority: Minor
> Fix For: 4.3.0.CR1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> In the component referacne guide Example 9.7 the example states the value @previous as the keyword to use to switch to a previous panel. I believe it should be @prev as per the online example.
> The bug is in the text prior to the example and in the example itself.
> Please note I am new to RichFaces so perhaps it's wrong in the component? However I have tested with @prev and it works.
--
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, 9 months
[JBoss JIRA] (RFPL-2078) Component reference - a4j:push - small typos
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2078?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2078:
--------------------------------
Sprint: 4.3.0.CR1 Doc Corrections
> Component reference - a4j:push - small typos
> --------------------------------------------
>
> Key: RFPL-2078
> URL: https://issues.jboss.org/browse/RFPL-2078
> Project: RichFaces Planning
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.2.0.Final
> Environment: Component reference
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Trivial
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> I have found these typos and other things which should be IMHO corrected for the _a4j:push_ in _Component Reference_.
> CURRENT: When you are registering Push servlet in the Servlets 3.0 environments manually, the RichFaces will detect that servlet for Push is already registered and it avoids to initialize it again.
> However be sure to setup the Push servlet to support asynchronous requests - modify the servlet registration in the previous web.xml snippet as follows:
> MAYBE: When you *attempt to register* Push servlet *manually* in the Servlets 3.0 environments, the RichFaces will detect that servlet for Push is already registered*, and* it *avoids initializing* it again.
> *However, be sure* to setup the Push servlet to support asynchronous requests - modify the servlet registration *from* the previous web.xml snippet as follows:
> CURRENT: Sending a message using the TopicsContext involves creating a TopicKey instance (denominator of given message topic) and looking up the TopicsContext used for topic registration and message publishing.
> MAYBE: Sending a message using the TopicsContext*, which was used for registration of topic and message publishing,* involves creating a TopicKey instance (denominator of given message topic) and *look the TopicContext up*.
> CURRENT: Ensure the Create durable subscriber and Delete durable subscriber options are set to true for push functionality.
> MAYBE: Ensure the Create durable subscriber and *the* Delete durable subscriber options are set to true for *proper* push functionality.
> CURRENT: The RichFaces looks for the JMS Connection Factory on the JNDI context /ConnectionFactory by default
> MAYBE: The RichFaces looks for the JMS Connection Factory on the JNDI context /ConnectionFactory by *default.*
> CURRENT: The JMS message which should be propagated to Push needs to be created with method session.createObjectMessage(message);.
> MAYBE: The JMS message which should be propagated to Push needs to be created with *the* method session.createObjectMessage(message);.
> CURRENT: Receiving messages from JMS doesn't differ from receiving messages sent by the TopicsContext or using CDI events.
> MAYBE: Receiving messages from *a JMS queues* doesn't differ from *the* receiving messages sent by the TopicsContext or using a CDI events.
> CURRENT: This example demonstrates a simple use of the <a4j:push> causing an immediate update of page content.
> MAYBE: *The example above* demonstrates a simple use of the <a4j:push> causing an immediate update of *the* page content.
--
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, 9 months
[JBoss JIRA] (RFPL-2295) vdl documentation for a4j:outputPanel contains non-implemented layout="none"
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RFPL-2295?page=com.atlassian.jira.plugin.... ]
Lukáš Fryč reassigned RFPL-2295:
--------------------------------
Assignee: Lukáš Fryč
> vdl documentation for a4j:outputPanel contains non-implemented layout="none"
> ----------------------------------------------------------------------------
>
> Key: RFPL-2295
> URL: https://issues.jboss.org/browse/RFPL-2295
> Project: RichFaces Planning
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.2.2.Final
> Environment: http://docs.jboss.org/richfaces/latest_4_2_X/vdldoc/
> Reporter: Michal Petrov
> Assignee: Lukáš Fryč
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> {code:xml}
> <a4j:outputPanel ajaxRendered="true" id="moviePanel" layout="none" rendered="#{not empty movieBean.movie}">
> {code}
> layout="none" doesn't seem to be implemented but it is mentioned in vdldoc: http://docs.jboss.org/richfaces/latest_4_2_X/vdldoc/
> {code}
> javax.el.ELException: Cannot convert none of type class java.lang.String to class org.richfaces.component.OutputPanelLayout
> at org.apache.el.lang.ELSupport.coerceToEnum(ELSupport.java:182)
> at org.apache.el.lang.ELSupport.coerceToType(ELSupport.java:405)
> at org.apache.el.ExpressionFactoryImpl.coerceToType(ExpressionFactoryImpl.java:47)
> at org.jboss.weld.util.el.ForwardingExpressionFactory.coerceToType(ForwardingExpressionFactory.java:34)
> at com.sun.faces.facelets.tag.BeanPropertyTagRule$LiteralPropertyMetadata.applyMetadata(BeanPropertyTagRule.java:88)
> at com.sun.faces.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:81)
> at javax.faces.view.facelets.MetaTagHandler.setAttributes(MetaTagHandler.java:129)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.setAttributes(DelegatingMetaTagHandler.java:102)
> at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.setAttributes(BehaviorsAddingComponentHandlerWrapper.java:113)
> at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.doNewComponentActions(ComponentTagHandlerDelegateImpl.java:423)
> at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:170)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
> at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
> at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
> at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
> at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
> at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
> at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:107)
> at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:178)
> at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395)
> at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366)
> at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:112)
> at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
> at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
> at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:195)
> at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
> at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
> at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
> at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
> at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
> at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
> at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
> at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
> at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
> at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
> at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:86)
> at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:152)
> at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:774)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:100)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50)
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
> at java.lang.Thread.run(Thread.java:722)
> {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, 9 months