<a4j:portlet> not needed anymore with JBossPortletBridge => tell it in the doc.
--------------------------------------------------------------------------------
Key: RF-3153
URL: http://jira.jboss.com/jira/browse/RF-3153
Project: RichFaces
Issue Type: Task
Components: doc
Affects Versions: 3.2.0
Environment: JBoss PortletBridge B2 / RichFaces 3.2.0 / JBoss Portal
Reporter: Antoine Herzog
Priority: Minor
Fix For: 3.2.1
In another jira, Wesley says that :
"The configurations used in this issue are old - like a4j:portlet is not needed. You should now be using JBoss Portlet Bridge (http://www.jboss.org/portletbridge/). the Beta2 demo application proves that this is working."
JIRA is : http://jira.jboss.com/jira/browse/PBR-20
(at the end of the comments)
if the a4j:portlet is not needed :
- not needed only with the JBoss PortletBridge, but needed with other bridges ?
- not needed never ?
It would be great to have something explained about that in the documentation of RichFaces.
Or a "Deprecated" put on it.
And in the doc or wiki of JBoss PortalBridge.
Now, the component is described, nothing to prevent using it...
--
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
Filtering: provide rich classes to generated via filterBy input
----------------------------------------------------------------
Key: RF-3210
URL: http://jira.jboss.com/jira/browse/RF-3210
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.1
Reporter: Ilya Shaikovsky
Assigned To: Nick Belaevski
Fix For: 3.2.1
--
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
for attribute in datascroller not handled when using datascroller in custom tags
--------------------------------------------------------------------------------
Key: RF-2923
URL: http://jira.jboss.com/jira/browse/RF-2923
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Alan Stewart
Have writtem custom JSF tags that incorporate the rich:datascroller.
We pass in the id of the rich:dataTable in our custom tag and the datascroller has working using this in versions up until 3.1.4.SR1. Changed to 3.2.0.GA and now without any other code changes, I get an error:
could not find dataTable for datascroller j_id171. When we hard-code the id of the dataTable in the "for" attribute of the rich:datascoller, it all works OK.
--
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
dataOrderedList: columnClasses doesn't work
-------------------------------------------
Key: RF-3138
URL: http://jira.jboss.com/jira/browse/RF-3138
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5
Environment: 3.1.5.CR2
Reporter: Tsikhon Kuprevich
Assigned To: Nick Belaevski
columnClasses: css classes aren't encoded in the html rendered.
--
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
Validity of all xml files
-------------------------
Key: RF-2917
URL: http://jira.jboss.com/jira/browse/RF-2917
Project: RichFaces
Issue Type: Task
Components: doc
Affects Versions: 3.2.1
Reporter: Gleb Galkin
Assigned To: Gleb Galkin
Fix For: 3.2.1
All xml files should be validated according to DTD specified in master.xml.
Just open master.xml in Oxygen and press Ctrl+Shift+V or go "Document->Validate->Validate Document"
--
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
Typo in section 5.4.1 in the Reference Manual
---------------------------------------------
Key: RF-2908
URL: http://jira.jboss.com/jira/browse/RF-2908
Project: RichFaces
Issue Type: Task
Components: doc
Affects Versions: 3.2.0
Reporter: Joao Paulo Viragine
In section 5.4.1 of the Reference Manual (http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone...) the phrase: "Most common problem with using reRender is pointing it to the component that has a "reRender" attribute"
Should be: "Most common problem with using reRender is pointing it to the component that has a "rendered" attribute"
Substitute: "reRender" attribute by: "rendered" attribute
--
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
Rearrange skin parameters table
-------------------------------
Key: RF-2775
URL: http://jira.jboss.com/jira/browse/RF-2775
Project: RichFaces
Issue Type: Task
Affects Versions: 3.2.0
Reporter: Nick Belaevski
Assigned To: Svetlana mukhina
Fix For: 3.2.0
Swap skin parameters table - CSS styles should be to the left, and corresponding skin parametrs to the right
--
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
demosite: create example of selection attribute usage.
------------------------------------------------------
Key: RF-1422
URL: http://jira.jboss.com/jira/browse/RF-1422
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.0
Reporter: Ilya Shaikovsky
Assigned To: Ilya Shaikovsky
Fix For: 3.2.0
--
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