February 2012 - richfaces-planning-issues

[JBoss JIRA] (RFPL-2064) Showcase tests on Android: Updarte testng groups

by Jan Papousek (JIRA)

Jan Papousek created RFPL-2064: ---------------------------------- Summary: Showcase tests on Android: Updarte testng groups Key: RFPL-2064 URL: https://issues.jboss.org/browse/RFPL-2064 Project: RichFaces Planning Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jan Papousek Assignee: Jan Papousek Fix For: 4.Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (RFPL-2081) Component Reference - consider too big spaces between words

by Juraj Huska (JIRA)

Juraj Huska created RFPL-2081: --------------------------------- Summary: Component Reference - consider too big spaces between words Key: RFPL-2081 URL: https://issues.jboss.org/browse/RFPL-2081 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 Huska Priority: Trivial There are in some parts of the Component Reference paragraphs, which have too big spaces between words(please see the screenshot). It is caused probably by block text structure, can be fixed by moving some words from the line which is above corrupted line by dividing the word, or to use other text alignment than block. Just to note that there is not many places where this occurs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (RFPL-2063) Showcase tests on Android: Update version of JBoss AS to use version defined in parent pom.xml

by Jan Papousek (JIRA)

Jan Papousek created RFPL-2063: ---------------------------------- Summary: Showcase tests on Android: Update version of JBoss AS to use version defined in parent pom.xml Key: RFPL-2063 URL: https://issues.jboss.org/browse/RFPL-2063 Project: RichFaces Planning Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jan Papousek Fix For: 4.Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
4
0 / 0

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

by Juraj Huska (JIRA)

Juraj Huska created RFPL-2080: --------------------------------- Summary: 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 Huska Priority: Trivial 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

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

by Juraj Huska (JIRA)

Juraj Huska created RFPL-2079: --------------------------------- Summary: 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 Huska Priority: Trivial 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

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

by Juraj Huska (JIRA)

[ https://issues.jboss.org/browse/RFPL-2078?page=com.atlassian.jira.plugin.... ] Juraj Huska moved RF-11998 to RFPL-2078: ---------------------------------------- Project: RichFaces Planning (was: RichFaces) Key: RFPL-2078 (was: RF-11998) Workflow: jira (was: GIT Pull Request workflow ) Affects Version/s: 4.2.0.Final (was: 4.2.0.Final) Component/s: doc (was: doc) (was: component-push/poll) > 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 Huska > Priority: Trivial > > 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1954) Umbrella for new component rich:hotkey

by Lukáš Fryč (Created) (JIRA)

Umbrella for new component rich:hotkey -------------------------------------- Key: RFPL-1954 URL: https://issues.jboss.org/browse/RFPL-1954 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: administration Affects Versions: 4.1.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] (RFPL-2030) Update dev guide and component ref with new css class names for the notify component

by Brian Leathem (JIRA)

Brian Leathem created RFPL-2030: ----------------------------------- Summary: Update dev guide and component ref with new css class names for the notify component Key: RFPL-2030 URL: https://issues.jboss.org/browse/RFPL-2030 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: doc Reporter: Brian Leathem Assignee: Lukáš Fryč Fix For: 4.2.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (RFPL-2077) Check versions in Dev Guide: Project libraries and dependencies section

by Lukáš Fryč (JIRA)

Lukáš Fryč created RFPL-2077: -------------------------------- Summary: Check versions in Dev Guide: Project libraries and dependencies section Key: RFPL-2077 URL: https://issues.jboss.org/browse/RFPL-2077 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.2.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (RFPL-1980) Improve a4j:push Docs for consistency, simplicity and readability

by Lukáš Fryč (JIRA)

Lukáš Fryč created RFPL-1980: -------------------------------- Summary: Improve a4j:push Docs for consistency, simplicity and readability Key: RFPL-1980 URL: https://issues.jboss.org/browse/RFPL-1980 Project: RichFaces Planning Issue Type: Enhancement Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.1.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Critical Fix For: 4.2.0.CR1 We have discussed on the team meeting that current docs are insufficient to guide new users. Following aspects needs to be considered when rewriting current docs: * samples' simplicity * readability and fluency * overall simplicity After rewriting, docs needs to be peer-reviewed / proof-read. [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues February 2012