[JIRA] Created: (NXP-2607) (dynsearch) support boolean values
(dynsearch) support boolean values -- Key: NXP-2607 URL: http://jira.nuxeo.org/browse/NXP-2607 Project: Nuxeo Enterprise Platform Issue Type: New Feature Reporter: Georges Racinet Assignee: Thierry Delprat The dynsearch add-on does not handle boolean values and corresponding queries yet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Closed: (NXP-1679) maven settings.xml
[ http://jira.nuxeo.org/browse/NXP-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Carsique closed NXP-1679. Resolution: Not A Bug maven settings.xml -- Key: NXP-1679 URL: http://jira.nuxeo.org/browse/NXP-1679 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Julien Carsique Assignee: Julien Carsique -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Commented: (NXP-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=40771#action_40771 ] Florent Guillaume commented on NXP-2567: http://hg.nuxeo.org/nuxeo/nuxeo-core/rev/7e6581a16a3a http://hg.nuxeo.org/nuxeo/nuxeo-platform/rev/94183b51b3c8 Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Resolved: (NXP-2607) (dynsearch) support boolean values
[ http://jira.nuxeo.org/browse/NXP-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georges Racinet resolved NXP-2607. -- Resolution: Fixed (dynsearch) support boolean values -- Key: NXP-2607 URL: http://jira.nuxeo.org/browse/NXP-2607 Project: Nuxeo Enterprise Platform Issue Type: New Feature Reporter: Georges Racinet Assignee: Thierry Delprat The dynsearch add-on does not handle boolean values and corresponding queries yet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-2567: --- Attachment: platform.diff Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Attachments: core.diff, nuxeo-core-1.4.2-NXP-2567.jar, nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar, nuxeo-platform-forum-core-5.1.5-NXP-2567.jar, platform.diff Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-2567: --- Attachment: nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar nuxeo-platform-forum-core-5.1.5-NXP-2567.jar nuxeo-core-1.4.2-NXP-2567.jar Backported jars for use with 5.1.5. Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Attachments: core.diff, nuxeo-core-1.4.2-NXP-2567.jar, nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar, nuxeo-platform-forum-core-5.1.5-NXP-2567.jar, platform.diff Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Commented: (NXP-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=40792#action_40792 ] Florent Guillaume commented on NXP-2567: http://hg.nuxeo.org/nuxeo/nuxeo-platform/rev/7295a7e90525 is also needed Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Attachments: core.diff, nuxeo-core-1.4.2-NXP-2567.jar, nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-2567: --- Attachment: (was: platform.diff) Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Attachments: core.diff, nuxeo-core-1.4.2-NXP-2567.jar, nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-2567: --- Attachment: (was: nuxeo-platform-forum-core-5.1.5-NXP-2567.jar) Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Attachments: core.diff, nuxeo-core-1.4.2-NXP-2567.jar, nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-2567: --- Comment: was deleted Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Attachments: core.diff, nuxeo-core-1.4.2-NXP-2567.jar, nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2567) Avoid lifecycles dependencies on JCRLifeCycleManager
[ http://jira.nuxeo.org/browse/NXP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-2567: --- Attachment: nuxeo-platform-forum-core-5.1.5-NXP-2567.jar platform.diff Backported jars for 5.1.5. Avoid lifecycles dependencies on JCRLifeCycleManager Key: NXP-2567 URL: http://jira.nuxeo.org/browse/NXP-2567 Project: Nuxeo Enterprise Platform Issue Type: Task Affects Versions: 5.1.5 Reporter: Florent Guillaume Assignee: Florent Guillaume Fix For: 5.1.6 Attachments: core.diff, nuxeo-core-1.4.2-NXP-2567.jar, nuxeo-core-jcr-connector-1.4.2-NXP-2567.jar, nuxeo-platform-forum-core-5.1.5-NXP-2567.jar, platform.diff Original Estimate: 2 hours Remaining Estimate: 2 hours Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager. The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend. TODO: nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed. The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService). LifeCycleServiceImpl should only instantiate a single manager for all lifecycles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Created: (NXP-2609) add capacity to create transient graph
add capacity to create transient graph -- Key: NXP-2609 URL: http://jira.nuxeo.org/browse/NXP-2609 Project: Nuxeo Enterprise Platform Issue Type: Improvement Components: Relation Engine Affects Versions: 5.1.5 Reporter: Alexandre Russel Assignee: Alexandre Russel Fix For: 5.1.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Commented: (NXP-2598) make liveedit client able to edit blobs that are not hosted in the default file:content property
[
http://jira.nuxeo.org/browse/NXP-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=40797#action_40797
]
Olivier Grisel commented on NXP-2598:
-
server side fixed in http://hg.nuxeo.org/nuxeo/nuxeo-platform/rev/60df7c675c63
make liveedit client able to edit blobs that are not hosted in the default
file:content property
Key: NXP-2598
URL: http://jira.nuxeo.org/browse/NXP-2598
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Desktop Integration
Affects Versions: 5.1.5, 5.2 M2
Reporter: Olivier Grisel
Assignee: Sun Tan
Priority: Major
Fix For: 5.1.6, 5.2 M3
Original Estimate: 4 hours
Remaining Estimate: 4 hours
The liveedit server side infrastructure is designed to be able to live edit /
create document that have blobs stored in arbitrary fields such as
myschema:myblobfield with file name in myschema:myfilenamefield instead of
the default file:content and file:filename properties.
However it seems that the current live edit client implementation for MS
Office (2.0.12) does not provide the custom field names as request parameters
for the DownloadFileRestlet and probably the UploadFileRestlet too.
According the to the restlets implementations the URL for the former restlet
should be:
GET
/nuxeo/restAPI/{repoId}/{docId}/downloadFile?blobPropertyName=myschema:myblobfieldfilenamePropertyName=myschema:myfilenamefield
The names of the request parameters used by live edit powering restlets are
defined in the org.nuxeo.ecm.platform.ui.web.tag.fn.LiveEditConstants
interface. The documentation in restAPI-contrib.xml deserves a fix too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
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] Created: (NXP-2610) (dynsearch) protect string values against null
(dynsearch) protect string values against null -- Key: NXP-2610 URL: http://jira.nuxeo.org/browse/NXP-2610 Project: Nuxeo Enterprise Platform Issue Type: Bug Reporter: Georges Racinet Assignee: Thierry Delprat If a string value is filled by h:selectOneRadio, there's a possibility to get 'null' In that case there's an NPE in that case in AtomicPredicateBuilder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Assigned: (NXP-2610) (dynsearch) protect string values against null
[ http://jira.nuxeo.org/browse/NXP-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georges Racinet reassigned NXP-2610: Assignee: Georges Racinet (was: Thierry Delprat) (dynsearch) protect string values against null -- Key: NXP-2610 URL: http://jira.nuxeo.org/browse/NXP-2610 Project: Nuxeo Enterprise Platform Issue Type: Bug Reporter: Georges Racinet Assignee: Georges Racinet If a string value is filled by h:selectOneRadio, there's a possibility to get 'null' In that case there's an NPE in that case in AtomicPredicateBuilder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Resolved: (NXP-2363) Adding the filename field in liveedit xml file
[ http://jira.nuxeo.org/browse/NXP-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Grisel resolved NXP-2363. - Resolution: Fixed Fix Version/s: 5.2 M3 5.1.6 duplicate of NXP-2598 Adding the filename field in liveedit xml file -- Key: NXP-2363 URL: http://jira.nuxeo.org/browse/NXP-2363 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Sun Tan Assignee: Olivier Grisel Fix For: 5.1.6, 5.2 M3 To fully customize where to save a document, liveedit clients need to know the filename field (from the xml file). the xml file already provide the schemaName and the content field. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Resolved: (NXP-2312) live edit link does not work on other schema than file
[ http://jira.nuxeo.org/browse/NXP-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sun Tan resolved NXP-2312. -- Resolution: Fixed Fixed in liveedit 2.0.14 live edit link does not work on other schema than file -- Key: NXP-2312 URL: http://jira.nuxeo.org/browse/NXP-2312 Project: Nuxeo Enterprise Platform Issue Type: Bug Affects Versions: 5.1.4 Reporter: Anahide Tchertchian Assignee: Sun Tan Fix For: 5.1.6, 5.2 M3 I added two fields, file2 and content2 to the dublincore schema and referenced them in a layout, and created a File document, setting both files. The live edit link for the file2 blob still opened the file:content blob. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Created: (NXP-2611) [IE] Content tab presentation
[IE] Content tab presentation - Key: NXP-2611 URL: http://jira.nuxeo.org/browse/NXP-2611 Project: Nuxeo Enterprise Platform Issue Type: Bug Reporter: Solen Guitter Assignee: Lise Kemen Fix For: 5.1.7 There is an empty space on the frame (left to Content tab) when user is on Content tab. See attached screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2611) [IE] Content tab presentation
[ http://jira.nuxeo.org/browse/NXP-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solen Guitter updated NXP-2611: --- Attachment: screenshot-1.jpg [IE] Content tab presentation - Key: NXP-2611 URL: http://jira.nuxeo.org/browse/NXP-2611 Project: Nuxeo Enterprise Platform Issue Type: Bug Reporter: Solen Guitter Assignee: Lise Kemen Fix For: 5.1.7 Attachments: screenshot-1.jpg There is an empty space on the frame (left to Content tab) when user is on Content tab. See attached screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2610) (dynsearch) protect all values against null
[ http://jira.nuxeo.org/browse/NXP-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georges Racinet updated NXP-2610: - Description: For instance, if a string value is filled by h:selectOneRadio, there's a possibility to get 'null' In that case there's an NPE in that case in AtomicPredicateBuilder was: If a string value is filled by h:selectOneRadio, there's a possibility to get 'null' In that case there's an NPE in that case in AtomicPredicateBuilder Summary: (dynsearch) protect all values against null (was: (dynsearch) protect string values against null) (dynsearch) protect all values against null --- Key: NXP-2610 URL: http://jira.nuxeo.org/browse/NXP-2610 Project: Nuxeo Enterprise Platform Issue Type: Bug Reporter: Georges Racinet Assignee: Georges Racinet For instance, if a string value is filled by h:selectOneRadio, there's a possibility to get 'null' In that case there's an NPE in that case in AtomicPredicateBuilder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Resolved: (NXP-2610) (dynsearch) protect all values against null
[ http://jira.nuxeo.org/browse/NXP-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georges Racinet resolved NXP-2610. -- Resolution: Fixed (dynsearch) protect all values against null --- Key: NXP-2610 URL: http://jira.nuxeo.org/browse/NXP-2610 Project: Nuxeo Enterprise Platform Issue Type: Bug Reporter: Georges Racinet Assignee: Georges Racinet For instance, if a string value is filled by h:selectOneRadio, there's a possibility to get 'null' In that case there's an NPE in that case in AtomicPredicateBuilder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Resolved: (NXP-2598) make liveedit client able to edit blobs that are not hosted in the default file:content property
[
http://jira.nuxeo.org/browse/NXP-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sun Tan resolved NXP-2598.
--
Resolution: Fixed
Client side fixed in nuxeo-live-edit 2.0.14.
passing blobPropertyName and filenamePropertyName retrived from the xml
(docitem filenameFilePath blobFieldPath)
If these args are not in the xml file, liveedit will use the default file
fields.
make liveedit client able to edit blobs that are not hosted in the default
file:content property
Key: NXP-2598
URL: http://jira.nuxeo.org/browse/NXP-2598
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Desktop Integration
Affects Versions: 5.1.5, 5.2 M2
Reporter: Olivier Grisel
Assignee: Sun Tan
Priority: Major
Fix For: 5.1.6, 5.2 M3
Original Estimate: 4 hours
Remaining Estimate: 4 hours
The liveedit server side infrastructure is designed to be able to live edit /
create document that have blobs stored in arbitrary fields such as
myschema:myblobfield with file name in myschema:myfilenamefield instead of
the default file:content and file:filename properties.
However it seems that the current live edit client implementation for MS
Office (2.0.12) does not provide the custom field names as request parameters
for the DownloadFileRestlet and probably the UploadFileRestlet too.
According the to the restlets implementations the URL for the former restlet
should be:
GET
/nuxeo/restAPI/{repoId}/{docId}/downloadFile?blobPropertyName=myschema:myblobfieldfilenamePropertyName=myschema:myfilenamefield
The names of the request parameters used by live edit powering restlets are
defined in the org.nuxeo.ecm.platform.ui.web.tag.fn.LiveEditConstants
interface. The documentation in restAPI-contrib.xml deserves a fix too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
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] Assigned: (NXP-2306) live edit does not work with list of files
[ http://jira.nuxeo.org/browse/NXP-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Grisel reassigned NXP-2306: --- Assignee: Anahide Tchertchian (was: Sun Tan) The fixes on the LE XML file generator is checkin Nuxeo 5.1.6 and 5.2M3 and the 2.0.14 version of the LE client can now use it. Anahide can you please update the multi files widget (view and edit modes) to add those links in the default webapp? live edit does not work with list of files -- Key: NXP-2306 URL: http://jira.nuxeo.org/browse/NXP-2306 Project: Nuxeo Enterprise Platform Issue Type: Bug Affects Versions: 5.1.4 Reporter: Anahide Tchertchian Assignee: Anahide Tchertchian Fix For: 5.1.6, 5.2 M3 Url is like: nxedit:http://localhost:8080/nuxeo/nxliveedit.faces?action=editrepoID=defaultdocRef=eec3ecbb-e8f7-4261-977e-0ede38a3d21cschema=filesblobField=files%2F0%2FfilefilenameField=files%2F0%2FfilenameconversationId=0NXMAINJSESSIONID=778E6CEBBAF6177D24286524D1979DFF Word opens, but its content is error. It seems there are weird interactions with the file schema too (instead of files, maybe it's due to some default values ?). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Created: (NXP-2612) Live edit v2 : firefox pr otocol handler manage special charactère as arguments
Live edit v2 : firefox protocol handler manage special charactère as arguments -- Key: NXP-2612 URL: http://jira.nuxeo.org/browse/NXP-2612 Project: Nuxeo Enterprise Platform Issue Type: Bug Reporter: Sun Tan Assignee: Sun Tan the current protocol handler is splitting the liste of mimetypes - command editor and args using ':' caractère. In the new openoffice plugin, we're using arguments like macro:///liveedit(xmlfile.xml) which contain ':' caractère. Fix should be done to escape special characters (by using escape method for ex) and manage to handle liveedit for openoffice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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-2612) Live edit v2 : firefox pr otocol handler manage special charactère as arguments
[ http://jira.nuxeo.org/browse/NXP-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sun Tan updated NXP-2612: - Component/s: Desktop Integration Live edit v2 : firefox protocol handler manage special charactère as arguments -- Key: NXP-2612 URL: http://jira.nuxeo.org/browse/NXP-2612 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Desktop Integration Reporter: Sun Tan Assignee: Sun Tan the current protocol handler is splitting the liste of mimetypes - command editor and args using ':' caractère. In the new openoffice plugin, we're using arguments like macro:///liveedit(xmlfile.xml) which contain ':' caractère. Fix should be done to escape special characters (by using escape method for ex) and manage to handle liveedit for openoffice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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] Resolved: (NXP-2612) Live edit v2 : firefox pr otocol handler manage special charactère as arguments
[ http://jira.nuxeo.org/browse/NXP-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sun Tan resolved NXP-2612. -- Resolution: Fixed version 0.3.4 Live edit v2 : firefox protocol handler manage special charactère as arguments -- Key: NXP-2612 URL: http://jira.nuxeo.org/browse/NXP-2612 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Desktop Integration Reporter: Sun Tan Assignee: Sun Tan the current protocol handler is splitting the liste of mimetypes - command editor and args using ':' caractère. In the new openoffice plugin, we're using arguments like macro:///liveedit(xmlfile.xml) which contain ':' caractère. Fix should be done to escape special characters (by using escape method for ex) and manage to handle liveedit for openoffice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nuxeo.org/secure/Administrators.jspa - 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
