[JIRA] Updated: (NXP-6681) File system level mapping

2011-12-21 Thread Florent Guillaume (JIRA NUXEO)

 [ 
https://jira.nuxeo.com/browse/NXP-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Florent Guillaume updated NXP-6681:
---

Description: 
Mapping a Nuxeo repository to a filesystem is not an easy job because the 
models do not match correctly:
 - name vs title+filename+name
 - file+folder vs folderish doc + multiple attachements

Most existing filesystem mapping protocol implementations in Nuxeo have tried 
to solve this issue: WebDav, WSS and CMIS.

There is no ideal solution and we will have to add some constraints on top of 
the Nuxeo model.

Rather that continuing with several mapping logic, it's time to build a generic 
module that will handle all the work:
 - Nuxeo Document - Filesystem resource
 - File System resource - Nuxeo Document (including what is done via 
FileManager)
 - Listeners to enforce the limitations of the FS model

This new module should be integrated in WebDav, WSS and CMIS.


  was:
We know for quite a long time than mapping Nuxeo repository to a file system is 
not an easy job because the model do not match correctly :

 - name vs title + filename + name

 - file+folder vs folderish doc + multiple attachements

Most existing file-system mapping protocol implementations in Nuxeo have tried 
to solve this issue : WebDav, WSS and CMIS.

There is no ideal solution and we will have to add some constraints on the 
Nuxeo model.

Rather that continuing with several mapping logic, it's time to build a generic 
module that will handle all the work :

 - Nuxeo Document = File System resource

 - File System resource = Nuxeo Document (including what is done via 
FileManager)

 - Listeners to enforce the limitations of the FS model

This new module should be integrated in WebDav, WSS and CMIS.
WebDav and CMIS should be based on the newly contributed version from 
Gagnavarslan that allows FileSystem level mounting via WSS.



 File system level mapping
 -

 Key: NXP-6681
 URL: https://jira.nuxeo.com/browse/NXP-6681
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Desktop Integration, WSS integration
Reporter: Thierry Delprat
Assignee: Florent Guillaume
 Fix For: 6.0


 Mapping a Nuxeo repository to a filesystem is not an easy job because the 
 models do not match correctly:
  - name vs title+filename+name
  - file+folder vs folderish doc + multiple attachements
 Most existing filesystem mapping protocol implementations in Nuxeo have tried 
 to solve this issue: WebDav, WSS and CMIS.
 There is no ideal solution and we will have to add some constraints on top of 
 the Nuxeo model.
 Rather that continuing with several mapping logic, it's time to build a 
 generic module that will handle all the work:
  - Nuxeo Document - Filesystem resource
  - File System resource - Nuxeo Document (including what is done via 
 FileManager)
  - Listeners to enforce the limitations of the FS model
 This new module should be integrated in WebDav, WSS and CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Updated: (NXP-6681) File system level mapping

2011-12-14 Thread Thierry Martins (JIRA NUXEO)

 [ 
https://jira.nuxeo.com/browse/NXP-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thierry Martins updated NXP-6681:
-

Tags: 541-hf15

Small part backported in 5.4.1 to enable renaming while editing a document

 File system level mapping
 -

 Key: NXP-6681
 URL: https://jira.nuxeo.com/browse/NXP-6681
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Desktop Integration, WSS integration
Reporter: Thierry Delprat
Assignee: Florent Guillaume
 Fix For: 6.0


 We know for quite a long time than mapping Nuxeo repository to a file system 
 is not an easy job because the model do not match correctly :
  - name vs title + filename + name
  - file+folder vs folderish doc + multiple attachements
 Most existing file-system mapping protocol implementations in Nuxeo have 
 tried to solve this issue : WebDav, WSS and CMIS.
 There is no ideal solution and we will have to add some constraints on the 
 Nuxeo model.
 Rather that continuing with several mapping logic, it's time to build a 
 generic module that will handle all the work :
  - Nuxeo Document = File System resource
  - File System resource = Nuxeo Document (including what is done via 
 FileManager)
  - Listeners to enforce the limitations of the FS model
 This new module should be integrated in WebDav, WSS and CMIS.
 WebDav and CMIS should be based on the newly contributed version from 
 Gagnavarslan that allows FileSystem level mounting via WSS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Updated: (NXP-6681) File system level mapping

2011-11-21 Thread Florent Guillaume (JIRA NUXEO)

 [ 
https://jira.nuxeo.com/browse/NXP-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Florent Guillaume updated NXP-6681:
---

Issue Type: Improvement  (was: User story)

 File system level mapping
 -

 Key: NXP-6681
 URL: https://jira.nuxeo.com/browse/NXP-6681
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Desktop Integration, WSS integration
Reporter: Thierry Delprat
Assignee: Florent Guillaume
 Fix For: 5.5


 We know for quite a long time than mapping Nuxeo repository to a file system 
 is not an easy job because the model do not match correctly :
  - name vs title + filename + name
  - file+folder vs folderish doc + multiple attachements
 Most existing file-system mapping protocol implementations in Nuxeo have 
 tried to solve this issue : WebDav, WSS and CMIS.
 There is no ideal solution and we will have to add some constraints on the 
 Nuxeo model.
 Rather that continuing with several mapping logic, it's time to build a 
 generic module that will handle all the work :
  - Nuxeo Document = File System resource
  - File System resource = Nuxeo Document (including what is done via 
 FileManager)
  - Listeners to enforce the limitations of the FS model
 This new module should be integrated in WebDav, WSS and CMIS.
 WebDav and CMIS should be based on the newly contributed version from 
 Gagnavarslan that allows FileSystem level mounting via WSS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Updated: (NXP-6681) File system level mapping

2011-05-20 Thread Florent Guillaume (JIRA NUXEO)

 [ 
https://jira.nuxeo.com/browse/NXP-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Florent Guillaume updated NXP-6681:
---

Fix Version/s: (was: 5.4.2)
   5.4.3

 File system level mapping
 -

 Key: NXP-6681
 URL: https://jira.nuxeo.com/browse/NXP-6681
 Project: Nuxeo Enterprise Platform
  Issue Type: User story
  Components: Desktop Integration, WSS integration
Reporter: Thierry Delprat
Assignee: Florent Guillaume
 Fix For: 5.4.3


 We know for quite a long time than mapping Nuxeo repository to a file system 
 is not an easy job because the model do not match correctly :
  - name vs title + filename + name
  - file+folder vs folderish doc + multiple attachements
 Most existing file-system mapping protocol implementations in Nuxeo have 
 tried to solve this issue : WebDav, WSS and CMIS.
 There is no ideal solution and we will have to add some constraints on the 
 Nuxeo model.
 Rather that continuing with several mapping logic, it's time to build a 
 generic module that will handle all the work :
  - Nuxeo Document = File System resource
  - File System resource = Nuxeo Document (including what is done via 
 FileManager)
  - Listeners to enforce the limitations of the FS model
 This new module should be integrated in WebDav, WSS and CMIS.
 WebDav and CMIS should be based on the newly contributed version from 
 Gagnavarslan that allows FileSystem level mounting via WSS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Updated: (NXP-6681) File system level mapping

2011-04-18 Thread JIRA NUXEO

 [ 
https://jira.nuxeo.com/browse/NXP-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stéfane Fermigier updated NXP-6681:
---

Description: 
We know for quite a long time than mapping Nuxeo repository to a file system is 
not an easy job because the model do not match correctly :

 - name vs title + filename + name

 - file+folder vs folderish doc + multiple attachements

Most existing file-system mapping protocol implementations in Nuxeo have tried 
to solve this issue : WebDav, WSS and CMIS.

There is no ideal solution and we will have to add some constraints on the 
Nuxeo model.

Rather that continuing with several mapping logic, it's time to build a generic 
module that will handle all the work :

 - Nuxeo Document = File System resource

 - File System resource = Nuxeo Document (including what is done via 
FileManager)

 - Listeners to enforce the limitations of the FS model

This new module should be integrated in WebDav, WSS and CMIS.
WebDav and CMIS should be based on the newly contributed version from 
Gagnavarslan that allows FileSystem level mounting via WSS.


  was:
We know for quite a long time than mapping Nuxeo repository to a file system is 
not an easy job because the model do not match correctly :

 - name vs title + filename + name

 - file+folder vs folderish doc + multiple attachements

Most existing file-system mapping protocol implementations in Nuxeo have tried 
to solve this issue : WebDav, WSS and CMIS.

There is now ideal solution and we will have to add some constraints on the 
Nuxeo model.

Rather that continuing with several mapping logic, it's time to build a generic 
module that will handle all the work :

 - Nuxeo Document = File System resource

 - File System resource = Nuxeo Document (including what is done via 
FileManager)

 - Listeners to enforce the limitations of the FS model

This new module should be integrated in WebDav, WSS and CMIS.
WebDav and CMIS should be based on the newly contributed version from 
Gagnavarslan that allows FileSystem level mounting via WSS.



 File system level mapping
 -

 Key: NXP-6681
 URL: https://jira.nuxeo.com/browse/NXP-6681
 Project: Nuxeo Enterprise Platform
  Issue Type: User story
  Components: Desktop Integration, WSS integration
Reporter: Thierry Delprat
Assignee: Florent Guillaume
 Fix For: 5.4.2


 We know for quite a long time than mapping Nuxeo repository to a file system 
 is not an easy job because the model do not match correctly :
  - name vs title + filename + name
  - file+folder vs folderish doc + multiple attachements
 Most existing file-system mapping protocol implementations in Nuxeo have 
 tried to solve this issue : WebDav, WSS and CMIS.
 There is no ideal solution and we will have to add some constraints on the 
 Nuxeo model.
 Rather that continuing with several mapping logic, it's time to build a 
 generic module that will handle all the work :
  - Nuxeo Document = File System resource
  - File System resource = Nuxeo Document (including what is done via 
 FileManager)
  - Listeners to enforce the limitations of the FS model
 This new module should be integrated in WebDav, WSS and CMIS.
 WebDav and CMIS should be based on the newly contributed version from 
 Gagnavarslan that allows FileSystem level mounting via WSS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

   
___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets