[richfaces-issues] [JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend

Brian Leathem (JIRA) issues at jboss.org
Wed Jun 11 17:02:37 EDT 2014


    [ https://issues.jboss.org/browse/RF-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975475#comment-12975475 ] 

Brian Leathem commented on RF-13661:
------------------------------------

I created a branch [RF-13661-independent-js|https://github.com/richfaces/richfaces/tree/RF-13661-independent-js] where I added a examples/standalone-js example that can be use to create standalone html pages for various RF components.  The jsf pages are stored in the {{jsf}} webapp folder, and the corresponding standalone html page is stored in the {{html}} folder.  

Note: the standalone html page is created by deploying the webapp, and viewing a component page in a browser.  The html source of the component page is saved as an html file.  Path changes are made to the html file to use the js resources of the components directly from the source tree.

----

Merging of this branch is pending discussion at the upcoming f2f meeting.

> De-couple the RichFaces.BaseComponent implementation from its JSF backend
> -------------------------------------------------------------------------
>
>                 Key: RF-13661
>                 URL: https://issues.jboss.org/browse/RF-13661
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Leathem
>            Assignee: Brian Leathem
>             Fix For: 4.5-Tracking
>
>
> Investigate whether we can de-couple a {{RichFaces.BaseComponent}} based component from the JSF back-end.  The ExtendedDataTable implementation would be a good candidate for this PoC.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the richfaces-issues mailing list