[JIRA] Created: (CMIS-44) Avoid creating document with empty cmis:contenStreamFileName

Discussion:

Olivier Grisel (JIRA NUXEO)

2011-05-25 22:33:47 UTC

Avoid creating document with empty cmis:contenStreamFileName
------------------------------------------------------------

Key: CMIS-44
URL: https://jira.nuxeo.com/browse/CMIS-44
Project: Nuxeo Chemistry
Issue Type: Improvement
Reporter: Olivier Grisel
Assignee: Florent Guillaume

Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.

A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Olivier Grisel (JIRA NUXEO)

2011-05-25 22:35:47 UTC

Permalink

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

Olivier Grisel updated CMIS-44:
-------------------------------

Summary: Avoid creating document with empty cmis:contentStreamFileName (was: Avoid creating document with empty cmis:contenStreamFileName)

Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: CMIS-44
URL: https://jira.nuxeo.com/browse/CMIS-44
Project: Nuxeo Chemistry
Issue Type: Improvement
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Florent Guillaume (JIRA NUXEO)

2011-06-03 12:27:47 UTC

Permalink

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

Florent Guillaume updated CMIS-44:
----------------------------------

Priority: Major (was: Minor)

Requalified as Major because AD2 is a common client.

Post by Olivier Grisel (JIRA NUXEO)
Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: CMIS-44
URL: https://jira.nuxeo.com/browse/CMIS-44
Project: Nuxeo Chemistry
Issue Type: Improvement
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Priority: Major
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Florent Guillaume (JIRA NUXEO)

2011-10-10 10:14:36 UTC

Permalink

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

Florent Guillaume updated CMIS-44:
----------------------------------

Tags: RDIT-11W41-42

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

Julien Carsique (JIRA NUXEO)

2011-12-29 16:21:32 UTC

Permalink

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

Julien Carsique updated CMIS-44:
--------------------------------

Component/s: CMIS

Post by Olivier Grisel (JIRA NUXEO)
Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: CMIS-44
URL: https://jira.nuxeo.com/browse/CMIS-44
Project: Nuxeo Chemistry
Issue Type: Improvement
Components: CMIS
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Priority: Major
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Julien Carsique (JIRA NUXEO)

2011-12-29 16:23:32 UTC

Permalink

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

Julien Carsique moved CMIS-44 to NXP-8490:
------------------------------------------

Nuxeo Connect support: (was: NONE)
Component/s: (was: CMIS)
CMIS
Workflow: NXP-WF (was: jira)
Key: NXP-8490 (was: CMIS-44)
Project: Nuxeo Enterprise Platform (was: Nuxeo Chemistry)

Post by Olivier Grisel (JIRA NUXEO)
Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: NXP-8490
URL: https://jira.nuxeo.com/browse/NXP-8490
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Components: CMIS
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Priority: Major
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Florent Guillaume (JIRA NUXEO)

2012-01-06 17:04:32 UTC

Permalink

Post by Olivier Grisel (JIRA NUXEO)
Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: NXP-8490
URL: https://jira.nuxeo.com/browse/NXP-8490
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Components: CMIS
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Priority: Major
Fix For: 5.6
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Florent Guillaume (JIRA NUXEO)

2012-01-06 17:04:32 UTC

Permalink

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

Florent Guillaume updated NXP-8490:
-----------------------------------

Tags: (was: RDIT-11W41-42)
Issue Type: Bug (was: Improvement)

Post by Olivier Grisel (JIRA NUXEO)
Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: NXP-8490
URL: https://jira.nuxeo.com/browse/NXP-8490
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: CMIS
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Priority: Major
Fix For: 5.6
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Florent Guillaume (JIRA NUXEO)

2012-01-10 13:29:33 UTC

Permalink

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

Florent Guillaume resolved NXP-8490.
------------------------------------

Resolution: Fixed

https://github.com/nuxeo/nuxeo-chemistry/commit/c8ed72a2755bd163a1093a2254b35db783628617

Post by Olivier Grisel (JIRA NUXEO)
Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: NXP-8490
URL: https://jira.nuxeo.com/browse/NXP-8490
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: CMIS
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Priority: Major
Fix For: 5.6
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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

Florent Guillaume (JIRA NUXEO)

2012-01-25 10:24:13 UTC

Permalink

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

Florent Guillaume updated NXP-8490:
-----------------------------------

Fix Version/s: 5.5.0-HF02

Backport to 5.5.0:
https://github.com/nuxeo/nuxeo-chemistry/commit/abd8270e6a9b29d8482e3a61ac45949443f866ee

Post by Olivier Grisel (JIRA NUXEO)
Avoid creating document with empty cmis:contentStreamFileName
-------------------------------------------------------------
Key: NXP-8490
URL: https://jira.nuxeo.com/browse/NXP-8490
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: CMIS
Reporter: Olivier Grisel
Assignee: Florent Guillaume
Priority: Major
Fix For: 5.5.0-HF02, 5.6
Some CMIS clients such as Adobe Drive 2.1 create cmis:document with a content stream with the correct payload and mimetype info but leave the cmis:contentStreamFileName property empty (the filename of the file in the Adobe Drive is mapped to the cmis:name of the document only). In that case Nuxeo will create with a mimetype info but without a filename fields. This makes the user interface look inconsistent when browsing the content from the default JSF UI.
A propose workaround would be to automatically fill the cmis:contentStreamFileName from the info coming from the cmis:name (and potentially also from the cmis:contentStreamMimeType if the extension is missing so as to find a good looking filename consistent with the mimetype info).

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