[JIRA] Created: (NXP-8734) Improve document XML export using namespaces and prefixes
Improve document XML export using namespaces and prefixes
-
Key: NXP-8734
URL: https://jira.nuxeo.com/browse/NXP-8734
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Affects Versions: 5.5
Reporter: Antoine Taillefer
Currently the document XML export does not fully take advantage of namespaces
and prefixes.
It would be nice to follow this W3C recommandation:
http://www.w3.org/TR/REC-xml-names/.
For example:
* The root element {{}} does not have any namespace, whereas
namespaces are held by the {{}} elements:
{code:xml}
http://www.nuxeo.org/ecm/schemas/dublincore/";
name="dublincore">
...
...
{code}
We could have a namespace on the {{}} element, to be defined.
Why not something like:
{code:xml}
http://www.nuxeo.org/ecm/document/"; ...>
{code}
Not so sure if a per-schema namespace would then still be wanted / useful ?
* List and complex item elements are not prefixed in the XML export, they could
be:
{code:xml}
ataillefer
Administrator
{code}
* What about attribute names and values?
For example in a type-aware export we currently have:
{code:xml}
Administrator
{code}
We could have a prefix for the {{type}} attribute name bound to the global
namespace {{nxdoc}}, and a prefix for the {{type}} attribute value, bound to
the standard XMLSchema namespace:
{code:xml}
http://www.nuxeo.org/ecm/document/";
xmlns:xs="http://www.w3.org/2001/XMLSchema"; ...>
...
Administrator
...
{code}
These are things to think about...
--
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] Commented: (NXP-8595) Override core io document exporter to generate a XML aware of property types
[
https://jira.nuxeo.com/browse/NXP-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=110488#comment-110488
]
Antoine Taillefer commented on NXP-8595:
A new implementation of {{ExportedDocument}} is now available:
{{TypedExportedDocumentImpl}}.
A new implementation of {{DocumentModelReader}} is now available:
{{TypedSingleDocumentReader}}.
> Override core io document exporter to generate a XML aware of property types
>
>
> Key: NXP-8595
> URL: https://jira.nuxeo.com/browse/NXP-8595
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> It would be nice to have an XML export of documents with a {{type}} attribute
> on each field element.
> This would make the work on the XML easier, for example in the Diff feature
> that compares XML exports.
> Typically what we want is:
> {code:xml}
> http://www.nuxeo.org/ecm/schemas/dublincore/";
> name="dublincore">
> Administrator
>
>
> Administrator
> joe
>
>
> 2011-12-29T11:24:25Z
> description
>
>
> Art
> Architecture
>
>
>
> {code}
> The available types are:
> * string
> * boolean
> * long
> * double
> * date
> * binary
> * content
> * complex
> * scalarList
> * complexList
--
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-8546) Add a diff feature to compare two documents or two versions of a document
[
https://jira.nuxeo.com/browse/NXP-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8546:
---
Description:
h2. Use cases
There a several cases where it makes sense to compare (make a diff of) 2
documents.
# *Version diff*: you want to list the modifications between a document and one
of its archived versions, typically in the case of functional specifications.
# *Publication diff*: you want to list the modifications between a published
document and its source, typically in the case of a web site page to measure
the gap between the draft and what is online. In Nuxeo this happens to be the
same case as the Version diff since the published document is a proxy to a
version of the document.
# *Document diff*: you want to list the modifications between a document A and
a document B, typically in the case of product information documents where you
may want to compare the product caracteristics such as material / price /
creation date.
h2. Approach
*Comparing (= making a diff of) 2 documents or 2 versions of a document* can be
seen in a Nuxeo way as *comparing the properties shared by the 2 documents*.
- This means that if a comparison is done between two documents of a different
type, only the schemas in common will be "diffed".
- The result of the comparison only shows the properties that have been
updated, or added / deleted in the case of multivalued properties.
- The comparison should take into account blob-type properties. This is a
tricky part since:
** The diff process depends on the blob mime type, therefore we need to be able
to define a list of supported types for which the diff is possible and for each
type to contribute a tool in charge of the diff.
** We have to find a nice way of displaying the result of a blob diff, again
depending on the blob mime type.
h2. High level User Story
# Launching a comparison
#* In the {{History > Archived Versions}} tab I can check versions. If I check
2 (and only 2) versions then the {{Compare}} button located under the version
listing gets enabled.
#* In the same tab, for each version a button {{Compare to current version}} is
also available.
These two first cases cover the *Version diff* use case.
#* In a content view if I check 2 (and only 2) documents then the {{Compare}}
button located near the {{Copy}}, {{Paste}}, ... buttons gets enabled.
This approach is nice for comparing 2 documents living in the same container or
that are part of a search result, but we also need to be able to compare 2
documents lcoated in separate containers.
#* So if I have added 2 (and only 2) documents to my worklist, then a
{{Compare}} action appears in the worklist actions.
These two cases cover the *Document diff* use case.
#* In a publication Section if I check 1 (and only 1) proxy document then the
{{Compare to working copy}} button located near the {{Delete}}, {{Unpublish}}
buttons gets enabled.
This case covers the *Publication diff* use case.
# Viewing the diff result in the UI
#* The diff result is displayed in the right panel, as a table with 2 columns:
document A / document B, and as many lines as different properties.
#* By default, properties are grouped by schemas. It could be nice to have a
layout / widget system to have a full control on the diff result display.
#* Rendering of a blob-type property diff still has to be defined.
#* Attached screenshot gives an example of the result of a diff between 2
documents, for most property types (simple, complex, complex list).
A color code is used to better distinguish updated / added / deleted values:
#** red for left document
#** green for right document
#* The add/delete notions make sense in the version diff case.
In the document diff case, we can consider that we are comparing the right
document with the left document which is the reference.
Therefore a value existing in the right doc and not in the left one will be
considered as "added" in comparison with the reference doc => green means added.
Conversely for the "deleted" case: red means "deleted".
# PDF export
#* I want to make a PDF export of a diff result.
#* I may also want to automatiucally store the generated PDF in Nuxeo?
was:
h2. Use cases
There a several cases where it makes sense to compare (make a diff of) 2
documents.
# *Version diff*: you want to list the modifications between a document and one
of its archived versions, typically in the case of functional specifications.
# *Publication diff*: you want to list the modifications between a published
document and its source, typically in the case of a web site page to measure
the gap between the draft and what is online. In Nuxeo this happens to be the
same case as the Version diff since the published document is a proxy to a
version of the document.
# *Document diff*: you want to list the modifications between a document A and
a document B, typically in the case
[JIRA] Updated: (NXP-8723) Querying for complex list types and ordering is failing, for instance on the files schema
[
https://jira.nuxeo.com/browse/NXP-8723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8723:
---
Attachment: complex_list_query_fail.log
> Querying for complex list types and ordering is failing, for instance on the
> files schema
> -
>
> Key: NXP-8723
> URL: https://jira.nuxeo.com/browse/NXP-8723
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Core SQL Storage
>Affects Versions: 5.5, 5.5.0-HF01
> Environment: PostgreSQL / h2
>Reporter: Antoine Taillefer
>Assignee: Florent Guillaume
> Attachments: complex_list_query_fail.log
>
>
> Making the following query fails:
> {code}
> Select * from Document where files/*/filename = 'myFile.txt' order by dc:title
> {code}
> Stack trace summary:
> {code}
> 2012-01-24 19:22:58,125 WARN
> [org.nuxeo.ecm.platform.query.nxql.CoreQueryDocumentPageProvider] Failed to
> execute query: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear
> in select list
> Position : 1737
> org.nuxeo.ecm.core.api.ClientException: Failed to execute query: ERROR: for
> SELECT DISTINCT, ORDER BY expressions must appear in select list
> Position : 1737
> at
> org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1571)
> at
> org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1481)
> ...
> Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
> org.nuxeo.ecm.core.query.QueryException. message: Invalid query: Select *
> from Document where files/*/filename = 'myFile.txt' order by dc:title
> at
> org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession$SQLSessionQuery.execute(SQLSession.java:594)
> at
> org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1518)
> ... 169 more
> Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
> org.nuxeo.ecm.core.storage.StorageException. message: Invalid query: Select *
> from Document where files/*/filename = 'myFile.txt' order by dc:title
> at
> org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.query(JDBCMapper.java:769)
> at
> org.nuxeo.ecm.core.storage.sql.CachingMapper.query(CachingMapper.java:85)
> at
> org.nuxeo.ecm.core.storage.sql.SessionImpl.query(SessionImpl.java:1145)
> at
> org.nuxeo.ecm.core.storage.sql.ra.ConnectionImpl.query(ConnectionImpl.java:335)
> at
> org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession$SQLSessionQuery.execute(SQLSession.java:589)
> ... 170 more
> Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
> org.postgresql.util.PSQLException. message: ERROR: for SELECT DISTINCT, ORDER
> BY expressions must appear in select list
> Position : 1737
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2102)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1835)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
> {code}
> Attached full stack trace.
--
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] Created: (NXP-8723) Querying for complex list types and ordering is failing, for instance on the files schema
Querying for complex list types and ordering is failing, for instance on the
files schema
-
Key: NXP-8723
URL: https://jira.nuxeo.com/browse/NXP-8723
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Core SQL Storage
Affects Versions: 5.5.0-HF01, 5.5
Environment: PostgreSQL / h2
Reporter: Antoine Taillefer
Assignee: Florent Guillaume
Making the following query fails:
{code}
Select * from Document where files/*/filename = 'myFile.txt' order by dc:title
{code}
Stack trace summary:
{code}
2012-01-24 19:22:58,125 WARN
[org.nuxeo.ecm.platform.query.nxql.CoreQueryDocumentPageProvider] Failed to
execute query: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in
select list
Position : 1737
org.nuxeo.ecm.core.api.ClientException: Failed to execute query: ERROR: for
SELECT DISTINCT, ORDER BY expressions must appear in select list
Position : 1737
at
org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1571)
at
org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1481)
...
Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
org.nuxeo.ecm.core.query.QueryException. message: Invalid query: Select * from
Document where files/*/filename = 'myFile.txt' order by dc:title
at
org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession$SQLSessionQuery.execute(SQLSession.java:594)
at
org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1518)
... 169 more
Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
org.nuxeo.ecm.core.storage.StorageException. message: Invalid query: Select *
from Document where files/*/filename = 'myFile.txt' order by dc:title
at
org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.query(JDBCMapper.java:769)
at
org.nuxeo.ecm.core.storage.sql.CachingMapper.query(CachingMapper.java:85)
at
org.nuxeo.ecm.core.storage.sql.SessionImpl.query(SessionImpl.java:1145)
at
org.nuxeo.ecm.core.storage.sql.ra.ConnectionImpl.query(ConnectionImpl.java:335)
at
org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession$SQLSessionQuery.execute(SQLSession.java:589)
... 170 more
Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
org.postgresql.util.PSQLException. message: ERROR: for SELECT DISTINCT, ORDER
BY expressions must appear in select list
Position : 1737
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2102)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1835)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
{code}
Attached full stack trace.
--
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] Created: (NXP-8706) Saving an NXQL query with quotes in the Quick Search gadget crashes
Saving an NXQL query with quotes in the Quick Search gadget crashes
---
Key: NXP-8706
URL: https://jira.nuxeo.com/browse/NXP-8706
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Dashboard / OpenSocial
Affects Versions: 5.5.0-HF01, 5.5
Reporter: Antoine Taillefer
Attachments: save_NXQL_query_quick_search_gadget.log
In the Quick search gadget, trying to save an NXQL query such as {{Select *
from Document where dc:creator='Administrator'}} crashes (same with double
quotes):
{code}
18:36:19,930 WARN [CoreQueryDocumentPageProvider] Failed to execute query:
org.nuxeo.ecm.core.query.QueryParseException: Lexical Error: Illegal character
<&> at offset 40 in query: Select * from Document where
dc:creator='Administrator'
org.nuxeo.ecm.core.api.ClientException: Failed to execute query:
org.nuxeo.ecm.core.query.QueryParseException: Lexical Error: Illegal character
<&> at offset 40 in query: Select * from Document where
dc:creator='Administrator'
at
org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1474)
at
org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1384)
at sun.reflect.GeneratedMethodAccessor407.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.nuxeo.ecm.core.api.TransactionalCoreSessionWrapper.invoke(TransactionalCoreSessionWrapper.java:127)
at $Proxy28.query(Unknown Source)
at
org.nuxeo.ecm.platform.query.nxql.CoreQueryDocumentPageProvider.getCurrentPage(CoreQueryDocumentPageProvider.java:93)
at
org.nuxeo.ecm.automation.core.operations.services.PaginableDocumentModelListImpl.(PaginableDocumentModelListImpl.java:34)
at
org.nuxeo.ecm.automation.core.operations.services.DocumentPageProviderOperation.run(DocumentPageProviderOperation.java:136)
{code}
--
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-8706) Saving an NXQL query with quotes in the Quick Search gadget crashes
[
https://jira.nuxeo.com/browse/NXP-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8706:
---
Attachment: save_NXQL_query_quick_search_gadget.log
Attached full stack trace
> Saving an NXQL query with quotes in the Quick Search gadget crashes
> ---
>
> Key: NXP-8706
> URL: https://jira.nuxeo.com/browse/NXP-8706
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Dashboard / OpenSocial
>Affects Versions: 5.5, 5.5.0-HF01
>Reporter: Antoine Taillefer
> Attachments: save_NXQL_query_quick_search_gadget.log
>
>
> In the Quick search gadget, trying to save an NXQL query such as {{Select *
> from Document where dc:creator='Administrator'}} crashes (same with double
> quotes):
> {code}
> 18:36:19,930 WARN [CoreQueryDocumentPageProvider] Failed to execute query:
> org.nuxeo.ecm.core.query.QueryParseException: Lexical Error: Illegal
> character <&> at offset 40 in query: Select * from Document where
> dc:creator='Administrator'
> org.nuxeo.ecm.core.api.ClientException: Failed to execute query:
> org.nuxeo.ecm.core.query.QueryParseException: Lexical Error: Illegal
> character <&> at offset 40 in query: Select * from Document where
> dc:creator='Administrator'
> at
> org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1474)
> at
> org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1384)
> at sun.reflect.GeneratedMethodAccessor407.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.nuxeo.ecm.core.api.TransactionalCoreSessionWrapper.invoke(TransactionalCoreSessionWrapper.java:127)
> at $Proxy28.query(Unknown Source)
> at
> org.nuxeo.ecm.platform.query.nxql.CoreQueryDocumentPageProvider.getCurrentPage(CoreQueryDocumentPageProvider.java:93)
> at
> org.nuxeo.ecm.automation.core.operations.services.PaginableDocumentModelListImpl.(PaginableDocumentModelListImpl.java:34)
> at
> org.nuxeo.ecm.automation.core.operations.services.DocumentPageProviderOperation.run(DocumentPageProviderOperation.java:136)
> {code}
--
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] Work started: (NXP-8589) Contribute a simple text differ
[ https://jira.nuxeo.com/browse/NXP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NXP-8589 started by Antoine Taillefer. > Contribute a simple text differ > --- > > Key: NXP-8589 > URL: https://jira.nuxeo.com/browse/NXP-8589 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 1 day > -- 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] Assigned: (NXP-8589) Contribute a simple text differ
[ https://jira.nuxeo.com/browse/NXP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer reassigned NXP-8589: -- Assignee: Antoine Taillefer > Contribute a simple text differ > --- > > Key: NXP-8589 > URL: https://jira.nuxeo.com/browse/NXP-8589 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 1 day > -- 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] Work logged: (NXP-8587) Make the diff service configurable with extension points
[
https://jira.nuxeo.com/browse/NXP-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Antoine Taillefer logged work on NXP-8587:
--
Author: Antoine Taillefer
Created on: 20/01/12 13:29
Start Date: 20/01/12 13:28
Worklog Time Spent: 1 day
Work Description: Add a (temporary) extendsion point to contribute
complex items order in diff display.
Issue Time Tracking
---
Worklog Id: (was: 27832)
Time Spent: 1 day
Remaining Estimate: 1 day (was: 2 days)
> Make the diff service configurable with extension points
>
>
> Key: NXP-8587
> URL: https://jira.nuxeo.com/browse/NXP-8587
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Original Estimate: 2 days
> Time Spent: 1 day
> Remaining Estimate: 1 day
>
> The {{DocumentDiffService}} should expose extension points to
> h5. Configure XMLUnit for the diff, what is currently hard-coded:
> {code:java}
> protected void configureXMLUnit() {
> XMLUnit.setIgnoreWhitespace(true);
> XMLUnit.setIgnoreDiffBetweenTextAndCDATA(true);
> }
> {code}
> h5. Configure the diff itself, what is currently hard-coded:
> {code:java}
> protected void configureDiff(Diff diff) {
> diff.overrideDifferenceListener(new IgnoreStructuralDifferenceListener());
>
> diff.overrideElementQualifier(new ElementNameAndAttributeQualifier());
> }
> {code}
> h5. Contribute a "second-level" differ for a given type of property.
> The first-level diff detects the document properties that are different
> between the 2 docs, for example {{dc:title}}.
> For now it also holds the different values on both sides: left and right, for
> example: {{{left = My first doc / right = My second doc}}}.
> The second-level diff would use the type held by the first-level diff of a
> property to call the specific differ for this type on the document's property.
> This implies a refactoring of the {{PropertyDiff}} implementations. The
> first-level diff no more needs to hold the different values, but the type of
> diff and a reference to the property itself (xpath like).
> For example a structure like {{{type = "complexList", xpath =
> "mySchema:complexListField[1]/complexListItem[2]/stringItem[1]"}}}.
> This way to access the second-level diff for a property, the system would
> just have to call the appropriate differ contributed for the diff type. If no
> differ is associated to the diff type, a fallback is done on the default one.
> Example of a contribution of a complexList differ:
> {code:xml}
>
> {code}
--
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] Commented: (NXP-8589) Contribute a simple text differ
[ https://jira.nuxeo.com/browse/NXP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=110072#comment-110072 ] Antoine Taillefer commented on NXP-8589: We need to have a test differ that allows a nice rendition of a textual diff. Something like: http://code.google.com/p/google-diff-match-patch/ Demo here: http://neil.fraser.name/software/diff_match_patch/svn/trunk/demos/demo_diff.html Tested this tool, seems to match our need. Still have to check the license terms and if another opensource tool would not fit better. > Contribute a simple text differ > --- > > Key: NXP-8589 > URL: https://jira.nuxeo.com/browse/NXP-8589 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 1 day > -- 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] Work logged: (NXP-8589) Contribute a simple text differ
[
https://jira.nuxeo.com/browse/NXP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Antoine Taillefer logged work on NXP-8589:
--
Author: Antoine Taillefer
Created on: 20/01/12 13:25
Start Date: 20/01/12 13:25
Worklog Time Spent: 1 day
Work Description: Test diff_match_patch
Issue Time Tracking
---
Worklog Id: (was: 27831)
Time Spent: 1 day
Remaining Estimate: 1 day (was: 2 days)
> Contribute a simple text differ
> ---
>
> Key: NXP-8589
> URL: https://jira.nuxeo.com/browse/NXP-8589
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
> Original Estimate: 2 days
> Time Spent: 1 day
> Remaining Estimate: 1 day
>
--
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-8589) Contribute a simple text differ
[ https://jira.nuxeo.com/browse/NXP-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8589: --- Status: Open (was: Triage) > Contribute a simple text differ > --- > > Key: NXP-8589 > URL: https://jira.nuxeo.com/browse/NXP-8589 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer > Original Estimate: 2 days > Remaining Estimate: 2 days > -- 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] Work started: (NXP-8587) Make the diff service configurable with extension points
[
https://jira.nuxeo.com/browse/NXP-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on NXP-8587 started by Antoine Taillefer.
> Make the diff service configurable with extension points
>
>
> Key: NXP-8587
> URL: https://jira.nuxeo.com/browse/NXP-8587
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The {{DocumentDiffService}} should expose extension points to
> h5. Configure XMLUnit for the diff, what is currently hard-coded:
> {code:java}
> protected void configureXMLUnit() {
> XMLUnit.setIgnoreWhitespace(true);
> XMLUnit.setIgnoreDiffBetweenTextAndCDATA(true);
> }
> {code}
> h5. Configure the diff itself, what is currently hard-coded:
> {code:java}
> protected void configureDiff(Diff diff) {
> diff.overrideDifferenceListener(new IgnoreStructuralDifferenceListener());
>
> diff.overrideElementQualifier(new ElementNameAndAttributeQualifier());
> }
> {code}
> h5. Contribute a "second-level" differ for a given type of property.
> The first-level diff detects the document properties that are different
> between the 2 docs, for example {{dc:title}}.
> For now it also holds the different values on both sides: left and right, for
> example: {{{left = My first doc / right = My second doc}}}.
> The second-level diff would use the type held by the first-level diff of a
> property to call the specific differ for this type on the document's property.
> This implies a refactoring of the {{PropertyDiff}} implementations. The
> first-level diff no more needs to hold the different values, but the type of
> diff and a reference to the property itself (xpath like).
> For example a structure like {{{type = "complexList", xpath =
> "mySchema:complexListField[1]/complexListItem[2]/stringItem[1]"}}}.
> This way to access the second-level diff for a property, the system would
> just have to call the appropriate differ contributed for the diff type. If no
> differ is associated to the diff type, a fallback is done on the default one.
> Example of a contribution of a complexList differ:
> {code:xml}
>
> {code}
--
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-8587) Make the diff service configurable with extension points
[
https://jira.nuxeo.com/browse/NXP-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8587:
---
Status: Open (was: Triage)
> Make the diff service configurable with extension points
>
>
> Key: NXP-8587
> URL: https://jira.nuxeo.com/browse/NXP-8587
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The {{DocumentDiffService}} should expose extension points to
> h5. Configure XMLUnit for the diff, what is currently hard-coded:
> {code:java}
> protected void configureXMLUnit() {
> XMLUnit.setIgnoreWhitespace(true);
> XMLUnit.setIgnoreDiffBetweenTextAndCDATA(true);
> }
> {code}
> h5. Configure the diff itself, what is currently hard-coded:
> {code:java}
> protected void configureDiff(Diff diff) {
> diff.overrideDifferenceListener(new IgnoreStructuralDifferenceListener());
>
> diff.overrideElementQualifier(new ElementNameAndAttributeQualifier());
> }
> {code}
> h5. Contribute a "second-level" differ for a given type of property.
> The first-level diff detects the document properties that are different
> between the 2 docs, for example {{dc:title}}.
> For now it also holds the different values on both sides: left and right, for
> example: {{{left = My first doc / right = My second doc}}}.
> The second-level diff would use the type held by the first-level diff of a
> property to call the specific differ for this type on the document's property.
> This implies a refactoring of the {{PropertyDiff}} implementations. The
> first-level diff no more needs to hold the different values, but the type of
> diff and a reference to the property itself (xpath like).
> For example a structure like {{{type = "complexList", xpath =
> "mySchema:complexListField[1]/complexListItem[2]/stringItem[1]"}}}.
> This way to access the second-level diff for a property, the system would
> just have to call the appropriate differ contributed for the diff type. If no
> differ is associated to the diff type, a fallback is done on the default one.
> Example of a contribution of a complexList differ:
> {code:xml}
>
> {code}
--
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] Resolved: (NXP-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[ https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer resolved NXP-8594. Resolution: Fixed > Refactor to take advantage of a nicer XML export and fix remaining bugs > --- > > Key: NXP-8594 > URL: https://jira.nuxeo.com/browse/NXP-8594 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 3 days > Time Spent: 3 days, 2 hours > Remaining Estimate: 0 minutes > -- 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] Commented: (NXP-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[ https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=110026#comment-110026 ] Antoine Taillefer commented on NXP-8594: master: https://github.com/ataillefer/nuxeo-platform-diff/commits/master (will move later to a nuxeo repository) > Refactor to take advantage of a nicer XML export and fix remaining bugs > --- > > Key: NXP-8594 > URL: https://jira.nuxeo.com/browse/NXP-8594 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 3 days > Time Spent: 3 days, 2 hours > Remaining Estimate: 0 minutes > -- 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] Work logged: (NXP-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[
https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Antoine Taillefer logged work on NXP-8594:
--
Author: Antoine Taillefer
Created on: 19/01/12 14:26
Start Date: 19/01/12 14:26
Worklog Time Spent: 3 days, 2 hours
Issue Time Tracking
---
Worklog Id: (was: 27826)
Time Spent: 3 days, 2 hours
Remaining Estimate: 0 minutes (was: 3 days)
> Refactor to take advantage of a nicer XML export and fix remaining bugs
> ---
>
> Key: NXP-8594
> URL: https://jira.nuxeo.com/browse/NXP-8594
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Original Estimate: 3 days
> Time Spent: 3 days, 2 hours
> Remaining Estimate: 0 minutes
>
--
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] Commented: (NXP-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[
https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=110023#comment-110023
]
Antoine Taillefer commented on NXP-8594:
Several refactorings have been done:
* The {{PropertyDiff}} object now holds a {{propertyType}} attribute, to be
chosen among the string constants defined in
{{org.nuxeo.ecm.platform.diff.model.PropertyType}} ("string", "boolean",
"date", "integer", "long", "double", "binary", "content", "complex",
"scalarList", "complexList").
This {{propertyType}} is set depending on the property's {{type}} attribute
(cf. https://jira.nuxeo.com/browse/NXP-8595) in the document XML export.
It allows us to know what kind of differ we will have to use when displaying
the property diff result.
* To display the diff, we now use:
** The compared documents to get their properties by using
({{doc.getProperty(schema, field)}}), instead of using the {{control}} and
{{test}} values from the {{Difference}} object.
** The property diff to now _how_ to display the diff result depending on the
property's type and _which part_ of the property is different between the left
or right doc.
For instance, on a complex property, the property diff allows us to know on
which specific sub field a difference was detected.
On a string property, the property diff will allow us to highlight the specific
parts of the text that have been added / removed, and to display a nice
representation of the actual differences (cf.
https://jira.nuxeo.com/browse/NXP-8589 for later work to be done).
* Bug fixes:
** Comparing complex list properties with different number of items no more
crashes.
** Comparing documents with different schemas (for example a _Note_ and a
_File_) no more crashes: only the common schemas are take into account for the
diff.
> Refactor to take advantage of a nicer XML export and fix remaining bugs
> ---
>
> Key: NXP-8594
> URL: https://jira.nuxeo.com/browse/NXP-8594
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
--
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] Work started: (NXP-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[ https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NXP-8594 started by Antoine Taillefer. > Refactor to take advantage of a nicer XML export and fix remaining bugs > --- > > Key: NXP-8594 > URL: https://jira.nuxeo.com/browse/NXP-8594 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[ https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8594: --- Status: Open (was: Triage) > Refactor to take advantage of a nicer XML export and fix remaining bugs > --- > > Key: NXP-8594 > URL: https://jira.nuxeo.com/browse/NXP-8594 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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-8665) Empty reRender in suggestbox template is not only useless but can cause an error
[
https://jira.nuxeo.com/browse/NXP-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8665:
---
Description:
In
{{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
there is an empty {{reRender}} attribute:
{code:html}
{code}
This empty {{reRender}}:
# Is useless.
# Can cause the following error (attached complete stacktrace) when selecting a
suggestion that does not trigger an URL redirect.
{code}
2012-01-16 11:51:02,604 WARN [org.jboss.seam.web.ExceptionFilter] handling
uncaught exception
javax.servlet.ServletException: String index out of range: 0
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
...
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 0
at java.lang.String.charAt(Unknown Source)
at
org.ajax4jsf.context.AjaxContextImpl.convertId(AjaxContextImpl.java:388)
at
org.ajax4jsf.context.AjaxContextImpl.addRegionsFromComponent(AjaxContextImpl.java:331)
at
org.ajax4jsf.component.AjaxActionComponent.setupReRender(AjaxActionComponent.java:96)
at
org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:60)
at javax.faces.component.UIData.broadcast(UIData.java:938)
at
org.richfaces.component.UISuggestionBox.broadcast(UISuggestionBox.java:421)
at
org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
at
org.ajax4jsf.component.AjaxViewRoot.broadcastAjaxEvents(AjaxViewRoot.java:340)
at
org.ajax4jsf.application.AjaxViewHandler.processAjaxEvents(AjaxViewHandler.java:216)
at
org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:169)
at
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at
org.nuxeo.ecm.platform.ui.web.lifecycle.NuxeoLifeCycleImpl.render(NuxeoLifeCycleImpl.java:98)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
{code}
was:
In
{{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
there is an empty {{reRender}} attribute:
{code:html}
{code}
This empty {{reRender}}:
# Is useless.
# Can cause the attached error when selecting a suggestion that does not
trigger an URL redirect.
> Empty reRender in suggestbox template is not only useless but can cause an
> error
>
>
> Key: NXP-8665
> URL: https://jira.nuxeo.com/browse/NXP-8665
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Attachments: empty_reRender.log
>
>
> In
> {{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
> there is an empty {{reRender}} attribute:
> {code:html}
>focus="" bypassUpdates="true" reRender=""
> action="#{suggestboxActions.handleSelection(result)}">
>
>
> {code}
> This empty {{reRender}}:
> # Is useless.
> # Can cause the following error (attached complete stacktrace) when selecting
> a suggestion that does not trigger an URL redirect.
> {code}
> 2012-01-16 11:51:02,604 WARN [org.jboss.seam.web.ExceptionFilter] handling
> uncaught exception
> javax.servlet.ServletException: String index out of range: 0
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> ...
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
> range: 0
> at java.lang.String.charAt(Unknown Source)
> at
> org.ajax4jsf.context.AjaxContextImpl.convertId(AjaxContextImpl.java:388)
> at
> org.ajax4jsf.context.AjaxContextImpl.addRegionsFromComponent(AjaxContextImpl.java:331)
> at
> org.ajax4jsf.component.AjaxActionComponent.setupReRender(AjaxActionComponent.java:96)
> at
> org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:60)
> at javax.faces.component.UIData.broadcast(UIData.java:938)
> at
> org.richfaces.component.UISuggestionBox.broadcast(UISuggestionBox.java:421)
> at
> org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
> at
>
[JIRA] Updated: (NXP-8665) Empty reRender in suggestbox template is not only useless but can cause an error
[
https://jira.nuxeo.com/browse/NXP-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8665:
---
Description:
In
{{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
there is an empty {{reRender}} attribute:
{code:html}
{code}
This empty {{reRender}}:
# Is useless.
# Can cause the following error (attached complete stacktrace) when selecting a
suggestion that does not trigger an URL redirect.
{code}
2012-01-16 11:51:02,604 WARN [org.jboss.seam.web.ExceptionFilter] handling
uncaught exception
javax.servlet.ServletException: String index out of range: 0
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
...
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 0
at java.lang.String.charAt(Unknown Source)
at
org.ajax4jsf.context.AjaxContextImpl.convertId(AjaxContextImpl.java:388)
at
org.ajax4jsf.context.AjaxContextImpl.addRegionsFromComponent(AjaxContextImpl.java:331)
at
org.ajax4jsf.component.AjaxActionComponent.setupReRender(AjaxActionComponent.java:96)
at
org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:60)
at javax.faces.component.UIData.broadcast(UIData.java:938)
at
org.richfaces.component.UISuggestionBox.broadcast(UISuggestionBox.java:421)
at
org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
at
org.ajax4jsf.component.AjaxViewRoot.broadcastAjaxEvents(AjaxViewRoot.java:340)
at
org.ajax4jsf.application.AjaxViewHandler.processAjaxEvents(AjaxViewHandler.java:216)
at
org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:169)
at
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at
org.nuxeo.ecm.platform.ui.web.lifecycle.NuxeoLifeCycleImpl.render(NuxeoLifeCycleImpl.java:98)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
{code}
was:
In
{{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
there is an empty {{reRender}} attribute:
{code:html}
{code}
This empty {{reRender}}:
# Is useless.
# Can cause the following error (attached complete stacktrace) when selecting a
suggestion that does not trigger an URL redirect.
{code}
2012-01-16 11:51:02,604 WARN [org.jboss.seam.web.ExceptionFilter] handling
uncaught exception
javax.servlet.ServletException: String index out of range: 0
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
...
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 0
at java.lang.String.charAt(Unknown Source)
at
org.ajax4jsf.context.AjaxContextImpl.convertId(AjaxContextImpl.java:388)
at
org.ajax4jsf.context.AjaxContextImpl.addRegionsFromComponent(AjaxContextImpl.java:331)
at
org.ajax4jsf.component.AjaxActionComponent.setupReRender(AjaxActionComponent.java:96)
at
org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:60)
at javax.faces.component.UIData.broadcast(UIData.java:938)
at
org.richfaces.component.UISuggestionBox.broadcast(UISuggestionBox.java:421)
at
org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
at
org.ajax4jsf.component.AjaxViewRoot.broadcastAjaxEvents(AjaxViewRoot.java:340)
at
org.ajax4jsf.application.AjaxViewHandler.processAjaxEvents(AjaxViewHandler.java:216)
at
org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:169)
at
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at
org.nuxeo.ecm.platform.ui.web.lifecycle.NuxeoLifeCycleImpl.render(NuxeoLifeCycleImpl.java:98)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
{code}
> Empty reRender in suggestbox template is not only useless but can cause an
> error
>
>
> Key: NXP-8665
> URL: https://jira.nuxeo.com/browse/NXP-8665
> Project: Nuxeo
[JIRA] Resolved: (NXP-8665) Empty reRender in suggestbox template is not only useless but can cause an error
[
https://jira.nuxeo.com/browse/NXP-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer resolved NXP-8665.
Resolution: Fixed
> Empty reRender in suggestbox template is not only useless but can cause an
> error
>
>
> Key: NXP-8665
> URL: https://jira.nuxeo.com/browse/NXP-8665
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Attachments: empty_reRender.log
>
>
> In
> {{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
> there is an empty {{reRender}} attribute:
> {code:html}
>focus="" bypassUpdates="true" reRender=""
> action="#{suggestboxActions.handleSelection(result)}">
>
>
> {code}
> This empty {{reRender}}:
> # Is useless.
> # Can cause the attached error when selecting a suggestion that does not
> trigger an URL redirect.
--
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] Commented: (NXP-8665) Empty reRender in suggestbox template is not only useless but can cause an error
[
https://jira.nuxeo.com/browse/NXP-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109883#comment-109883
]
Antoine Taillefer commented on NXP-8665:
Fixed here on master:
https://github.com/nuxeo/nuxeo-platform-suggestbox/commit/f0e33256248463ee74b3c4f0688be9893a16aea8
> Empty reRender in suggestbox template is not only useless but can cause an
> error
>
>
> Key: NXP-8665
> URL: https://jira.nuxeo.com/browse/NXP-8665
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Attachments: empty_reRender.log
>
>
> In
> {{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
> there is an empty {{reRender}} attribute:
> {code:html}
>focus="" bypassUpdates="true" reRender=""
> action="#{suggestboxActions.handleSelection(result)}">
>
>
> {code}
> This empty {{reRender}}:
> # Is useless.
> # Can cause the attached error when selecting a suggestion that does not
> trigger an URL redirect.
--
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-8665) Empty reRender in suggestbox template is not only useless but can cause an error
[
https://jira.nuxeo.com/browse/NXP-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8665:
---
Status: Open (was: Triage)
> Empty reRender in suggestbox template is not only useless but can cause an
> error
>
>
> Key: NXP-8665
> URL: https://jira.nuxeo.com/browse/NXP-8665
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Attachments: empty_reRender.log
>
>
> In
> {{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
> there is an empty {{reRender}} attribute:
> {code:html}
>focus="" bypassUpdates="true" reRender=""
> action="#{suggestboxActions.handleSelection(result)}">
>
>
> {code}
> This empty {{reRender}}:
> # Is useless.
> # Can cause the attached error when selecting a suggestion that does not
> trigger an URL redirect.
--
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-8665) Empty reRender in suggestbox template is not only useless but can cause an error
[
https://jira.nuxeo.com/browse/NXP-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8665:
---
Attachment: empty_reRender.log
> Empty reRender in suggestbox template is not only useless but can cause an
> error
>
>
> Key: NXP-8665
> URL: https://jira.nuxeo.com/browse/NXP-8665
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Attachments: empty_reRender.log
>
>
> In
> {{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
> there is an empty {{reRender}} attribute:
> {code:html}
>focus="" bypassUpdates="true" reRender=""
> action="#{suggestboxActions.handleSelection(result)}">
>
>
> {code}
> This empty {{reRender}}:
> # Is useless.
> # Can cause the attached error when selecting a suggestion that does not
> trigger an URL redirect.
--
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] Created: (NXP-8665) Empty reRender in suggestbox template is not only useless but can cause an error
Empty reRender in suggestbox template is not only useless but can cause an error
Key: NXP-8665
URL: https://jira.nuxeo.com/browse/NXP-8665
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Affects Versions: 5.5
Reporter: Antoine Taillefer
Assignee: Antoine Taillefer
Fix For: 5.6
In
{{/nuxeo-platform-suggestbox-jsf/src/main/resources/web/nuxeo.war/search/suggestbox.xhtml}},
there is an empty {{reRender}} attribute:
{code:html}
{code}
This empty {{reRender}}:
# Is useless.
# Can cause the attached error when selecting a suggestion that does not
trigger an URL redirect.
--
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] Assigned: (NXP-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[ https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer reassigned NXP-8594: -- Assignee: Antoine Taillefer > Refactor to take advantage of a nicer XML export and fix remaining bugs > --- > > Key: NXP-8594 > URL: https://jira.nuxeo.com/browse/NXP-8594 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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] Resolved: (NXP-8585) Allow core io document exporter to be overriden
[ https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer resolved NXP-8585. Resolution: Fixed > Allow core io document exporter to be overriden > --- > > Key: NXP-8585 > URL: https://jira.nuxeo.com/browse/NXP-8585 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Affects Versions: 5.5 >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.6 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > We need to be able to override the core io document exporter to be able to > generate a different XML export file. -- 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] Commented: (NXP-8585) Allow core io document exporter to be overriden
[ https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109367#comment-109367 ] Antoine Taillefer commented on NXP-8585: master: https://github.com/nuxeo/nuxeo-core/commit/f27503c7eb318edbefa7098c852893f4d23f7274#nuxeo-core-io > Allow core io document exporter to be overriden > --- > > Key: NXP-8585 > URL: https://jira.nuxeo.com/browse/NXP-8585 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Affects Versions: 5.5 >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.6 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > We need to be able to override the core io document exporter to be able to > generate a different XML export file. -- 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-8585) Allow core io document exporter to be overriden
[ https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8585: --- Status: Open (was: Triage) > Allow core io document exporter to be overriden > --- > > Key: NXP-8585 > URL: https://jira.nuxeo.com/browse/NXP-8585 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Affects Versions: 5.5 >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.6 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > We need to be able to override the core io document exporter to be able to > generate a different XML export file. -- 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] Work logged: (NXP-8595) Override core io document exporter to generate a XML aware of property types
[
https://jira.nuxeo.com/browse/NXP-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Antoine Taillefer logged work on NXP-8595:
--
Author: Antoine Taillefer
Created on: 12/01/12 02:41
Start Date: 12/01/12 02:41
Worklog Time Spent: 4 hours
Issue Time Tracking
---
Worklog Id: (was: 27652)
Time Spent: 4 hours
Remaining Estimate: 0 minutes (was: 4 hours)
> Override core io document exporter to generate a XML aware of property types
>
>
> Key: NXP-8595
> URL: https://jira.nuxeo.com/browse/NXP-8595
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> It would be nice to have an XML export of documents with a {{type}} attribute
> on each field element.
> This would make the work on the XML easier, for example in the Diff feature
> that compares XML exports.
> Typically what we want is:
> {code:xml}
> http://www.nuxeo.org/ecm/schemas/dublincore/";
> name="dublincore">
> Administrator
>
>
> Administrator
> joe
>
>
> 2011-12-29T11:24:25Z
> description
>
>
> Art
> Architecture
>
>
>
> {code}
> The available types are:
> * string
> * boolean
> * long
> * double
> * date
> * binary
> * content
> * complex
> * scalarList
> * complexList
--
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-8595) Override core io document exporter to generate a XML aware of property types
[
https://jira.nuxeo.com/browse/NXP-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8595:
---
Status: Open (was: Triage)
> Override core io document exporter to generate a XML aware of property types
>
>
> Key: NXP-8595
> URL: https://jira.nuxeo.com/browse/NXP-8595
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> It would be nice to have an XML export of documents with a {{type}} attribute
> on each field element.
> This would make the work on the XML easier, for example in the Diff feature
> that compares XML exports.
> Typically what we want is:
> {code:xml}
> http://www.nuxeo.org/ecm/schemas/dublincore/";
> name="dublincore">
> Administrator
>
>
> Administrator
> joe
>
>
> 2011-12-29T11:24:25Z
> description
>
>
> Art
> Architecture
>
>
>
> {code}
> The available types are:
> * string
> * boolean
> * long
> * double
> * date
> * binary
> * content
> * complex
> * scalarList
> * complexList
--
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] Resolved: (NXP-8595) Override core io document exporter to generate a XML aware of property types
[
https://jira.nuxeo.com/browse/NXP-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer resolved NXP-8595.
Resolution: Fixed
> Override core io document exporter to generate a XML aware of property types
>
>
> Key: NXP-8595
> URL: https://jira.nuxeo.com/browse/NXP-8595
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> It would be nice to have an XML export of documents with a {{type}} attribute
> on each field element.
> This would make the work on the XML easier, for example in the Diff feature
> that compares XML exports.
> Typically what we want is:
> {code:xml}
> http://www.nuxeo.org/ecm/schemas/dublincore/";
> name="dublincore">
> Administrator
>
>
> Administrator
> joe
>
>
> 2011-12-29T11:24:25Z
> description
>
>
> Art
> Architecture
>
>
>
> {code}
> The available types are:
> * string
> * boolean
> * long
> * double
> * date
> * binary
> * content
> * complex
> * scalarList
> * complexList
--
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] Commented: (NXP-8595) Override core io document exporter to generate a XML aware of property types
[
https://jira.nuxeo.com/browse/NXP-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109366#comment-109366
]
Antoine Taillefer commented on NXP-8595:
master:
https://github.com/nuxeo/nuxeo-core/commit/5686c606f8f94bd7d74536b6ed740a9c83c22755
> Override core io document exporter to generate a XML aware of property types
>
>
> Key: NXP-8595
> URL: https://jira.nuxeo.com/browse/NXP-8595
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> It would be nice to have an XML export of documents with a {{type}} attribute
> on each field element.
> This would make the work on the XML easier, for example in the Diff feature
> that compares XML exports.
> Typically what we want is:
> {code:xml}
> http://www.nuxeo.org/ecm/schemas/dublincore/";
> name="dublincore">
> Administrator
>
>
> Administrator
> joe
>
>
> 2011-12-29T11:24:25Z
> description
>
>
> Art
> Architecture
>
>
>
> {code}
> The available types are:
> * string
> * boolean
> * long
> * double
> * date
> * binary
> * content
> * complex
> * scalarList
> * complexList
--
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-8595) Override core io document exporter to generate a XML aware of property types
[
https://jira.nuxeo.com/browse/NXP-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8595:
---
Description:
It would be nice to have an XML export of documents with a {{type}} attribute
on each field element.
This would make the work on the XML easier, for example in the Diff feature
that compares XML exports.
Typically what we want is:
{code:xml}
http://www.nuxeo.org/ecm/schemas/dublincore/";
name="dublincore">
Administrator
Administrator
joe
2011-12-29T11:24:25Z
description
Art
Architecture
{code}
The available types are:
* string
* boolean
* long
* double
* date
* binary
* content
* complex
* scalarList
* complexList
Affects Version/s: 5.5
Fix Version/s: 5.6
Assignee: Antoine Taillefer
Summary: Override core io document exporter to generate a XML
aware of property types (was: Override core io document exporter to generate a
nicer XML)
> Override core io document exporter to generate a XML aware of property types
>
>
> Key: NXP-8595
> URL: https://jira.nuxeo.com/browse/NXP-8595
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> It would be nice to have an XML export of documents with a {{type}} attribute
> on each field element.
> This would make the work on the XML easier, for example in the Diff feature
> that compares XML exports.
> Typically what we want is:
> {code:xml}
> http://www.nuxeo.org/ecm/schemas/dublincore/";
> name="dublincore">
> Administrator
>
>
> Administrator
> joe
>
>
> 2011-12-29T11:24:25Z
> description
>
>
> Art
> Architecture
>
>
>
> {code}
> The available types are:
> * string
> * boolean
> * long
> * double
> * date
> * binary
> * content
> * complex
> * scalarList
> * complexList
--
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] Work logged: (NXP-8585) Allow core io document exporter to be overriden
[
https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Antoine Taillefer logged work on NXP-8585:
--
Author: Antoine Taillefer
Created on: 11/01/12 14:25
Start Date: 11/01/12 14:25
Worklog Time Spent: 2 hours
Issue Time Tracking
---
Worklog Id: (was: 27648)
Time Spent: 2 hours
Remaining Estimate: 0 minutes (was: 2 hours)
> Allow core io document exporter to be overriden
> ---
>
> Key: NXP-8585
> URL: https://jira.nuxeo.com/browse/NXP-8585
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 2 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> We need to be able to override the core io document exporter to be able to
> generate a different XML export file.
--
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] Commented: (NXP-8585) Allow core io document exporter to be overriden
[
https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109331#comment-109331
]
Antoine Taillefer commented on NXP-8585:
{{SingleDocumentReader}} and {{ExportedDocumentImpl}} need to have protected
attributes and methods to be overriden.
> Allow core io document exporter to be overriden
> ---
>
> Key: NXP-8585
> URL: https://jira.nuxeo.com/browse/NXP-8585
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.6
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> We need to be able to override the core io document exporter to be able to
> generate a different XML export file.
--
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-8587) Make the diff service configurable with extension points
[
https://jira.nuxeo.com/browse/NXP-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8587:
---
Description:
The {{DocumentDiffService}} should expose extension points to
h5. Configure XMLUnit for the diff, what is currently hard-coded:
{code:java}
protected void configureXMLUnit() {
XMLUnit.setIgnoreWhitespace(true);
XMLUnit.setIgnoreDiffBetweenTextAndCDATA(true);
}
{code}
h5. Configure the diff itself, what is currently hard-coded:
{code:java}
protected void configureDiff(Diff diff) {
diff.overrideDifferenceListener(new IgnoreStructuralDifferenceListener());
diff.overrideElementQualifier(new ElementNameAndAttributeQualifier());
}
{code}
h5. Contribute a "second-level" differ for a given type of property.
The first-level diff detects the document properties that are different between
the 2 docs, for example {{dc:title}}.
For now it also holds the different values on both sides: left and right, for
example: {{{left = My first doc / right = My second doc}}}.
The second-level diff would use the type held by the first-level diff of a
property to call the specific differ for this type on the document's property.
This implies a refactoring of the {{PropertyDiff}} implementations. The
first-level diff no more needs to hold the different values, but the type of
diff and a reference to the property itself (xpath like).
For example a structure like {{{type = "complexList", xpath =
"mySchema:complexListField[1]/complexListItem[2]/stringItem[1]"}}}.
This way to access the second-level diff for a property, the system would just
have to call the appropriate differ contributed for the diff type. If no differ
is associated to the diff type, a fallback is done on the default one.
Example of a contribution of a complexList differ:
{code:xml}
{code}
> Make the diff service configurable with extension points
>
>
> Key: NXP-8587
> URL: https://jira.nuxeo.com/browse/NXP-8587
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The {{DocumentDiffService}} should expose extension points to
> h5. Configure XMLUnit for the diff, what is currently hard-coded:
> {code:java}
> protected void configureXMLUnit() {
> XMLUnit.setIgnoreWhitespace(true);
> XMLUnit.setIgnoreDiffBetweenTextAndCDATA(true);
> }
> {code}
> h5. Configure the diff itself, what is currently hard-coded:
> {code:java}
> protected void configureDiff(Diff diff) {
> diff.overrideDifferenceListener(new IgnoreStructuralDifferenceListener());
>
> diff.overrideElementQualifier(new ElementNameAndAttributeQualifier());
> }
> {code}
> h5. Contribute a "second-level" differ for a given type of property.
> The first-level diff detects the document properties that are different
> between the 2 docs, for example {{dc:title}}.
> For now it also holds the different values on both sides: left and right, for
> example: {{{left = My first doc / right = My second doc}}}.
> The second-level diff would use the type held by the first-level diff of a
> property to call the specific differ for this type on the document's property.
> This implies a refactoring of the {{PropertyDiff}} implementations. The
> first-level diff no more needs to hold the different values, but the type of
> diff and a reference to the property itself (xpath like).
> For example a structure like {{{type = "complexList", xpath =
> "mySchema:complexListField[1]/complexListItem[2]/stringItem[1]"}}}.
> This way to access the second-level diff for a property, the system would
> just have to call the appropriate differ contributed for the diff type. If no
> differ is associated to the diff type, a fallback is done on the default one.
> Example of a contribution of a complexList differ:
> {code:xml}
>
> {code}
--
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-8592) Allow diff between 2 archived versions
[ https://jira.nuxeo.com/browse/NXP-8592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8592: --- Remaining Estimate: 4 hours (was: 1 day) Original Estimate: 4 hours (was: 1 day) > Allow diff between 2 archived versions > -- > > Key: NXP-8592 > URL: https://jira.nuxeo.com/browse/NXP-8592 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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-8588) Use BlobHolder to manage binary content diff
[ https://jira.nuxeo.com/browse/NXP-8588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8588: --- Remaining Estimate: 1 day (was: 2 days) Original Estimate: 1 day (was: 2 days) > Use BlobHolder to manage binary content diff > > > Key: NXP-8588 > URL: https://jira.nuxeo.com/browse/NXP-8588 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
[ https://jira.nuxeo.com/browse/NXP-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8594: --- Remaining Estimate: 3 days (was: 2 days) Original Estimate: 3 days (was: 2 days) > Refactor to take advantage of a nicer XML export and fix remaining bugs > --- > > Key: NXP-8594 > URL: https://jira.nuxeo.com/browse/NXP-8594 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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] Created: (NXP-8598) Addon / marketplace package
Addon / marketplace package --- Key: NXP-8598 URL: https://jira.nuxeo.com/browse/NXP-8598 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Work logged: (NXP-8597) Initial prototype
[
https://jira.nuxeo.com/browse/NXP-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Antoine Taillefer logged work on NXP-8597:
--
Author: Antoine Taillefer
Created on: 09/01/12 01:01
Start Date: 28/12/11 01:00
Worklog Time Spent: 1 week, 2 days, 4 hours
Issue Time Tracking
---
Worklog Id: (was: 27643)
Time Spent: 1 week, 2 days, 4 hours
Remaining Estimate: 0 minutes (was: 1 week)
> Initial prototype
> -
>
> Key: NXP-8597
> URL: https://jira.nuxeo.com/browse/NXP-8597
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: ADDONS_5.6
>
> Original Estimate: 1 week
> Time Spent: 1 week, 2 days, 4 hours
> Remaining Estimate: 0 minutes
>
--
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] Resolved: (NXP-8597) Initial prototype
[ https://jira.nuxeo.com/browse/NXP-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer resolved NXP-8597. Resolution: Fixed Fix Version/s: ADDONS_5.6 > Initial prototype > - > > Key: NXP-8597 > URL: https://jira.nuxeo.com/browse/NXP-8597 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: ADDONS_5.6 > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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-8597) Initial prototype
[ https://jira.nuxeo.com/browse/NXP-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8597: --- Status: Open (was: Triage) > Initial prototype > - > > Key: NXP-8597 > URL: https://jira.nuxeo.com/browse/NXP-8597 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: ADDONS_5.6 > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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] Commented: (NXP-8597) Initial prototype
[ https://jira.nuxeo.com/browse/NXP-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=109119#comment-109119 ] Antoine Taillefer commented on NXP-8597: Prototype available on github: https://github.com/ataillefer/nuxeo-platform-diff > Initial prototype > - > > Key: NXP-8597 > URL: https://jira.nuxeo.com/browse/NXP-8597 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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] Created: (NXP-8597) Initial prototype
Initial prototype - Key: NXP-8597 URL: https://jira.nuxeo.com/browse/NXP-8597 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer Assignee: Antoine Taillefer -- 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-8596) Allow use of layouts and widgets to display the diff result, and write sample widgets
[ https://jira.nuxeo.com/browse/NXP-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8596: --- Remaining Estimate: 4 days (was: 3 days) Original Estimate: 4 days (was: 3 days) > Allow use of layouts and widgets to display the diff result, and write sample > widgets > - > > Key: NXP-8596 > URL: https://jira.nuxeo.com/browse/NXP-8596 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer > Original Estimate: 4 days > Remaining Estimate: 4 days > -- 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] Created: (NXP-8596) Allow use of layouts and widgets to display the diff result, and write sample widgets
Allow use of layouts and widgets to display the diff result, and write sample widgets - Key: NXP-8596 URL: https://jira.nuxeo.com/browse/NXP-8596 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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-8586) Documentation for the diff feature
[ https://jira.nuxeo.com/browse/NXP-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8586: --- Summary: Documentation for the diff feature (was: Document diff feature) > Documentation for the diff feature > -- > > Key: NXP-8586 > URL: https://jira.nuxeo.com/browse/NXP-8586 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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-8595) Override core io document exporter to generate a nicer XML
[ https://jira.nuxeo.com/browse/NXP-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8595: --- Remaining Estimate: 4 hours (was: 4 days) Original Estimate: 4 hours (was: 4 days) > Override core io document exporter to generate a nicer XML > -- > > Key: NXP-8595 > URL: https://jira.nuxeo.com/browse/NXP-8595 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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-8585) Allow core io document exporter to be overriden
[ https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8585: --- Remaining Estimate: 2 hours (was: 4 hours) Original Estimate: 2 hours (was: 4 hours) > Allow core io document exporter to be overriden > --- > > Key: NXP-8585 > URL: https://jira.nuxeo.com/browse/NXP-8585 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Affects Versions: 5.5 >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.6 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > We need to be able to override the core io document exporter to be able to > generate a different XML export file. -- 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] Created: (NXP-8595) Override core io document exporter to generate a nicer XML
Override core io document exporter to generate a nicer XML -- Key: NXP-8595 URL: https://jira.nuxeo.com/browse/NXP-8595 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Created: (NXP-8594) Refactor to take advantage of a nicer XML export and fix remaining bugs
Refactor to take advantage of a nicer XML export and fix remaining bugs --- Key: NXP-8594 URL: https://jira.nuxeo.com/browse/NXP-8594 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Created: (NXP-8593) Allow diff of 2 documents from Worklist
Allow diff of 2 documents from Worklist --- Key: NXP-8593 URL: https://jira.nuxeo.com/browse/NXP-8593 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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-8585) Allow core io document exporter to be overriden
[ https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8585: --- Summary: Allow core io document exporter to be overriden (was: Allow document core io exporter to be overriden) > Allow core io document exporter to be overriden > --- > > Key: NXP-8585 > URL: https://jira.nuxeo.com/browse/NXP-8585 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Affects Versions: 5.5 >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.6 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > We need to be able to override the core io document exporter to be able to > generate a different XML export file. -- 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-8586) Document diff feature
[ https://jira.nuxeo.com/browse/NXP-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8586: --- Summary: Document diff feature (was: Docuent diff feature) > Document diff feature > - > > Key: NXP-8586 > URL: https://jira.nuxeo.com/browse/NXP-8586 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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] Created: (NXP-8592) Allow diff between 2 archived versions
Allow diff between 2 archived versions -- Key: NXP-8592 URL: https://jira.nuxeo.com/browse/NXP-8592 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Created: (NXP-8591) Contribute a binary content differ based on HTML preview
Contribute a binary content differ based on HTML preview Key: NXP-8591 URL: https://jira.nuxeo.com/browse/NXP-8591 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Created: (NXP-8589) Contribute a simple text differ
Contribute a simple text differ --- Key: NXP-8589 URL: https://jira.nuxeo.com/browse/NXP-8589 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Created: (NXP-8590) Contribute an HTML differ
Contribute an HTML differ - Key: NXP-8590 URL: https://jira.nuxeo.com/browse/NXP-8590 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Created: (NXP-8588) Use BlobHolder to manage binary content diff
Use BlobHolder to manage binary content diff Key: NXP-8588 URL: https://jira.nuxeo.com/browse/NXP-8588 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer -- 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] Created: (NXP-8587) Make the diff service configurable with extension points
Make the diff service configurable with extension points Key: NXP-8587 URL: https://jira.nuxeo.com/browse/NXP-8587 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer Assignee: Antoine Taillefer -- 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-8585) Allow document core io exporter to be overriden
[ https://jira.nuxeo.com/browse/NXP-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8585: --- Remaining Estimate: 4 hours Original Estimate: 4 hours > Allow document core io exporter to be overriden > --- > > Key: NXP-8585 > URL: https://jira.nuxeo.com/browse/NXP-8585 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Affects Versions: 5.5 >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.6 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > We need to be able to override the core io document exporter to be able to > generate a different XML export file. -- 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] Created: (NXP-8586) Docuentation
Docuentation Key: NXP-8586 URL: https://jira.nuxeo.com/browse/NXP-8586 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Antoine Taillefer Assignee: Antoine Taillefer -- 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-8586) Docuent diff feature
[ https://jira.nuxeo.com/browse/NXP-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8586: --- Summary: Docuent diff feature (was: Docuentation) > Docuent diff feature > > > Key: NXP-8586 > URL: https://jira.nuxeo.com/browse/NXP-8586 > Project: Nuxeo Enterprise Platform > Issue Type: Sub-task >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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] Created: (NXP-8585) Allow document core io exporter to be overriden
Allow document core io exporter to be overriden --- Key: NXP-8585 URL: https://jira.nuxeo.com/browse/NXP-8585 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Affects Versions: 5.5 Reporter: Antoine Taillefer Assignee: Antoine Taillefer Fix For: 5.6 We need to be able to override the core io document exporter to be able to generate a different XML export file. -- 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: (NXS-883) Login page form is (slightly) broken when using a Studio project with an empty branding
[ https://jira.nuxeo.com/browse/NXS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXS-883: -- Security: (was: Internal) > Login page form is (slightly) broken when using a Studio project with an > empty branding > --- > > Key: NXS-883 > URL: https://jira.nuxeo.com/browse/NXS-883 > Project: Nuxeo Studio > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Antoine Taillefer >Assignee: Anahide Tchertchian > Fix For: Short term backlog > > > What I did: just create a new Branding in Studio without customizing anything > in it. > When refreshing Nuxeo with the Studio project and logging out, I notice that > the login form is slightly broken, see attached screenshot. > I also noticed that if I check "Disable theme branding" in my branding, then > Save and refresh the Studio project in Nuxeo, the problem remains. A server > restart is needed to get rid of it. > I assume that this is due to the default Login box width in Studio (250px), > whereas the .login style is 22em in Nuxeo standard stylesheet. > Maybe the other default values should be checked to be aligned with Nuxeo 5.5 > default theme. -- 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-8080) Use the new a4j namespace URI in every XHTML files
[
https://jira.nuxeo.com/browse/NXP-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8080:
---
Fix Version/s: 5.6
> Use the new a4j namespace URI in every XHTML files
> --
>
> Key: NXP-8080
> URL: https://jira.nuxeo.com/browse/NXP-8080
> Project: Nuxeo Enterprise Platform
> Issue Type: Task
> Components: Web UI
>Affects Versions: 5.5-SNAPSHOT
>Reporter: Antoine Taillefer
> Fix For: 5.6
>
> Attachments: a4j_namespace.log
>
>
> The URI for the a4j: namespace should be the same in every XHTML file.
> At the moment, there is a mix between the old URI
> {{"https://ajax4jsf.dev.java.net/ajax"}} and the new one
> {{"http://richfaces.org/a4j"}} (see http://doc.nuxeo.com/x/-4pH, "Use the new
> a4j namespace"), depending on the xhtml files.
> For example in {{tree_explorer_with_virtual_nav.xhtml}} we have the old one
> and in {{message_banner.xhtml}} the new one.
> That is not a problem as long as we don't use 2 different URIs for a given
> namespace in XHTML files associated to fragment views in the theme. But if
> ever we do (that is how I detected this incoherency), we get the attached
> error.
> To reproduce it, just replace {{"https://ajax4jsf.dev.java.net/ajax"}} by
> {{"http://richfaces.org/a4j"}} in {{user_clipboard.xhtml}} (then you will
> have one of each URIs in 2 separate fragment XHTML views).
--
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-8547) Allowed subtypes are not well hot reloaded
[
https://jira.nuxeo.com/browse/NXP-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8547:
---
Description:
Updating the {{Container types}} list in Studio, for instance from {Workspace,
Folder} to {Workspace}, has no direct effect in the UI, a reboot is needed.
In a strange way, once rebooted, if we put Folder back into the {{Container
types}} list, a simple logout/login works.
was:
Updating the {{Container types}} list, for instance from {Workspace, Folder} to
{Workspace}, has no direct effect in the UI, a reboot is needed.
In a strange way, once rebooted, if we put Folder back into the {{Container
types}} list, a simple logout/login works.
Summary: Allowed subtypes are not well hot reloaded (was: Container
types are not well hot reloaded)
> Allowed subtypes are not well hot reloaded
> --
>
> Key: NXP-8547
> URL: https://jira.nuxeo.com/browse/NXP-8547
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>
> Updating the {{Container types}} list in Studio, for instance from
> {Workspace, Folder} to {Workspace}, has no direct effect in the UI, a reboot
> is needed.
> In a strange way, once rebooted, if we put Folder back into the {{Container
> types}} list, a simple logout/login works.
--
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] Moved: (NXP-8547) Container types are not well hot reloaded
[
https://jira.nuxeo.com/browse/NXP-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer moved NXS-892 to NXP-8547:
Affects Version/s: (was: 2.5)
5.5
Key: NXP-8547 (was: NXS-892)
Project: Nuxeo Enterprise Platform (was: Nuxeo Studio)
> Container types are not well hot reloaded
> -
>
> Key: NXP-8547
> URL: https://jira.nuxeo.com/browse/NXP-8547
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
>Affects Versions: 5.5
>Reporter: Antoine Taillefer
>
> Updating the {{Container types}} list, for instance from {Workspace, Folder}
> to {Workspace}, has no direct effect in the UI, a reboot is needed.
> In a strange way, once rebooted, if we put Folder back into the {{Container
> types}} list, a simple logout/login works.
--
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-8546) Add a diff feature to compare two documents or two versions of a document
[
https://jira.nuxeo.com/browse/NXP-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8546:
---
Attachment: (was: diff_result_sample.pdf)
> Add a diff feature to compare two documents or two versions of a document
> -
>
> Key: NXP-8546
> URL: https://jira.nuxeo.com/browse/NXP-8546
> Project: Nuxeo Enterprise Platform
> Issue Type: User story
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: ADDONS_5.6
>
> Attachments: diff_result_sample.png
>
>
> h2. Use cases
> There a several cases where it makes sense to compare (make a diff of) 2
> documents.
> # *Version diff*: you want to list the modifications between a document and
> one of its archived versions, typically in the case of functional
> specifications.
> # *Publication diff*: you want to list the modifications between a published
> document and its source, typically in the case of a web site page to measure
> the gap between the draft and what is online. In Nuxeo this happens to be the
> same case as the Version diff since the published document is a proxy to a
> version of the document.
> # *Document diff*: you want to list the modifications between a document A
> and a document B, typically in the case of product information documents
> where you may want to compare the product caracteristics such as material /
> price / creation date.
> h2. Approach
> *Comparing (= making a diff of) 2 documents or 2 versions of a document* can
> be seen in a Nuxeo way as *comparing the properties shared by the 2
> documents*.
> - This means that if a comparison is done between two documents of a
> different type, only the schemas in common will be "diffed".
> - The result of the comparison only shows the properties that have been
> updated, or added / deleted in the case of multivalued properties.
> - The comparison should take into account blob-type properties. This is a
> tricky part since:
> ** The diff process depends on the blob mime type, therefore we need to be
> able to define a list of supported types for which the diff is possible and
> for each type to contribute a tool in charge of the diff.
> ** We have to find a nice way of displaying the result of a blob diff, again
> depending on the blob mime type.
> h2. High level User Story
> # Launching a comparison
> #* In the {{History > Archived Versions}} tab I can check versions. If I
> check 2 (and only 2) versions then the {{Compare}} button located under the
> version listing gets enabled.
> #* In the same tab, for each version a button {{Compare to current version}}
> is also available.
> These two first cases cover the *Version diff* use case.
> #* In a content view if I check 2 (and only 2) documents then the {{Compare}}
> button located near the {{Copy}}, {{Paste}}, ... buttons gets enabled.
> This approach is nice for comparing 2 documents living in the same container
> or that are part of a search result, but we also need to be able to compare 2
> documents lcoated in separate containers.
> #* So if I have added 2 (and only 2) documents to my worklist, then a
> {{Compare}} action appears in the worklist actions.
> These two last cases cover the *Publication diff* and *Document diff* use
> cases.
> # Viewing the diff result in the UI
> #* The diff result is displayed in the right panel, as a table with 2
> columns: document A / document B, and as many lines as different properties.
> #* By default, properties are grouped by schemas. It could be nice to have a
> layout / widget system to have a full control on the diff result display.
> #* Rendering of a blob-type property diff still has to be defined.
> #* Attached screenshot gives an example of the result of a diff between 2
> documents, for most property types (simple, complex, complex list).
> A color code is used to better distinguish updated / added / deleted values:
> #** red for left document
> #** green for right document
> #* The add/delete notions make sense in the version diff case.
> In the document diff case, we can consider that we are comparing the right
> document with the left document which is the reference.
> Therefore a value existing in the right doc and not in the left one will be
> considered as "added" in comparison with the reference doc => green means
> added.
> Conversely for the "deleted" case: red means "deleted".
> # PDF export
> #* I want to make a PDF export of a diff result.
> #* I may also want to automatiucally store the generated PDF in Nuxeo?
--
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.nuxe
[JIRA] Updated: (NXP-8546) Add a diff feature to compare two documents or two versions of a document
[
https://jira.nuxeo.com/browse/NXP-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8546:
---
Attachment: diff_result_sample.png
> Add a diff feature to compare two documents or two versions of a document
> -
>
> Key: NXP-8546
> URL: https://jira.nuxeo.com/browse/NXP-8546
> Project: Nuxeo Enterprise Platform
> Issue Type: User story
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: ADDONS_5.6
>
> Attachments: diff_result_sample.png
>
>
> h2. Use cases
> There a several cases where it makes sense to compare (make a diff of) 2
> documents.
> # *Version diff*: you want to list the modifications between a document and
> one of its archived versions, typically in the case of functional
> specifications.
> # *Publication diff*: you want to list the modifications between a published
> document and its source, typically in the case of a web site page to measure
> the gap between the draft and what is online. In Nuxeo this happens to be the
> same case as the Version diff since the published document is a proxy to a
> version of the document.
> # *Document diff*: you want to list the modifications between a document A
> and a document B, typically in the case of product information documents
> where you may want to compare the product caracteristics such as material /
> price / creation date.
> h2. Approach
> *Comparing (= making a diff of) 2 documents or 2 versions of a document* can
> be seen in a Nuxeo way as *comparing the properties shared by the 2
> documents*.
> - This means that if a comparison is done between two documents of a
> different type, only the schemas in common will be "diffed".
> - The result of the comparison only shows the properties that have been
> updated, or added / deleted in the case of multivalued properties.
> - The comparison should take into account blob-type properties. This is a
> tricky part since:
> ** The diff process depends on the blob mime type, therefore we need to be
> able to define a list of supported types for which the diff is possible and
> for each type to contribute a tool in charge of the diff.
> ** We have to find a nice way of displaying the result of a blob diff, again
> depending on the blob mime type.
> h2. High level User Story
> # Launching a comparison
> #* In the {{History > Archived Versions}} tab I can check versions. If I
> check 2 (and only 2) versions then the {{Compare}} button located under the
> version listing gets enabled.
> #* In the same tab, for each version a button {{Compare to current version}}
> is also available.
> These two first cases cover the *Version diff* use case.
> #* In a content view if I check 2 (and only 2) documents then the {{Compare}}
> button located near the {{Copy}}, {{Paste}}, ... buttons gets enabled.
> This approach is nice for comparing 2 documents living in the same container
> or that are part of a search result, but we also need to be able to compare 2
> documents lcoated in separate containers.
> #* So if I have added 2 (and only 2) documents to my worklist, then a
> {{Compare}} action appears in the worklist actions.
> These two last cases cover the *Publication diff* and *Document diff* use
> cases.
> # Viewing the diff result in the UI
> #* The diff result is displayed in the right panel, as a table with 2
> columns: document A / document B, and as many lines as different properties.
> #* By default, properties are grouped by schemas. It could be nice to have a
> layout / widget system to have a full control on the diff result display.
> #* Rendering of a blob-type property diff still has to be defined.
> #* Attached screenshot gives an example of the result of a diff between 2
> documents, for most property types (simple, complex, complex list).
> A color code is used to better distinguish updated / added / deleted values:
> #** red for left document
> #** green for right document
> #* The add/delete notions make sense in the version diff case.
> In the document diff case, we can consider that we are comparing the right
> document with the left document which is the reference.
> Therefore a value existing in the right doc and not in the left one will be
> considered as "added" in comparison with the reference doc => green means
> added.
> Conversely for the "deleted" case: red means "deleted".
> # PDF export
> #* I want to make a PDF export of a diff result.
> #* I may also want to automatiucally store the generated PDF in Nuxeo?
--
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/mailm
[JIRA] Updated: (NXP-8546) Add a diff feature to compare two documents or two versions of a document
[
https://jira.nuxeo.com/browse/NXP-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8546:
---
Attachment: diff_result_sample.pdf
> Add a diff feature to compare two documents or two versions of a document
> -
>
> Key: NXP-8546
> URL: https://jira.nuxeo.com/browse/NXP-8546
> Project: Nuxeo Enterprise Platform
> Issue Type: User story
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: ADDONS_5.6
>
> Attachments: diff_result_sample.pdf
>
>
> h2. Use cases
> There a several cases where it makes sense to compare (make a diff of) 2
> documents.
> # *Version diff*: you want to list the modifications between a document and
> one of its archived versions, typically in the case of functional
> specifications.
> # *Publication diff*: you want to list the modifications between a published
> document and its source, typically in the case of a web site page to measure
> the gap between the draft and what is online. In Nuxeo this happens to be the
> same case as the Version diff since the published document is a proxy to a
> version of the document.
> # *Document diff*: you want to list the modifications between a document A
> and a document B, typically in the case of product information documents
> where you may want to compare the product caracteristics such as material /
> price / creation date.
> h2. Approach
> *Comparing (= making a diff of) 2 documents or 2 versions of a document* can
> be seen in a Nuxeo way as *comparing the properties shared by the 2
> documents*.
> - This means that if a comparison is done between two documents of a
> different type, only the schemas in common will be "diffed".
> - The result of the comparison only shows the properties that have been
> updated, or added / deleted in the case of multivalued properties.
> - The comparison should take into account blob-type properties. This is a
> tricky part since:
> ** The diff process depends on the blob mime type, therefore we need to be
> able to define a list of supported types for which the diff is possible and
> for each type to contribute a tool in charge of the diff.
> ** We have to find a nice way of displaying the result of a blob diff, again
> depending on the blob mime type.
> h2. High level User Story
> # Launching a comparison
> #* In the {{History > Archived Versions}} tab I can check versions. If I
> check 2 (and only 2) versions then the {{Compare}} button located under the
> version listing gets enabled.
> #* In the same tab, for each version a button {{Compare to current version}}
> is also available.
> These two first cases cover the *Version diff* use case.
> #* In a content view if I check 2 (and only 2) documents then the {{Compare}}
> button located near the {{Copy}}, {{Paste}}, ... buttons gets enabled.
> This approach is nice for comparing 2 documents living in the same container
> or that are part of a search result, but we also need to be able to compare 2
> documents lcoated in separate containers.
> #* So if I have added 2 (and only 2) documents to my worklist, then a
> {{Compare}} action appears in the worklist actions.
> These two last cases cover the *Publication diff* and *Document diff* use
> cases.
> # Viewing the diff result in the UI
> #* The diff result is displayed in the right panel, as a table with 2
> columns: document A / document B, and as many lines as different properties.
> #* By default, properties are grouped by schemas. It could be nice to have a
> layout / widget system to have a full control on the diff result display.
> #* Rendering of a blob-type property diff still has to be defined.
> #* Attached screenshot gives an example of the result of a diff between 2
> documents, for most property types (simple, complex, complex list).
> A color code is used to better distinguish updated / added / deleted values:
> #** red for left document
> #** green for right document
> #* The add/delete notions make sense in the version diff case.
> In the document diff case, we can consider that we are comparing the right
> document with the left document which is the reference.
> Therefore a value existing in the right doc and not in the left one will be
> considered as "added" in comparison with the reference doc => green means
> added.
> Conversely for the "deleted" case: red means "deleted".
> # PDF export
> #* I want to make a PDF export of a diff result.
> #* I may also want to automatiucally store the generated PDF in Nuxeo?
--
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/mailm
[JIRA] Updated: (NXP-8546) Add a diff feature to compare two documents or two versions of a document
[
https://jira.nuxeo.com/browse/NXP-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8546:
---
Description:
h2. Use cases
There a several cases where it makes sense to compare (make a diff of) 2
documents.
# *Version diff*: you want to list the modifications between a document and one
of its archived versions, typically in the case of functional specifications.
# *Publication diff*: you want to list the modifications between a published
document and its source, typically in the case of a web site page to measure
the gap between the draft and what is online. In Nuxeo this happens to be the
same case as the Version diff since the published document is a proxy to a
version of the document.
# *Document diff*: you want to list the modifications between a document A and
a document B, typically in the case of product information documents where you
may want to compare the product caracteristics such as material / price /
creation date.
h2. Approach
*Comparing (= making a diff of) 2 documents or 2 versions of a document* can be
seen in a Nuxeo way as *comparing the properties shared by the 2 documents*.
- This means that if a comparison is done between two documents of a different
type, only the schemas in common will be "diffed".
- The result of the comparison only shows the properties that have been
updated, or added / deleted in the case of multivalued properties.
- The comparison should take into account blob-type properties. This is a
tricky part since:
** The diff process depends on the blob mime type, therefore we need to be able
to define a list of supported types for which the diff is possible and for each
type to contribute a tool in charge of the diff.
** We have to find a nice way of displaying the result of a blob diff, again
depending on the blob mime type.
h2. High level User Story
# Launching a comparison
#* In the {{History > Archived Versions}} tab I can check versions. If I check
2 (and only 2) versions then the {{Compare}} button located under the version
listing gets enabled.
#* In the same tab, for each version a button {{Compare to current version}} is
also available.
These two first cases cover the *Version diff* use case.
#* In a content view if I check 2 (and only 2) documents then the {{Compare}}
button located near the {{Copy}}, {{Paste}}, ... buttons gets enabled.
This approach is nice for comparing 2 documents living in the same container or
that are part of a search result, but we also need to be able to compare 2
documents lcoated in separate containers.
#* So if I have added 2 (and only 2) documents to my worklist, then a
{{Compare}} action appears in the worklist actions.
These two last cases cover the *Publication diff* and *Document diff* use cases.
# Viewing the diff result in the UI
#* The diff result is displayed in the right panel, as a table with 2 columns:
document A / document B, and as many lines as different properties.
#* By default, properties are grouped by schemas. It could be nice to have a
layout / widget system to have a full control on the diff result display.
#* Rendering of a blob-type property diff still has to be defined.
#* Attached screenshot gives an example of the result of a diff between 2
documents, for most property types (simple, complex, complex list).
A color code is used to better distinguish updated / added / deleted values:
#** red for left document
#** green for right document
#* The add/delete notions make sense in the version diff case.
In the document diff case, we can consider that we are comparing the right
document with the left document which is the reference.
Therefore a value existing in the right doc and not in the left one will be
considered as "added" in comparison with the reference doc => green means added.
Conversely for the "deleted" case: red means "deleted".
# PDF export
#* I want to make a PDF export of a diff result.
#* I may also want to automatiucally store the generated PDF in Nuxeo?
was:
h2. Use cases
There a several cases where it makes sense to compare (make a diff of) 2
documents.
# *Version diff*: you want to list the modifications between a document and one
of its archived versions, typically in the case of functional specifications.
# *Publication diff*: you want to list the modifications between a published
document and its source, typically in the case of a web site page to measure
the gap between the draft and what is online. In Nuxeo this happens to be the
same case as the Version diff since the published document is a proxy to a
version of the document.
# *Document diff*: you want to list the modifications between a document A and
a document B, typically in the case of product information documents where you
may want to compare the product caracteristics such as material / price /
creation date.
h2. Approach
*Comparing (= making a diff of) 2 documents or 2 ve
[JIRA] Created: (NXP-8546) Add a diff feature to compare two documents or two versions of a document
Add a diff feature to compare two documents or two versions of a document
-
Key: NXP-8546
URL: https://jira.nuxeo.com/browse/NXP-8546
Project: Nuxeo Enterprise Platform
Issue Type: User story
Reporter: Antoine Taillefer
Assignee: Antoine Taillefer
Fix For: ADDONS_5.6
h2. Use cases
There a several cases where it makes sense to compare (make a diff of) 2
documents.
# *Version diff*: you want to list the modifications between a document and one
of its archived versions, typically in the case of functional specifications.
# *Publication diff*: you want to list the modifications between a published
document and its source, typically in the case of a web site page to measure
the gap between the draft and what is online. In Nuxeo this happens to be the
same case as the Version diff since the published document is a proxy to a
version of the document.
# *Document diff*: you want to list the modifications between a document A and
a document B, typically in the case of product information documents where you
may want to compare the product caracteristics such as material / price /
creation date.
h2. Approach
*Comparing (= making a diff of) 2 documents or 2 versions of a document* can be
seen in a Nuxeo way as *comparing the properties shared by the 2 documents*.
- This means that if a comparison is done between two documents of a different
type, only the schemas in common will be "diffed".
- The result of the comparison only shows the properties that have been
updated, or added / deleted in the case of multivalued properties.
- The comparison should take into account blob-type properties. This is a
tricky part since:
** The diff process depends on the blob mime type, therefore we need to be able
to define a list of supported types for which the diff is possible and for each
type to contribute a tool in charge of the diff.
** We have to find a nice way of displaying the result of a blob diff, again
depending on the blob mime type.
h2. High level User Story
# Launching a comparison
#* In the {{History > Archived Versions}} tab I can check versions. If I check
2 (and only 2) versions then the {{Compare}} button located under the version
listing gets enabled.
#* In the same tab, for each version a button {{Compare to current version}} is
also available.
These two first cases cover the *Version diff* use case.
#* In a content view if I check 2 (and only 2) documents then the {{Compare}}
button located near the {{Copy}}, {{Paste}}, ... buttons gets enabled.
This approach is nice for comparing 2 documents living in the same container or
that are part of a search result, but we also need to be able to compare 2
documents lcoated in separate containers.
#* So if I have added 2 (and only 2) documents to my worklist, then a
{{Compare}} action appears in the worklist actions.
These two last cases cover the *Publication diff* and *Document diff* use cases.
# Viewing the diff result in the UI
#* The diff result is displayed in the right panel, as a table with 2 columns:
document A / document B, and as many lines as different properties.
#* By default, properties are grouped by schemas. It could be nice to have a
layout / widget system to have a full control on the diff result display.
#* Rendering of a blob-type property diff still has to be defined.
#* Attached screenshot gives an example of the result of a diff between 2
documents, for most property types (simple, list, complex, complex list).
A color code is used to better distinguish updated / added / deleted values:
#** red for left document
#** green for right document
#* The add/delete notions make sense in the version diff case.
In the document diff case, we can consider that we are comparing the right
document with the left document which is the reference.
Therefore a value existing in the right doc and not in the left one will be
considered as "added" in comparison with the reference doc => green means added.
Conversely for the "deleted" case: red means "deleted".
# PDF export
#* I want to make a PDF export of a diff result.
#* I may also want to automatiucally store the generated PDF in Nuxeo?
--
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] Created: (NXS-893) Uninstalling the "Nuxeo DM Default configuration [EASY]" Application Template makes the Domain type unavailable
Uninstalling the "Nuxeo DM Default configuration [EASY]" Application Template
makes the Domain type unavailable
---
Key: NXS-893
URL: https://jira.nuxeo.com/browse/NXS-893
Project: Nuxeo Studio
Issue Type: Bug
Affects Versions: 2.5
Reporter: Antoine Taillefer
After removing the "Nuxeo DM Default configuration [EASY]" Application Template
, when going back to {{Document Management}}, Nuxeo crashes because it doesn't
find the Domain type, so the {{/default-domain}} document cannot be found
either. A restart solves the problem.
It seems like removing this template doesn't take into account the fact that it
overrides some doc types.
--
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] Created: (NXS-892) Container types are not well hot reloaded
Container types are not well hot reloaded
-
Key: NXS-892
URL: https://jira.nuxeo.com/browse/NXS-892
Project: Nuxeo Studio
Issue Type: Bug
Affects Versions: 2.5
Reporter: Antoine Taillefer
Updating the {{Container types}} list, for instance from {Workspace, Folder} to
{Workspace}, has no direct effect in the UI, a reboot is needed.
In a strange way, once rebooted, if we put Folder back into the {{Container
types}} list, a simple logout/login works.
--
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] Created: (NXS-891) Have a "Disable feature" checkbox on every Studio feature
Have a "Disable feature" checkbox on every Studio feature - Key: NXS-891 URL: https://jira.nuxeo.com/browse/NXS-891 Project: Nuxeo Studio Issue Type: New Feature Affects Versions: 2.5 Reporter: Antoine Taillefer It would be nice to have a "Disable feature" checkbox en every Studio feature (especially Documents, Structure Templates, User actions, Vocabulaires, ...) to be able to keep a feature in the Studio project without necessarily having it enabled in Nuxeo. This already exists for the branding with the "Disable theme branding" checkbox. -- 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-8136) Bad labels in the "My Tasks" gadget for tasks migrated from JBPM
[ https://jira.nuxeo.com/browse/NXP-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8136: --- Status: Open (was: Triage) > Bad labels in the "My Tasks" gadget for tasks migrated from JBPM > > > Key: NXP-8136 > URL: https://jira.nuxeo.com/browse/NXP-8136 > Project: Nuxeo Enterprise Platform > Issue Type: Bug > Components: Dashboard / OpenSocial >Affects Versions: 5.5-SNAPSHOT >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.5 > > Attachments: task_labels.png > > > In the "My Tasks" dashboard gadget, labels for the tasks that have been > migrated from JBPM through the TaskMigrationRunner are bad. > For example, in the attached screenshot, we should have: > * "Document à publier" instead of > "org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory" > * "Modérer le document" instead of "moderate" -- 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] Resolved: (NXP-8136) Bad labels in the "My Tasks" gadget for tasks migrated from JBPM
[ https://jira.nuxeo.com/browse/NXP-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer resolved NXP-8136. Resolution: Fixed Fix Version/s: 5.5 > Bad labels in the "My Tasks" gadget for tasks migrated from JBPM > > > Key: NXP-8136 > URL: https://jira.nuxeo.com/browse/NXP-8136 > Project: Nuxeo Enterprise Platform > Issue Type: Bug > Components: Dashboard / OpenSocial >Affects Versions: 5.5-SNAPSHOT >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Fix For: 5.5 > > Attachments: task_labels.png > > > In the "My Tasks" dashboard gadget, labels for the tasks that have been > migrated from JBPM through the TaskMigrationRunner are bad. > For example, in the attached screenshot, we should have: > * "Document à publier" instead of > "org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory" > * "Modérer le document" instead of "moderate" -- 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] Commented: (NXP-8136) Bad labels in the "My Tasks" gadget for tasks migrated from JBPM
[
https://jira.nuxeo.com/browse/NXP-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=107747#comment-107747
]
Antoine Taillefer commented on NXP-8136:
Don't set {{createdFromCreateTaskOperation}} variable when a migrating comment
task (only needed for tasks created by CreateTask operation).
http://hg.nuxeo.org/nuxeo/nuxeo-features/rev/d15192ae2c6e
> Bad labels in the "My Tasks" gadget for tasks migrated from JBPM
>
>
> Key: NXP-8136
> URL: https://jira.nuxeo.com/browse/NXP-8136
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Dashboard / OpenSocial
>Affects Versions: 5.5-SNAPSHOT
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
> Fix For: 5.5
>
> Attachments: task_labels.png
>
>
> In the "My Tasks" dashboard gadget, labels for the tasks that have been
> migrated from JBPM through the TaskMigrationRunner are bad.
> For example, in the attached screenshot, we should have:
> * "Document à publier" instead of
> "org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory"
> * "Modérer le document" instead of "moderate"
--
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] Created: (NXP-8139) Refactor packages named *.jbpm* in nuxeo-platform-publisher-task and nuxeo-platform-task-web
Refactor packages named *.jbpm* in nuxeo-platform-publisher-task and
nuxeo-platform-task-web
Key: NXP-8139
URL: https://jira.nuxeo.com/browse/NXP-8139
Project: Nuxeo Enterprise Platform
Issue Type: Clean up
Components: Publishing
Affects Versions: 5.5-SNAPSHOT
Reporter: Antoine Taillefer
Assignee: Thierry Delprat
In *{{nuxeo-platform-publisher-task}}*, the
{{org.nuxeo.ecm.platform.publisher.jbpm}} package should be refactored to
{{org.nuxeo.ecm.platform.publisher.task}}.
In *{{nuxeo-platform-task-web}}*, the
{{org.nuxeo.ecm.platform.jbpm.web}} package should be refactored to
{{org.nuxeo.ecm.platform.task.web}}.
Maybe we should check there are no occurrences of *.jbpm* in other bundles.
--
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-8138) "Pending requests" gadget is not updated when a forum post moderation task has been done
[ https://jira.nuxeo.com/browse/NXP-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8138: --- Attachment: moderated_forum_thread.png waiting_for_forum_post_moderation.png > "Pending requests" gadget is not updated when a forum post moderation task > has been done > > > Key: NXP-8138 > URL: https://jira.nuxeo.com/browse/NXP-8138 > Project: Nuxeo Enterprise Platform > Issue Type: Bug > Components: Dashboard / OpenSocial >Affects Versions: 5.5-SNAPSHOT >Reporter: Antoine Taillefer > Fix For: 5.6 > > Attachments: moderated_forum_thread.png, > waiting_for_forum_post_moderation.png > > > When a forum post moderation task is done (approved or rejected), the user > author of the post has a remaining request in his "Pending requests" gadget. > It should disappear since the request has been processed. > Attached screenshots shows such a pending request whereas all posts have been > moderated in the Forum thread. -- 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] Created: (NXP-8138) "Pending requests" gadget is not updated when a forum post moderation task has been done
"Pending requests" gadget is not updated when a forum post moderation task has been done Key: NXP-8138 URL: https://jira.nuxeo.com/browse/NXP-8138 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Dashboard / OpenSocial Affects Versions: 5.5-SNAPSHOT Reporter: Antoine Taillefer Fix For: 5.6 Attachments: moderated_forum_thread.png, waiting_for_forum_post_moderation.png When a forum post moderation task is done (approved or rejected), the user author of the post has a remaining request in his "Pending requests" gadget. It should disappear since the request has been processed. Attached screenshots shows such a pending request whereas all posts have been moderated in the Forum thread. -- 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] Created: (NXP-8137) JBPM migrated tasks could maybe be canceled and not only suspended.
JBPM migrated tasks could maybe be canceled and not only suspended.
---
Key: NXP-8137
URL: https://jira.nuxeo.com/browse/NXP-8137
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Components: Workflow
Affects Versions: 5.5-SNAPSHOT
Reporter: Antoine Taillefer
In {{TaskMigrationRunner#migrateGenericTask}}, we suspend the JBPM task
instance once it has been migrated:
{code:java}
ti.suspend();
{code}
Maybe is should even be canceled to keep it in a "cleaner" state since it is
not supposed to be used anymore:
{code:java}
ti.cancel();
{code}
--
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-8136) Bad labels in the "My Tasks" gadget for tasks migrated from JBPM
[ https://jira.nuxeo.com/browse/NXP-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8136: --- Attachment: task_labels.png > Bad labels in the "My Tasks" gadget for tasks migrated from JBPM > > > Key: NXP-8136 > URL: https://jira.nuxeo.com/browse/NXP-8136 > Project: Nuxeo Enterprise Platform > Issue Type: Bug > Components: Dashboard / OpenSocial >Affects Versions: 5.5-SNAPSHOT >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer > Attachments: task_labels.png > > > In the "My Tasks" dashboard gadget, labels for the tasks that have been > migrated from JBPM through the TaskMigrationRunner are bad. > For example, in the attached screenshot, we should have: > * "Document à publier" instead of > "org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory" > * "Modérer le document" instead of "moderate" -- 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] Created: (NXP-8136) Bad labels in the "My Tasks" gadget for tasks migrated from JBPM
Bad labels in the "My Tasks" gadget for tasks migrated from JBPM Key: NXP-8136 URL: https://jira.nuxeo.com/browse/NXP-8136 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Dashboard / OpenSocial Affects Versions: 5.5-SNAPSHOT Reporter: Antoine Taillefer Assignee: Antoine Taillefer In the "My Tasks" dashboard gadget, labels for the tasks that have been migrated from JBPM through the TaskMigrationRunner are bad. For example, in the attached screenshot, we should have: * "Document à publier" instead of "org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory" * "Modérer le document" instead of "moderate" -- 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] Resolved: (NXP-8094) User who submits the document can approve publishing
[ https://jira.nuxeo.com/browse/NXP-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer resolved NXP-8094. Resolution: Fixed > User who submits the document can approve publishing > > > Key: NXP-8094 > URL: https://jira.nuxeo.com/browse/NXP-8094 > Project: Nuxeo Enterprise Platform > Issue Type: Bug > Components: Publishing > Environment: 5.5 RC 1 DM only >Reporter: Solen Guitter >Assignee: Antoine Taillefer >Priority: Critical > Fix For: 5.5 > > > A user with Read right can ask for publishing and then approve publishing. -- 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] Work started: (NXP-8094) User who submits the document can approve publishing
[ https://jira.nuxeo.com/browse/NXP-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NXP-8094 started by Antoine Taillefer. > User who submits the document can approve publishing > > > Key: NXP-8094 > URL: https://jira.nuxeo.com/browse/NXP-8094 > Project: Nuxeo Enterprise Platform > Issue Type: Bug > Components: Publishing > Environment: 5.5 RC 1 DM only >Reporter: Solen Guitter >Assignee: Antoine Taillefer >Priority: Critical > Fix For: 5.5 > > > A user with Read right can ask for publishing and then approve publishing. -- 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] Commented: (NXP-8094) User who submits the document can approve publishing
[ https://jira.nuxeo.com/browse/NXP-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=107739#comment-107739 ] Antoine Taillefer commented on NXP-8094: OK issue is fixed, now only the users to whom the "Approve publicaton" task is assigned can approve or reject publishing. Problem was due to a bad query to retrieve the current user's tasks, and to other problems in the task service, fixed in NXP-8126. > User who submits the document can approve publishing > > > Key: NXP-8094 > URL: https://jira.nuxeo.com/browse/NXP-8094 > Project: Nuxeo Enterprise Platform > Issue Type: Bug > Components: Publishing > Environment: 5.5 RC 1 DM only >Reporter: Solen Guitter >Assignee: Antoine Taillefer >Priority: Critical > Fix For: 5.5 > > > A user with Read right can ask for publishing and then approve publishing. -- 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] Resolved: (NXP-8125) Display only current user tasks in dashboard, instead of all tasks
[ https://jira.nuxeo.com/browse/NXP-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer resolved NXP-8125. Resolution: Fixed > Display only current user tasks in dashboard, instead of all tasks > -- > > Key: NXP-8125 > URL: https://jira.nuxeo.com/browse/NXP-8125 > Project: Nuxeo Enterprise Platform > Issue Type: Bug >Affects Versions: 5.5-SNAPSHOT >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer >Priority: Major > Fix For: 5.5 > > > In the "Task" dashboard gadget, all tasks are displayed, instead of current > user ones. -- 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-8125) Display only current user tasks in dashboard, instead of all tasks
[ https://jira.nuxeo.com/browse/NXP-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Taillefer updated NXP-8125: --- Status: Open (was: Triage) > Display only current user tasks in dashboard, instead of all tasks > -- > > Key: NXP-8125 > URL: https://jira.nuxeo.com/browse/NXP-8125 > Project: Nuxeo Enterprise Platform > Issue Type: Bug >Affects Versions: 5.5-SNAPSHOT >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer >Priority: Major > Fix For: 5.5 > > > In the "Task" dashboard gadget, all tasks are displayed, instead of current > user ones. -- 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] Commented: (NXP-8125) Display only current user tasks in dashboard, instead of all tasks
[ https://jira.nuxeo.com/browse/NXP-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=107738#comment-107738 ] Antoine Taillefer commented on NXP-8125: First commit: http://hg.nuxeo.org/nuxeo/nuxeo-features/rev/038c40cbe8b7 > Display only current user tasks in dashboard, instead of all tasks > -- > > Key: NXP-8125 > URL: https://jira.nuxeo.com/browse/NXP-8125 > Project: Nuxeo Enterprise Platform > Issue Type: Bug >Affects Versions: 5.5-SNAPSHOT >Reporter: Antoine Taillefer >Assignee: Antoine Taillefer >Priority: Major > Fix For: 5.5 > > > In the "Task" dashboard gadget, all tasks are displayed, instead of current > user ones. -- 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] Resolved: (NXP-8126) Use current user to filter validation tasks in publication workflow.
[
https://jira.nuxeo.com/browse/NXP-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer resolved NXP-8126.
Resolution: Fixed
> Use current user to filter validation tasks in publication workflow.
>
>
> Key: NXP-8126
> URL: https://jira.nuxeo.com/browse/NXP-8126
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Publishing
>Affects Versions: 5.5-SNAPSHOT
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
>Priority: Major
> Fix For: 5.5
>
>
> We need to use the current user to filter the validaton tasks in publication
> workflow.
> NXP-8094 is a side effect of this bug.
> Indeed, if a user submits a doc to publication, as the validation tasks are
> not filtered with the current user, the CoreProxyWithWorkflowFactory
> considers that this user has validation tasks (since a task actually exists,
> but assigned to Administrator), so the "Publish/Reject" buttons are displayed
> in the summary tab of the proxy.
> See {{}} in
> {{publication_widget_template.xhtml}}.
--
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-8126) Use current user to filter validation tasks in publication workflow.
[
https://jira.nuxeo.com/browse/NXP-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Taillefer updated NXP-8126:
---
Status: Open (was: Triage)
> Use current user to filter validation tasks in publication workflow.
>
>
> Key: NXP-8126
> URL: https://jira.nuxeo.com/browse/NXP-8126
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Publishing
>Affects Versions: 5.5-SNAPSHOT
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
>Priority: Major
> Fix For: 5.5
>
>
> We need to use the current user to filter the validaton tasks in publication
> workflow.
> NXP-8094 is a side effect of this bug.
> Indeed, if a user submits a doc to publication, as the validation tasks are
> not filtered with the current user, the CoreProxyWithWorkflowFactory
> considers that this user has validation tasks (since a task actually exists,
> but assigned to Administrator), so the "Publish/Reject" buttons are displayed
> in the summary tab of the proxy.
> See {{}} in
> {{publication_widget_template.xhtml}}.
--
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] Commented: (NXP-8126) Use current user to filter validation tasks in publication workflow.
[
https://jira.nuxeo.com/browse/NXP-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=107736#comment-107736
]
Antoine Taillefer commented on NXP-8126:
First commit is http://hg.nuxeo.org/nuxeo/nuxeo-features/rev/038c40cbe8b7
> Use current user to filter validation tasks in publication workflow.
>
>
> Key: NXP-8126
> URL: https://jira.nuxeo.com/browse/NXP-8126
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Publishing
>Affects Versions: 5.5-SNAPSHOT
>Reporter: Antoine Taillefer
>Assignee: Antoine Taillefer
>Priority: Major
> Fix For: 5.5
>
>
> We need to use the current user to filter the validaton tasks in publication
> workflow.
> NXP-8094 is a side effect of this bug.
> Indeed, if a user submits a doc to publication, as the validation tasks are
> not filtered with the current user, the CoreProxyWithWorkflowFactory
> considers that this user has validation tasks (since a task actually exists,
> but assigned to Administrator), so the "Publish/Reject" buttons are displayed
> in the summary tab of the proxy.
> See {{}} in
> {{publication_widget_template.xhtml}}.
--
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] Created: (NXP-8126) Use current user to filter validation tasks in publication workflow.
Use current user to filter validation tasks in publication workflow.
Key: NXP-8126
URL: https://jira.nuxeo.com/browse/NXP-8126
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Publishing
Affects Versions: 5.5-SNAPSHOT
Reporter: Antoine Taillefer
Assignee: Antoine Taillefer
Priority: Major
Fix For: 5.5
We need to use the current user to filter the validaton tasks in publication
workflow.
NXP-8094 is a side effect of this bug.
Indeed, if a user submits a doc to publication, as the validation tasks are not
filtered with the current user, the CoreProxyWithWorkflowFactory considers that
this user has validation tasks (since a task actually exists, but assigned to
Administrator), so the "Publish/Reject" buttons are displayed in the summary
tab of the proxy.
See {{}} in
{{publication_widget_template.xhtml}}.
--
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
