February 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11987) rich:extendedDataTable column drag&drop dependant on column id

by J S (JIRA)

J S created RF-11987: ------------------------ Summary: rich:extendedDataTable column drag&drop dependant on column id Key: RF-11987 URL: https://issues.jboss.org/browse/RF-11987 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-drag/drop Affects Versions: 3.3.2.CR1 Reporter: J S I have the following table <rich:extendedDataTable value="#{taskDataModel}" id="tasksTable0"> <rich:column label="1" id="id_column1"> <f:facet name="header"> <h:outputText id="htaskId_text1" value="1" /> </f:facet> <h:outputText id="taskId1" value="1"/> </rich:column> <rich:column label="2" id="id_column2"> <f:facet name="header"> <h:outputText id="htaskId_text2" value="2" /> </f:facet> <h:outputText id="taskId2" value="2"/> </rich:column> </rich:extendedDataTable> And it works fine, however if I change the columns id from "id_column1" and "id_column2" to "id_column" and "name_column" I'm not able to drag&drop columns anymore. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-11054) Dynamically created tabs within tabPanel causes NPE in getActiveItem()

by Ján Jamrich (JIRA)

Dynamically created tabs within tabPanel causes NPE in getActiveItem() ---------------------------------------------------------------------- Key: RF-11054 URL: https://issues.jboss.org/browse/RF-11054 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: RichFaces 4.1.0-SNAPSHOT r.22526 Metamer r.22526 Mojarra 2.0.4-b09 Apache Tomcat 7.0.12 Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux Chrome 12.0.718.0 @ Linux i686 Reporter: Ján Jamrich When set switchType on TabPanel to "server" (notice that with "client" everything works correctly, with "ajax" tab switch not work as well as with "null"), all dynamically created tabs causes NPE on tab switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

8
20
0 / 0

[JBoss JIRA] (RF-11764) resourceMapping turned on?

by Jean ANDRE (Created) (JIRA)

resourceMapping turned on? -------------------------- Key: RF-11764 URL: https://issues.jboss.org/browse/RF-11764 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.CR1 Reporter: Jean ANDRE See also RF-11694 and RF-11757 -- 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, 2 months

12
38
0 / 0

[JBoss JIRA] (RF-11959) Support custom skins with resource packaging

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-11959: ------------------------------- Summary: Support custom skins with resource packaging Key: RF-11959 URL: https://issues.jboss.org/browse/RF-11959 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: skinning Affects Versions: 4.2.0.CR1 Reporter: Lukáš Fryč Fix For: 4.3-Tracking -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] (RF-11888) Resource Servlet can't handle query string appended to resource url

by Brendan Healey (JIRA)

Brendan Healey created RF-11888: ----------------------------------- Summary: Resource Servlet can't handle query string appended to resource url Key: RF-11888 URL: https://issues.jboss.org/browse/RF-11888 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: resource handling Affects Versions: 4.1.0.Final Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser - Reporter: Brendan Healey A custom resource handler (http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature) can be used to append a version string (i.e. ?v=23) to a resource url to force a browser to refresh a resource rather than use any cached version. This is useful as a last resort strategy, perhaps after a major redeployment, and also in the event that there are other problems setting useful ETag and Last-Modified http response headers. At present any appending of a version string causes a 404 response status, for example: Request URL: https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource... Removing the url parameter makes it work ok. As you can see I have resourceMapping enabled. -- 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, 2 months

3
18
0 / 0

[JBoss JIRA] (RF-11998) Component reference - a4j:push - small typos

by Juraj Huska (JIRA)

Juraj Huska created RF-11998: -------------------------------- Summary: Component reference - a4j:push - small typos Key: RF-11998 URL: https://issues.jboss.org/browse/RF-11998 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-push/poll, 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-10814) Facelet taglib: add facets to component extension tag

by Anton Belevich (JIRA)

Facelet taglib: add facets to component extension tag ----------------------------------------------------- Key: RF-10814 URL: https://issues.jboss.org/browse/RF-10814 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: cdk Reporter: Anton Belevich Fix For: 4.1.0.Milestone1 Need to add information about component facet to facet.taglib we should get something like this: <component-extension> <cdk:extension> <facets> <facet>header</facet> <facet>footer</facet> </facets> </cdk:extension> </component-extension> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
9
0 / 0

[JBoss JIRA] Created: (RF-11017) rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4

by Rene O (JIRA)

rich:extendedDataTable: Problems with resizing and ordering of columns with Firefox 4 ------------------------------------------------------------------------------------- Key: RF-11017 URL: https://issues.jboss.org/browse/RF-11017 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone1 Environment: Tomcat6 and 7, Java 6, MyFaces 2.1.0-SNAPSHOT (28.05.2011), RichFaces 4.1.0-SNAPSHOT (28.05.2011) Reporter: Rene O To reproduce the two issues, i have append a testcase: Issue 1 (ordering): 1. call http://localhost:8080/jsf2testcase/tableTest.jsf 2. try to change the order of the columns (e.g. A,B,C -> B,A,C) 3. after that, the scrollbar of the table disappears Note, that this issue appears with Firefox 4.0.1, but not with IE8 Issue 2 (resizing): 1. call http://localhost:8080/jsf2testcase/tableTestB.jsf 2. click button to show table B 3. try to resize the column width of table B 4. resizing doesn't work in table B, but if you try to resize the column width of table A, it will work. So it must be a bug. Note, that this issue appears with Firefox 4.0.1, but not with IE8 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

13
21
0 / 0

[JBoss JIRA] (RF-11929) showcase - a4j:actionListener - move commandButtons from panelGrid to make it look better

by Juraj Huska (JIRA)

Juraj Huska created RF-11929: -------------------------------- Summary: showcase - a4j:actionListener - move commandButtons from panelGrid to make it look better Key: RF-11929 URL: https://issues.jboss.org/browse/RF-11929 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-a4j-core, showcase Affects Versions: 4.2.0.CR1 Environment: all containers all browsers Reporter: Juraj Huska Priority: Trivial In demo for a4j:actionListener there are commandButtons included in the panelGrid together with panel which they generate. Invoking listener by type(middle command button) causes that the rendered panel is enlarged, and since the buttons are in the same panelGrid they are moved too, which looks weird. IMHO their should be moved from that panelGrid to be independent on the width of generated message. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] (RF-11930) showcase - a4j:actionListener - typo in demo description

by Juraj Huska (JIRA)

Juraj Huska created RF-11930: -------------------------------- Summary: showcase - a4j:actionListener - typo in demo description Key: RF-11930 URL: https://issues.jboss.org/browse/RF-11930 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, showcase Affects Versions: 4.2.0.CR1 Environment: all containers all browsers Reporter: Juraj Huska Priority: Minor In the demo for a4j:actionListener there is a typo in demo description. It is in the description to second way of attaching of actionListener. ??2. By listerner class, using the type attribute.?? -- 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, 3 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2012