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

[Brian Leathem (JIRA)]

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

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

Fortunately {{RichFaces.BaseComponent}} itself doesn't contain any jsf.js integration.  De-coupling a component for its JSF backend then should simply involve replacing direct {{RichFaces.ajax}} calls with an event mechanism.

On a related note, much of the {{RichFaces.BaseComponent}} merely wraps some specific jQuery functionality.  The client-side codebase could conceivably be simplified by removing the unused and redundant abstractions.

> 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.3#6260)