January 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-3986) oncomplete documentation in richfaces_userguide.pdf wrong

by Michael Heinen (JIRA)

oncomplete documentation in richfaces_userguide.pdf wrong --------------------------------------------------------- Key: RF-3986 URL: https://jira.jboss.org/jira/browse/RF-3986 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.1.5 Reporter: Michael Heinen I assume there is a bug in the current richfaces-userguide.pdf, section 5.4.5. JavaScript Interactions: It says: "oncomplete" attribute allows to invoke the JavaScript code right after the Ajax Response is returned back and the DOM tree of the browser is updated. Richfaces registers the code for further invocation of XMLHTTP request object before an Ajax request is sent. This means the code will not be changed during processing of the request on the server if you use JSF EL value binding. Also, you cannot use "this'" inside the code, because it will not point the component where Ajax request was initiated. Is this description deprecated or is the implementation in richfaces 3.1.5 wrong? sample: actionListener="#{mybean.al}" oncomplete="#{!empty requestScope['someVar']?'doA();':'doB();'}" depending on what I do in my actionListener doA or doB is called. Therefore I think the documentation has to be updated. -- 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

15 years, 10 months

5
15
0 / 0

[JBoss JIRA] Created: (RF-4482) Typo in rich:contextMenu docs, actionParam with uppercase P

by Anders Biehl (JIRA)

Typo in rich:contextMenu docs, actionParam with uppercase P ----------------------------------------------------------- Key: RF-4482 URL: https://jira.jboss.org/jira/browse/RF-4482 Project: RichFaces Issue Type: Bug Components: doc Affects Versions: 3.2.2 Reporter: Anders Biehl Priority: Minor I think the example code on http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/... has typos. a4j:actionParam must be lowercase, right? -- 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

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (RF-5940) Figure does not reflect the value of the jointPoint attribute used in the example

by Karl Philipp (JIRA)

Figure does not reflect the value of the jointPoint attribute used in the example --------------------------------------------------------------------------------- Key: RF-5940 URL: https://jira.jboss.org/jira/browse/RF-5940 Project: RichFaces Issue Type: Bug Components: doc Affects Versions: 3.3.0 Environment: Web Reporter: Karl Philipp Priority: Minor http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/... Take a look at the figure named '6.101. Using the "direction" and "joinPoint" attributes' http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/... It shows a menu attached to the bottom-left point of the button element. But the example above, that is assigned to this figure, specifies the jointPoint attribute with value "tr" (top-right): <rich:dropDownMenu value="File" direction="bottom-right" jointPoint="tr"> ... -- 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

15 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (RF-4216) AjaxKeepAlive is not a component

by Nick Belaevski (JIRA)

AjaxKeepAlive is not a component -------------------------------- Key: RF-4216 URL: https://jira.jboss.org/jira/browse/RF-4216 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Reporter: Nick Belaevski Assignee: Svetlana mukhina Documentation: AjaxKeepAlive myKeepAlive = new AjaxKeepAlive() There's no AjaxKeepAlive component nor AjaxKeepAlive class and it cannot be created programmatically and there's no need for that. Request-scoped beans marked with org.ajax4jsf.model.KeepAlive annotation are kept-alive by framework internals. -- 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

15 years, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (RF-4080) Developer guide does not contain details for web.xml configuration to successfully integrate fileUpload component with myfaces framework.

by Andrei Markavtsov (JIRA)

Developer guide does not contain details for web.xml configuration to successfully integrate fileUpload component with myfaces framework. ----------------------------------------------------------------------------------------------------------------------------------------- Key: RF-4080 URL: https://jira.jboss.org/jira/browse/RF-4080 Project: RichFaces Issue Type: Bug Components: doc Affects Versions: 3.2.0 Environment: Myfaces RF Reporter: Andrei Markavtsov Assignee: Svetlana mukhina Fix For: 3.2.2 FileUpload guide should contain example of web.xml confiuration to fire component in myfaces framework. -- 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

15 years, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (RF-4215) Wrong binding type for tree listeners

by Nick Belaevski (JIRA)

Wrong binding type for tree listeners ------------------------------------- Key: RF-4215 URL: https://jira.jboss.org/jira/browse/RF-4215 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Reporter: Nick Belaevski Assignee: Svetlana mukhina Ex.: this was added into tree component by doc. team: <listener> <name>dropListener</name> <property existintag="true" exist="true" el="true" elonly="true"> <name>binding</name> <classname>javax.faces.component.UIComponent</classname> <description>The attribute takes a value-binding expression for a component property of a backing bean</description> </property> ... binding for listener elements is of type org.richfaces.*Listener, not of UIComponent -- 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

15 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (RF-5173) Styles are not rendered using RichFaces 3.2.2 with Spring WebFlow/Facelets

by Lou Parisi (JIRA)

Styles are not rendered using RichFaces 3.2.2 with Spring WebFlow/Facelets -------------------------------------------------------------------------- Key: RF-5173 URL: https://jira.jboss.org/jira/browse/RF-5173 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: Sun JSF 1.2 Spring Framework 2.5.5 Spring Webflow 2.0.3 Facelet 1.1.14 Tomcat 5.5.25 on Windows Reporter: Lou Parisi I have a Spring WebFlow project with Facelets on Tomcat 5.5.25. With RichFaces 3.2.1.GA everything works fine. When I change to RichFaces 3.2.2.SR1 none of the styles are rendered and the page is just text with links. I have a sample war file with a tabbed panel that I can reproduce the problem in my environment. -- 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

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-3600) Input number slider has wrong handle position inside modal panel.

by Sergey Halipov (JIRA)

Input number slider has wrong handle position inside modal panel. ----------------------------------------------------------------- Key: RF-3600 URL: http://jira.jboss.com/jira/browse/RF-3600 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.1 Environment: IE, FF, Opera Reporter: Sergey Halipov Priority: Minor Attachments: correctPosition.png, wrongPosition.png <h:form id="form" > <h:panelGroup id="test" > <rich:modalPanel id="mp" showWhenRendered="true" width="550"> <rich:inputNumberSlider id="slider" minValue="0" maxValue="100" value="50" barStyle="width: 500px;" /> <a4j:commandButton id="comm" reRender="test" value="Re-render" /> </rich:modalPanel> </h:panelGroup> </h:form> Small arrow should be places in the center of slider bar for this example. But really it is moved to the first slider position (see pictures for details). Under IE bug is reproducible immediately, under FF and Opera only after ajax re-rendering. -- 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

15 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-5118) Components names in dev project and in guides

by Svetlana mukhina (JIRA)

Components names in dev project and in guides ---------------------------------------------- Key: RF-5118 URL: https://jira.jboss.org/jira/browse/RF-5118 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.2 Reporter: Svetlana mukhina Assignee: Catherine Luts Priority: Minor Fix For: Future Make sure that components are named in guide the same way as they are in dev project, paid special attention to the case, e.g. if in TLD a component is datascroller then in guide it also should be detascroller not dataScroller -- 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

15 years, 10 months

2
11
0 / 0

[JBoss JIRA] Created: (RF-4597) AjaxStatus: style/styleClass attibutes are not applied on a4j:status

by Dmitry Svyatobatsko (JIRA)

AjaxStatus: style/styleClass attibutes are not applied on a4j:status -------------------------------------------------------------------- Key: RF-4597 URL: https://jira.jboss.org/jira/browse/RF-4597 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Reporter: Dmitry Svyatobatsko Assignee: Nick Belaevski Priority: Minor Fix For: 3.3.0 a) style/styleClass attributes are not applied on a4j:status component. They seem to be redundant (start/stop can be used instead) and probably should be removed b) startStyle attributes has wrong description -- 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

15 years, 10 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2009