Issue (View Online)

Key: NXP-439
Issue Type: Sub-task Sub-task
Status: Resolved Resolved
Priority: Minor Minor
Resolution: Fixed
Assignee: Razvan Caraghin
Reporter: Thierry Delprat

Operations

View all
View comments
View history
Improve JSF / DocumentModel binding 
Updated: 26/01/07 09:45   Created: 29/12/06 18:58  

The following issue has been resolved as FIXED.

Author: Anahide Tchertchian
Date: 26/01/07 09:45
Comment:
done using adapters, maybe add taglibs that now how to use these adapters

Project: Nuxeo Enterprise Platform 5
Fix Versions: 5.0 Final

 Description   
The binding inside JSF should be more simple.

The ActionListeners should not contains any mapping / casting logic.
Typically, the mapping from FileUpload to nx:content should not be made at ActionListener level : this should be handled at URLResolverlevel (like Dates) or in a dedicated phase listener. The transformation logic should be registred using an extension point at web document declaration level : ie, each document can declare it's own mapping model.

The differents facets of the document (versions, relations, wf ...) should be directly accessible via the document model.
Instead of using separated Seam context variables (one for versioninfo, one for relations infos ...), all informations generated by the services should be bound to facets of the document model.
currentItem.getFacet(VERSON) => VersionInfo
currentItem.getFacet(RELATIONS) => RelationsInfo

Theses facets should be easily accesibled to the facelets using the custom url resolver : currentItem@@RelationInfo.linkedDocuments



This message was automatically generated by Atlassian JIRA Enterprise Edition, Version: 3.7.2-186 - Bug/feature request.
If you think it was sent incorrectly, contact one of this server's administrators.

_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to