July 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-4017) Error with handling static resources under WebSphere

by Thierry Robin (JIRA)

Error with handling static resources under WebSphere ---------------------------------------------------- Key: RF-4017 URL: https://jira.jboss.org/jira/browse/RF-4017 Project: RichFaces Issue Type: Patch Environment: websphere 6.1 Reporter: Thierry Robin ajax4jsf filter for static resources doesn't flush before sending response and a bug (?) with websphere generate an error message 404 for some resources. the same issue is describe here : https://issues.apache.org/struts/browse/WW-1526 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-4055) Panelbar: error in demosite under NEKO parser

by Nick Belaevski (JIRA)

Panelbar: error in demosite under NEKO parser --------------------------------------------- Key: RF-4055 URL: https://jira.jboss.org/jira/browse/RF-4055 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Reporter: Nick Belaevski Assignee: Anton Belevich Fix For: 3.2.2 this.content.firstChild.style is undefined showContent()()panelbar.js.jsf (line 235) showSlide()(Object index=0 slidePanel=Object)panelbar.js.jsf (line 103) initialize()("j_id109", Object items=[13])panelbar.js.jsf (line 51) klass()a4j_3_2_...cript.jsf (line 50) (?)()actionpa...tab=usage (line 1457) [Break on this error] this.content.firstChild.style.height=""; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-2947) Could not get Input stream for resource error under glassfish

by Ilya Shaikovsky (JIRA)

Could not get Input stream for resource error under glassfish ------------------------------------------------------------- Key: RF-2947 URL: http://jira.jboss.com/jira/browse/RF-2947 Project: RichFaces Issue Type: Sub-task Affects Versions: 3.2.0 Reporter: Ilya Shaikovsky Assigned To: Vladislav Baranov Fix For: 3.2.0SP1 check please this also under glassfish. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140979#4140979 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-4042) Validators: add "message" attribute for ajaxValidator & beanValidator

by Nick Belaevski (JIRA)

Validators: add "message" attribute for ajaxValidator & beanValidator --------------------------------------------------------------------- Key: RF-4042 URL: https://jira.jboss.org/jira/browse/RF-4042 Project: RichFaces Issue Type: Feature Request Reporter: Nick Belaevski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (RF-3758) add a4j:supportAll to mirror Seam's s:validateAll

by Dan Allen (JIRA)

add a4j:supportAll to mirror Seam's s:validateAll ------------------------------------------------- Key: RF-3758 URL: http://jira.jboss.com/jira/browse/RF-3758 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.2.1 Reporter: Dan Allen Priority: Minor Fix For: 3.2.2 To save the developer from having to add the <s:validate> tag to every input component, Seam introduced the <s:validateAll> tag which walks its descendents and applies the Seam model validator to the input components. The same technique could be added to Ajax4jsf to avoid the need of having to add the <a4j:support> tag to every input. Often times you see the following markup: <h:panelGroup id="fieldNameGroup"> <h:inputText id="fieldName" value="#{model.fieldName"> <a4j:support event="onblur" ajaxSingle="true" bypassUpdates="true" reRender="fieldNameGroup"/> </h:inputText> <h:message for="fieldName"/> </h:panelGroup> It sure would be nice to be able to simplify this to the following: <h:panelGroup id="fieldNameGroup"> <a4j:supportAll event="onblur" ajaxSingle="true" bypassUpdates="true" reRender="fieldNameGroup"> <h:inputText id="fieldName" value="#{model.fieldName}"/> </a4j:supportAll> <h:message for="fieldName"/> </h:panelGroup> At first, you may think to yourself what the difference is. Well, a Facelet template can accomodate the second example to eliminate the need to specify the <a4j:support> tag. The first example cannot since there is no way to add a child element to a component passed into a template. So you could reduce this to: <s:decorate id="fieldNameDecorate" template="layout/edit.xhtml"> <ui:param name="reRender" value="fieldNameDecorate"/> <h:inputText id="fieldName" value="#{model.fieldName}"/> </s:decorate> We could even modify Seam to make the id of the decorate component available to the template so that the reRender parameter is not necessary. The template would look like the second example above, except that the input component would be replaced with <ui:insert/> and the value of reRender would be set to #{reRender}. The other benefit, of course, is that it is easy to turn on and off Ajax4jsf. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (RF-3946) contextMenu: if parent component doesn't have manually defined id contextMenu won't appear

by Tatyana Romanovich (JIRA)

contextMenu: if parent component doesn't have manually defined id contextMenu won't appear ------------------------------------------------------------------------------------------ Key: RF-3946 URL: https://jira.jboss.org/jira/browse/RF-3946 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: jsp test application Tomcat 6 all browsers 3.2.2.BETA1 Reporter: Tatyana Romanovich Assignee: Nick Belaevski 1. Go to the jsp test application 2. Select contextMenu component 3. Set event="onclick" 4. Try to call context menu for firs tested panel (panel with contextMenu(DEFAULT) testing events) Result: contextMenu doesn't appear Another Scenario: 1. create tested application with two examples for context menu: firs example: parent component has id, second: parent component doesn't have id: <h:outputText id="text2" value="Some text with context menu2"> <rich:contextMenu> <rich:menuItem value="a"> <f:param name="cmdParam" value="a" /> </rich:menuItem> </rich:contextMenu> </h:outputText> <h:outputText value="Some text with context menu3"> <rich:contextMenu> <rich:menuItem value="b"> <f:param name="cmdParam" value="b" /> </rich:menuItem> </rich:contextMenu> </h:outputText> 2. Run application on the server 3. Try to call context menu for each example result: context menu doesn't appear for second example (where parent component doesn't have id) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (RF-3847) Error using custom components inside scrollableDataTable

by Ilya Musihin (JIRA)

Error using custom components inside scrollableDataTable -------------------------------------------------------- Key: RF-3847 URL: http://jira.jboss.com/jira/browse/RF-3847 Project: RichFaces Issue Type: Feature Request Reporter: Ilya Musihin We are developing custom JSF components and have found the following problem when placing our components inside of <rich:scrollableDataTable> component. Everything worked fine before we added the "col" tag as part of our component. Now if we use our component inside of <rich:scrollableDataTable> , we get the JavaScript error "columns[j] has no properties" appear. Our investigation has shown that this error is caused by the specifics of implementation of RichFaces' scrollable-date-table.js.jsf JavaScript file that uses function getElementsByTagName("col") in line 149: cols=this.templNormal.getElement().getElementsByTagName("col");for(i=0;i<cols.length;i++){columns[j].bodyCol=$(cols[i]);j++;} This piece of code works correctly unless a component inside of ScrollableDataTable component renders its own "col" tags. So the problem of interoperability of such components with ScrollableDataTable would be solved if the mentioned code would just retrieve ScrollableDataTable's own "col" tags without searching the inner parts of sub-components. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (RF-3141) dataOrderedList: headerClass doesn't work

by Tsikhon Kuprevich (JIRA)

dataOrderedList: headerClass doesn't work ----------------------------------------- Key: RF-3141 URL: http://jira.jboss.com/jira/browse/RF-3141 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.5 Environment: 3.1.5.CR2 Reporter: Tsikhon Kuprevich Assigned To: Nick Belaevski dataOrderedList: headerClass doesn't work -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
15
0 / 0

[JBoss JIRA] Created: (RF-3047) Nightly builds arrangement

by Svetlana mukhina (JIRA)

Nightly builds arrangement --------------------------- Key: RF-3047 URL: http://jira.jboss.com/jira/browse/RF-3047 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.0 Reporter: Svetlana mukhina Assigned To: Svetlana mukhina Fix For: 3.1.5, 3.2.1 it's necessary that doc hightly build where placed somewhere online not in snapshots but as plain PDF or Html files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

1
6
0 / 0

[JBoss JIRA] Created: (RF-4069) URLs of resources generated by RF

by Svetlana mukhina (JIRA)

URLs of resources generated by RF --------------------------------- Key: RF-4069 URL: https://jira.jboss.org/jira/browse/RF-4069 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.1 Reporter: Svetlana mukhina Assignee: Catherine Luts Fix For: 3.2.2 Add note box in guide with the info in the linked task -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2008