January 2013 - richfaces-planning-issues

[JBoss JIRA] (RFPL-1962) Component-Reference for rich:jQuery - Defining a selector section is untrue

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RFPL-1962?page=com.atlassian.jira.plugin.... ] Lukáš Fryč resolved RFPL-1962. ------------------------------ Fix Version/s: 4.3.0.CR1 Resolution: Done > Component-Reference for rich:jQuery - Defining a selector section is untrue > --------------------------------------------------------------------------- > > Key: RFPL-1962 > URL: https://issues.jboss.org/browse/RFPL-1962 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.1.0.Final > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Documentation [1] says: > {quote} > The selector attribute can refer to the id identifier of any JSF component or client. > {quote} > This is untrue, the real algorithm [2] is trying to expand each CSS ID selector (starting with {{#}}) from {{componentId}} to {{clientId}} (e.g. {{#component}} becomes {{#form\:component}}). > [1] http://docs.jboss.org/richfaces/4.1.X/4.1.0.Final/Component_Reference/en-... > [2] https://github.com/richfaces/components/blob/develop/common/ui/src/main/j... -- 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2080) Developer guide - resource mapping/optimization - small typos

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RFPL-2080?page=com.atlassian.jira.plugin.... ] Lukáš Fryč resolved RFPL-2080. ------------------------------ Fix Version/s: 4.3.0.CR1 Resolution: Done > 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 > Fix For: 4.3.0.CR1 > > 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2583) Metamer: rewrite DnD tests using webDriver

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-2583?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated RFPL-2583: -------------------------------- Due Date: 11/Jan/13 > Metamer: rewrite DnD tests using webDriver > ------------------------------------------ > > Key: RFPL-2583 > URL: https://issues.jboss.org/browse/RFPL-2583 > Project: RichFaces Planning > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ján Jamrich > Assignee: Ján Jamrich > > Since DnD impl has changed tests start failing and fix them would require comparable resources than rewrite them completely using webDriver. -- 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2079) Component reference - rich:hotKey - small typos

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RFPL-2079?page=com.atlassian.jira.plugin.... ] Lukáš Fryč resolved RFPL-2079. ------------------------------ Fix Version/s: 4.3.0.CR1 Resolution: Done > 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 > Fix For: 4.3.0.CR1 > > 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2078) Component reference - a4j:push - small typos

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RFPL-2078?page=com.atlassian.jira.plugin.... ] Lukáš Fryč resolved RFPL-2078. ------------------------------ Fix Version/s: 4.3.0.CR1 Resolution: Done > 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 > Fix For: 4.3.0.CR1 > > 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2637) Document automatic Push topic creation

by Lukáš Fryč (JIRA)

Lukáš Fryč created RFPL-2637: -------------------------------- Summary: Document automatic Push topic creation Key: RFPL-2637 URL: https://issues.jboss.org/browse/RFPL-2637 Project: RichFaces Planning Issue Type: Enhancement Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.2.3.Final Reporter: Lukáš Fryč Push documentation currently describes the way of creating topics manually. But in scope of RF 4.2 we have introduced automatic topic creation. The documentation should be re-work to prefer automatic topic creation. -- 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2636) Metamer: filtering demo for rich:autocomplete doesn't work

by Jan Papousek (JIRA)

Jan Papousek created RFPL-2636: ---------------------------------- Summary: Metamer: filtering demo for rich:autocomplete doesn't work Key: RFPL-2636 URL: https://issues.jboss.org/browse/RFPL-2636 Project: RichFaces Planning Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.CR1 Reporter: Jan Papousek -- 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2625) Closeout and resolve QE issues in RichFaces "RFPL" jira project for this release

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-2625?page=com.atlassian.jira.plugin.... ] Pavol Pitonak resolved RFPL-2625. --------------------------------- Resolution: Done > Closeout and resolve QE issues in RichFaces "RFPL" jira project for this release > -------------------------------------------------------------------------------- > > Key: RFPL-2625 > URL: https://issues.jboss.org/browse/RFPL-2625 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Assignee: Pavol Pitonak > Fix For: 4.3.0.CR1 > > -- 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2508) Configure fundamental tests in Jenkins

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-2508?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on RFPL-2508: ------------------------------------- There is a Jenkins job [1] but it cannot be set as default because of unstable tests. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RF-4.0/job/richface... > Configure fundamental tests in Jenkins > -------------------------------------- > > Key: RFPL-2508 > URL: https://issues.jboss.org/browse/RFPL-2508 > Project: RichFaces Planning > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: QE > Reporter: Lukáš Fryč > Assignee: Pavol Pitonak > Fix For: 5.0.0.M1 > > > Fundamental tests (core/component integration tests using Warp/Graphene) needs to be configured to run in continuous integration. -- 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

1
0
0 / 0

[JBoss JIRA] (RFPL-2508) Configure fundamental tests in Jenkins

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-2508?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated RFPL-2508: -------------------------------- Fix Version/s: 5.0.0.M1 (was: 4.3.0.CR1) > Configure fundamental tests in Jenkins > -------------------------------------- > > Key: RFPL-2508 > URL: https://issues.jboss.org/browse/RFPL-2508 > Project: RichFaces Planning > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: QE > Reporter: Lukáš Fryč > Assignee: Pavol Pitonak > Fix For: 5.0.0.M1 > > > Fundamental tests (core/component integration tests using Warp/Graphene) needs to be configured to run in continuous integration. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues January 2013