[richfaces-planning-issues] [JBoss JIRA] Commented: (RFPL-183) Review RF 3.3.X/4.0 support for AS 5.2 with JSF 2.0 and the admin console

Alexander Smirnov (JIRA) jira-events at lists.jboss.org
Wed Oct 7 18:21:37 EDT 2009


    [ https://jira.jboss.org/jira/browse/RFPL-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12488886#action_12488886 ] 

Alexander Smirnov commented on RFPL-183:
----------------------------------------

After a few attempts, I got that example running on Jboss AS 5.2. I use JBAS 5.2.beta build from 09/27 there that example generates an empty page after any submit, just like https://jira.jboss.org/jira/browse/JBAS-7309 . Everything became ok after replacing Mojarra libraries to the latest code built from trunk, so it seems like temporary Mojarra problem.
I've checked next components:
a4j:commandButton
a4j:repeat
a4j:support

rich:column
rich:columnGroup
rich:datascroller
rich:dataTable
rich:tabPanel
rich:panel 


> Review RF 3.3.X/4.0 support for AS 5.2 with JSF 2.0 and the admin console
> -------------------------------------------------------------------------
>
>                 Key: RFPL-183
>                 URL: https://jira.jboss.org/jira/browse/RFPL-183
>             Project: RichFaces Planning
>          Issue Type: Task
>          Components: build, components
>         Environment: JBoss AS 5.2 with latest JSF 2.0 fix from stan build http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.x-sun16/804/
> RichFaces 3.3.2.GA and RichFaces 4.0
>            Reporter: Jay Balunas
>            Assignee: Jay Balunas
>            Priority: Critical
>             Fix For: 3.3.3.CR1, 4.0.0.ALPHA2
>
>
> The AS team is attempting to release AS 5.2 as an EE6 preview release with JSF 2.0.  The problem is that admin console user RichFaces and is attempting to use 3.3.X.
> The RichFaces team needs to investigate option for support - See minutes from team meeting - http://www.jboss.org/community/wiki/RichFaces40MeetingMinutes10-7-2009
> 1) Find a way to make 3.3.X support the component set that the admin console uses ( attached below )
> 2) Work with and prioritize the 4.0 component development to support the components 
> 2.1) This would mean that AS 5.2 ships as an ALPHA without the admin console

-- 
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

        


More information about the richfaces-planning-issues mailing list