date:20120103

Nuxeo platform imaging windows problems
---

 Key: NXP-8545
 URL: https://jira.nuxeo.com/browse/NXP-8545
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: DAM
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


Errors are found when cropping, resizing, converting and rotating pictures (dam 
importer).

--
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-8545) Nuxeo platform imaging windows problems


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

Vladimir Pasquier updated NXP-8545:
---

Status: Open  (was: Triage)

 Nuxeo platform imaging windows problems
 ---

 Key: NXP-8545
 URL: https://jira.nuxeo.com/browse/NXP-8545
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: DAM
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


 Errors are found when cropping, resizing, converting and rotating pictures 
 (dam importer).

--
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-8545) Nuxeo platform imaging windows problems


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

Vladimir Pasquier resolved NXP-8545.


Resolution: Fixed

 Nuxeo platform imaging windows problems
 ---

 Key: NXP-8545
 URL: https://jira.nuxeo.com/browse/NXP-8545
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: DAM
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


 Errors are found when cropping, resizing, converting and rotating pictures 
 (dam importer).

--
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-8545) Nuxeo platform imaging windows problems


[ 
https://jira.nuxeo.com/browse/NXP-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108750#comment-108750
 ] 

Vladimir Pasquier commented on NXP-8545:


The way to execute image magick commands on a magnitude picture implies to 
add [0] to the source file.
But:
- the java runtime command execution (Runtime#exec) show parameter errors if 
image title contains white spaces.

 Nuxeo platform imaging windows problems
 ---

 Key: NXP-8545
 URL: https://jira.nuxeo.com/browse/NXP-8545
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: DAM
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


 Errors are found when cropping, resizing, converting and rotating pictures 
 (dam importer).

--
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-898) Operation Online help crash

2012-01-03 Thread Pivotal Integration (JIRA NUXEO)

Operation Online help crash
---

 Key: NXS-898
 URL: https://jira.nuxeo.com/browse/NXS-898
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Pivotal Integration


- I click on Automation  Automation Chain  New
- I expand the Fetch Context exposed into the chain
- I click on the See Online Help button
Problem
- The page open a new window with this folioing url

http://explorer.nuxeo.org/nuxeo/site/distribution/Nuxeo%20DM-5.5/viewOperation/Context.FetchDocument

= Nuxeo DM 5.5 ditribtion not present

--
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-8226) Fix Social Collaboration Selenium tests


[ 
https://jira.nuxeo.com/browse/NXP-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108757#comment-108757
 ] 

Thomas Roger commented on NXP-8226:
---

Rename test files (problem with case)
https://github.com/nuxeo/nuxeo-distribution/commit/73393d23dfb9c3045f882926971f182c9ceb5ce1

 Fix Social Collaboration Selenium tests
 ---

 Key: NXP-8226
 URL: https://jira.nuxeo.com/browse/NXP-8226
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
  Components: Social Collaboration
Reporter: Thomas Roger
Assignee: Thomas Roger
 Fix For: 5.5.x

  Time Spent: 5 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] Updated: (NXBT-348) Improve CI and Testing framework

2012-01-03 Thread Thierry Delprat (JIRA NUXEO)

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

Thierry Delprat updated NXBT-348:
-

Description:
h2. Technical debt on Test

h3. Non Regression tests

- rewrite Selenium tests in WebDriver

= make them more modular and easier to debug

- improve Nuxeo HTML layout to make tests easier

= make tests more robust

h3. Funkload tests

Currently only Ben can really fix a broken test.

We should probably improve training and documentation so that not only Ben can
fix them when needed.

= migrate CMIS and Rest Tests in java

h3. Multi-DB / Multi-OS

MultiDB and Multi-OS tests matrix have been added recently.

There is still a lot of work to be done so that they all run :
- fix unit tests on MSSQL and MySQL (h2, PGSQL et Oracle are ok)
- Windows : there are still failed unit tests under windows
- OpenJDK 7 : there are still failed unit tests under windows

Non regression testing in Matrix should also be fixed but it's probably
pointless until all unit tests are fixed.

h2. CI infrastructure speedup

The goal is to make CI feedback quicker.
We can not expect CI feedback to take a only few minutes :
- build is big
- we have a lot of tests in different configuration

But there are some actions we can do to improve the feedback time.

h3. fix Nexus / Jenkins concurrency issue

Nexus and Jenkins master share the same server and the same NAS.
- Jenkins Master uses NAS storage to store the workspace (build and test
results)
- Nexus uses NAS to store the repo

Monitoring shows that the server has a load average about 2 and that Jenkins or
Nexus are faster when the other service is off.

This means we should work on the global optimization of this Nexus/Jenkins
setup : that will globalling improve speed of all CI :
- for fetching / pushing artifacts
- for storing results

Based on Ben's remarks, the main lead for improvement seems to be the NFS share
:
- separate NASs for Jenkins / Nexus ?
- use local storage instead of NAS ?
- NFS / NAS tunning ?
- ...

h3. GWT Build issue

GWT build is really very slow and represent a big part of the global Nuxeo
build time event if we only have a few (3 or 4) GWT modules.

= This needs to be fixed, both for CI and for developpers

Identified solutions include :
- change profile to limit the number of target browser (meaning nb of
permitation) during the standard Build
( we will still need to do the full build for releases)
- disable GWT optimizations during standard builds
- be sure to only trigger the GWT build when needed

See
http://stackoverflow.com/questions/1011863/how-do-i-speed-up-the-gwt-compiler

NB : we can also extract GWT modules in Addons to help running GWT builds in
parallel

h3. Slave build performances

Currently the build on the Jenkins slaves is about the same time than on a dev
laptop.

= we can make better !

It's true that a big part of the Jenkins slave are poor hardware (the dwarf).

Before taking any decision, we should probably do some profiling to see exactly
what are the real impacting factors :
- test build on a bigger CPU (like Octo)
- use RAMFS to speedup I/O
- tweak compile options ?
- test on big RackSpace VMs

= based on that we will be able to define what kind of Build slaves we need

(then we will have to see what we can host internaly and what must be external)

h2. CI Config

h3. Permanent checks

Permanent checks currently don't wait for nuxeo-features to be built but won't
raise relevant issues until nuxeo-features is built.
In cases where there are a lot of commits, nuxeo-features build can take
several hours.

= need to change that

So basically, we could have permanent checks be closer to the IT builds :
- rebuild everything from zero
- do build / no UT / distrib on a fast slave
- dispatch non-reg tests on different hosts

h3. Addons

Current distribution build depends on some addons: the one that are considered
standard and used in distribs / MP packages.

= Create a job that build all standard addons so that distribution does not
have to wait for 20 jobs

h3. JBoss distrib

We need to update JBoss distribution to align on tomcat/MP build.

h2. Tests to add

There are still some part of the platform that are poorly / not enough tested

h3. Studio

XXX Let Anahide list what she has in mind, but basically :
- define a standard Studio project
- run build against different targets
- check result in a running Nuxeo on several target versions

h3.Admin Center / Marketplace

We already have a webdriver test that tests the basis.

We need to extend it so that we validate for example :
- add CMF / uninstall DM
- Install DAM / uninstall DAM + install CMF
- ...

XXX more here

was:
h2. Technical debt on Test

h3. Non Regression tests

- rewrite Selenium tests in WebDriver

= make them more modular and easier to debug

- improve Nuxeo HTML layout to make tests easier

= make tests

[JIRA] Reopened: (NXP-8194) set tx timeout from an http header


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

Florent Guillaume reopened NXP-8194:



Reopening to remove servlet-api dependency from nuxeo-runtime. This will go in 
a new ServletHelper in nuxeo-platform-web-common.

 set tx timeout from an http header
 --

 Key: NXP-8194
 URL: https://jira.nuxeo.com/browse/NXP-8194
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Web Foundations
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Stéphane Lacoin
 Fix For: 5.5.0-HF01, 5.6


 When operating an automation request we want to be able to set the tx timeout 
 using an http header. This is needed for long operation processing such as 
 large blob injection.
 The header key is named {{Nuxeo-Transaction-Timeout}}, values are seconds 
 expression.

--
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-8194) set tx timeout from an http header


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

Florent Guillaume reassigned NXP-8194:
--

Assignee: Florent Guillaume  (was: Stéphane Lacoin)

 set tx timeout from an http header
 --

 Key: NXP-8194
 URL: https://jira.nuxeo.com/browse/NXP-8194
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Web Foundations
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Florent Guillaume
 Fix For: 5.5.0-HF01, 5.6


 When operating an automation request we want to be able to set the tx timeout 
 using an http header. This is needed for long operation processing such as 
 large blob injection.
 The header key is named {{Nuxeo-Transaction-Timeout}}, values are seconds 
 expression.

--
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-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] 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.

h2. Approach

*Comparing (= making a diff of) 2 documents or 2 versions of

[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/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: 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

--
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

--
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-899) Accessing to a operation chain from an action (edit) is crashing if the action id is 19 characters long and if the operation has the same id

Accessing to a operation chain from an action (edit) is crashing if the action 
id is 19 characters long and if the operation has the same id


 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
 Fix For: 2.5




--
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-899) Accessing to an operation chain from an action (edit link) is crashing if the action id is 19 characters long and if the operation has the same id


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

Sun Tan updated NXS-899:


Summary: Accessing to an operation chain from an action (edit link) is 
crashing if the action id is 19 characters long and if the operation has the 
same id  (was: Accessing to a operation chain from an action (edit) is crashing 
if the action id is 19 characters long and if the operation has the same id)

 Accessing to an operation chain from an action (edit link) is crashing if the 
 action id is 19 characters long and if the operation has the same id
 --

 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
 Fix For: 2.5




--
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: (NXS-899) Accessing to an operation chain from an action (edit link) is crashing if the action id is 19 characters long and if the operation has the same id


[ 
https://jira.nuxeo.com/browse/NXS-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108770#comment-108770
 ] 

Sun Tan commented on NXS-899:
-

Same for event handler but with 21 characters

 Accessing to an operation chain from an action (edit link) is crashing if the 
 action id is 19 characters long and if the operation has the same id
 --

 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
 Fix For: 2.5




--
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] Issue Comment Edited: (NXP-8226) Fix Social Collaboration Selenium tests


[ 
https://jira.nuxeo.com/browse/NXP-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108757#comment-108757
 ] 

Thomas Roger edited comment on NXP-8226 at 1/3/12 2:57 PM:
---

Rename test files (problem with case)
https://github.com/nuxeo/nuxeo-distribution/commit/73393d23dfb9c3045f882926971f182c9ceb5ce1
https://github.com/nuxeo/nuxeo-distribution/commit/971dfafb33bf4015fd869c9c1609e4df73e188d6

  was (Author: troger):
Rename test files (problem with case)
https://github.com/nuxeo/nuxeo-distribution/commit/73393d23dfb9c3045f882926971f182c9ceb5ce1
  
 Fix Social Collaboration Selenium tests
 ---

 Key: NXP-8226
 URL: https://jira.nuxeo.com/browse/NXP-8226
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
  Components: Social Collaboration
Reporter: Thomas Roger
Assignee: Thomas Roger
 Fix For: 5.5.x

  Time Spent: 5 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] Created: (NXS-900) random test failure because of extensions ordering in extensions.xml

2012-01-03 Thread Bogdan Stefanescu (JIRA NUXEO)

random test failure because of extensions ordering in extensions.xml


 Key: NXS-900
 URL: https://jira.nuxeo.com/browse/NXS-900
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Bogdan Stefanescu
Assignee: Bogdan Stefanescu
Priority: Major


The tests fails on my laptop because the extensions.xml compare done in unit 
tests fails.
They are passing on linux machines ... (on jenkins etc.)


--
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-893) Uninstalling the Nuxeo DM Default configuration [EASY] Application Template makes the Domain type unavailable


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

Anahide Tchertchian updated NXS-893:


Status: Open  (was: Triage)

 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] Commented: (NXP-8194) set tx timeout from an http header


[ 
https://jira.nuxeo.com/browse/NXP-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108772#comment-108772
 ] 

Florent Guillaume commented on NXP-8194:


https://github.com/nuxeo/nuxeo-services/commit/61c56dd613cc2d20f99544cd98a4713147afef9b
https://github.com/nuxeo/nuxeo-runtime/commit/8f589478f166113ff1f50f0cb8fc495bf6176333
https://github.com/nuxeo/nuxeo-features/commit/ecc99a4b1253f5f7f3e654a77f1b0df014e5196b
https://github.com/nuxeo/nuxeo-webengine/commit/4c4562c2a18bb4db79c550035be100962efe7aaa


 set tx timeout from an http header
 --

 Key: NXP-8194
 URL: https://jira.nuxeo.com/browse/NXP-8194
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Web Foundations
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Florent Guillaume
 Fix For: 5.5.0-HF01, 5.6


 When operating an automation request we want to be able to set the tx timeout 
 using an http header. This is needed for long operation processing such as 
 large blob injection.
 The header key is named {{Nuxeo-Transaction-Timeout}}, values are seconds 
 expression.

--
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-8194) set tx timeout from an http header


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

Florent Guillaume resolved NXP-8194.


Resolution: Fixed

 set tx timeout from an http header
 --

 Key: NXP-8194
 URL: https://jira.nuxeo.com/browse/NXP-8194
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Web Foundations
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Florent Guillaume
 Fix For: 5.5.0-HF01, 5.6


 When operating an automation request we want to be able to set the tx timeout 
 using an http header. This is needed for long operation processing such as 
 large blob injection.
 The header key is named {{Nuxeo-Transaction-Timeout}}, values are seconds 
 expression.

--
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-8194) set tx timeout from an http header

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

Florent Guillaume updated NXP-8194:
---

Upgrade notes:
New methods:
- TransactionHelper.startTransaction(timeout): starts a transaction with the
given timeout.
- ServletHelper.startTransaction(HttpServletRequest): starts a transaction with
the timeout given by the Nuxeo-Transaction-Timeout header of the request.

For tests, new feature:
- JettyTransactionalFeature: manages the transaction manager and connection
factory binding in the jetty naming.

was:
In TransactionHelper, new method:
- startTransaction(HttpServletRequest): takes into account the
Nuxeo-Transaction-Timeout header sent in the client request.
For tests, new feature:
- JettyTransactionalFeature: manages the transaction manager and connection
factory binding in the jetty naming.

set tx timeout from an http header
--

Key: NXP-8194
URL: https://jira.nuxeo.com/browse/NXP-8194
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Components: Web Foundations
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Florent Guillaume
Fix For: 5.5.0-HF01, 5.6

When operating an automation request we want to be able to set the tx timeout
using an http header. This is needed for long operation processing such as
large blob injection.
The header key is named {{Nuxeo-Transaction-Timeout}}, values are seconds
expression.

--
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: (NXS-893) Uninstalling the Nuxeo DM Default configuration [EASY] Application Template makes the Domain type unavailable


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

Anahide Tchertchian resolved NXS-893.
-

Resolution: Duplicate

NXP-8054 duplicate: this is a hot reload pb on Nuxeo side.

 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] Updated: (NXS-892) Container types are not well hot reloaded


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

Anahide Tchertchian updated NXS-892:


Tags: hotreload

 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] Resolved: (NXP-8023) Document the new system and migration process


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

Anahide Tchertchian resolved NXP-8023.
--

   Resolution: Fixed
Fix Version/s: (was: 5.5.x)
   5.5

Work is done, pages are here:
http://doc.nuxeo.com/x/N4AO
http://doc.nuxeo.com/x/AYSN
http://doc.nuxeo.com/x/A4SN

Documentation could be improved, but another ticket will be created for that in 
NXDOC.

 Document the new system and migration process
 -

 Key: NXP-8023
 URL: https://jira.nuxeo.com/browse/NXP-8023
 Project: Nuxeo Enterprise Platform
  Issue Type: Sub-task
  Components: Themes, Web UI
Reporter: Anahide Tchertchian
Assignee: Anahide Tchertchian
 Fix For: 5.5




--
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-898) Fix error page when opening Operation Online help


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

Anahide Tchertchian updated NXS-898:


Description: 
- I click on Automation  Automation Chain  New
- I expand the Fetch Context exposed into the chain
- I click on the See Online Help button
Problem
- The page open a new window with this folioing url

http://explorer.nuxeo.org/nuxeo/site/distribution/Nuxeo%20DM-5.5/viewOperation/Context.FetchDocument

= Nuxeo DM 5.5 ditribution not present

  was:
- I click on Automation  Automation Chain  New
- I expand the Fetch Context exposed into the chain
- I click on the See Online Help button
Problem
- The page open a new window with this folioing url

http://explorer.nuxeo.org/nuxeo/site/distribution/Nuxeo%20DM-5.5/viewOperation/Context.FetchDocument

= Nuxeo DM 5.5 ditribtion not present

Summary: Fix error page when opening Operation Online help  (was: 
Operation Online help crash)

 Fix error page when opening Operation Online help
 -

 Key: NXS-898
 URL: https://jira.nuxeo.com/browse/NXS-898
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Pivotal Integration

 - I click on Automation  Automation Chain  New
 - I expand the Fetch Context exposed into the chain
 - I click on the See Online Help button
 Problem
 - The page open a new window with this folioing url
 http://explorer.nuxeo.org/nuxeo/site/distribution/Nuxeo%20DM-5.5/viewOperation/Context.FetchDocument
 = Nuxeo DM 5.5 ditribution not present

--
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-897) Add subwidgets palette on a custom template widget subwidgets configuration


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

Anahide Tchertchian updated NXS-897:


Description: 
If a user defines a template widget pour display a multi-valued field, the 
subwidgets palette with subwidgets for this field is not available = find a 
way to make it available (?).


  was:
If a user defines a template widget pour display a multi-valued field, he is 
not proposed the subwidget palette when editing the widget subwidgets.


Summary: Add subwidgets palette on a custom template widget subwidgets 
configuration  (was: Propose subwidgets palette for custom template)

 Add subwidgets palette on a custom template widget subwidgets configuration
 ---

 Key: NXS-897
 URL: https://jira.nuxeo.com/browse/NXS-897
 Project: Nuxeo Studio
  Issue Type: Improvement
  Components: Layouts
Affects Versions: 2.5
Reporter: Thierry Martins
Assignee: Anahide Tchertchian
Priority: Major
 Fix For: 2.5.1, Short term backlog


 If a user defines a template widget pour display a multi-valued field, the 
 subwidgets palette with subwidgets for this field is not available = find a 
 way to make it available (?).

--
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: (LIVED-149) Allow live edit to be usable with MS Office 2010


[ 
https://jira.nuxeo.com/browse/LIVED-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108777#comment-108777
 ] 

Arnaud Kervern commented on LIVED-149:
--

LiveEdit, with the new installer is now fully compatible with Office 2010 with 
both 32 and 64 versions.

 Allow live edit to be usable with MS Office 2010
 

 Key: LIVED-149
 URL: https://jira.nuxeo.com/browse/LIVED-149
 Project: Nuxeo Live Desktop
  Issue Type: Improvement
Reporter: Arnaud Kervern
Assignee: Arnaud Kervern
Priority: Major
 Fix For: NLE 2.3.0




--
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: (LIVED-149) Allow live edit to be usable with MS Office 2010


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

Arnaud Kervern updated LIVED-149:
-

Fix Version/s: (was: NLE 2.3.0)
   NLE 2.3.1

 Allow live edit to be usable with MS Office 2010
 

 Key: LIVED-149
 URL: https://jira.nuxeo.com/browse/LIVED-149
 Project: Nuxeo Live Desktop
  Issue Type: Improvement
Reporter: Arnaud Kervern
Assignee: Arnaud Kervern
Priority: Major
 Fix For: NLE 2.3.1




--
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: (LIVED-149) Allow live edit to be usable with MS Office 2010


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

Arnaud Kervern resolved LIVED-149.
--

Resolution: Fixed

 Allow live edit to be usable with MS Office 2010
 

 Key: LIVED-149
 URL: https://jira.nuxeo.com/browse/LIVED-149
 Project: Nuxeo Live Desktop
  Issue Type: Improvement
Reporter: Arnaud Kervern
Assignee: Arnaud Kervern
Priority: Major
 Fix For: NLE 2.3.1




--
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] Commented: (LIVED-209) Migrate current vdproj projects to WiX


[ 
https://jira.nuxeo.com/browse/LIVED-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108778#comment-108778
 ] 

Arnaud Kervern commented on LIVED-209:
--

Migrate LiveEdit installer done. Creating a 32 and 64bits installer.

 Migrate current vdproj projects to WiX
 

 Key: LIVED-209
 URL: https://jira.nuxeo.com/browse/LIVED-209
 Project: Nuxeo Live Desktop
  Issue Type: Improvement
  Components: DragDrop plugin, NLE MSO
 Environment: Windows
Reporter: Mathieu Guillaume
Assignee: Arnaud Kervern

 The vdproj format has been deprecated. It also requires the installation of 
 Visual Studio on the build machines.
 The current vdproj projects need to be migrated to a new format, and WiX 
 seems to be a good contender as that's what Microsoft migrated to.

--
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-8193) Use a Personal Name in the mailfrom attribute in nuxeo.conf


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

Anahide Tchertchian updated NXP-8193:
-

Status: Open  (was: Triage)

 Use a Personal Name in the mailfrom attribute  in  nuxeo.conf
 -

 Key: NXP-8193
 URL: https://jira.nuxeo.com/browse/NXP-8193
 Project: Nuxeo Enterprise Platform
  Issue Type: Improvement
  Components: Mail
Affects Versions: 5.4.2
 Environment: Windows 7
Reporter: Michel Caissie

 The needs :  Configure the  reply address of the notification emails to 
 contain  a Personal Name (displayed on the mail client) and the reply 
 address.  Ex: Nuxeo Answers  nore...@nuxeo.com
 The tests:  Configure nuxeo.conf
  1-  mail.from=supp...@domain.com  -  works ok  but without  Personal Name
  2-  mail.from=Domain supp...@domain.com   -  server doesn't start
  3-  mail.from=Domain supp...@domain.com   - server starts but  notification 
 email are not sent
  4-  mail.from=whatever including   or= server doesn't start 

--
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-882) Improve the document type generated layout


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

Anahide Tchertchian updated NXS-882:


Fix Version/s: (was: 2.4.4)
   Short term backlog
   2.5.1

 Improve the document type generated layout
 --

 Key: NXS-882
 URL: https://jira.nuxeo.com/browse/NXS-882
 Project: Nuxeo Studio
  Issue Type: Task
  Components: User Experience
Affects Versions: 2.4.3
Reporter: Lise Kemen
Assignee: Lise Kemen
 Fix For: 2.5.1, Short term backlog

 Attachments: Screen Shot 2011-12-21 at 17.03.21.png, Screen Shot 
 2011-12-21 at 17.03.33.png


 One of the first thing you can do with Studio is to create a custom document 
 type, with your fields of data.
 But the layout generation is really messy. See screenshots.
 - Products side: provide a classes system to have a flexible layout
 - Studio side: make studio generate the right classes depending of user's 
 layout choice

--
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-899) Accessing to an operation chain from an action (edit link) is crashing if the action id is 19 characters long and if the operation has the same id


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

Sun Tan updated NXS-899:


Status: Open  (was: Triage)

 Accessing to an operation chain from an action (edit link) is crashing if the 
 action id is 19 characters long and if the operation has the same id
 --

 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
 Fix For: 2.6




--
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: (NXS-899) Accessing to an operation chain from an action (edit link) is crashing if the action id is 19 characters long and if the operation has the same id


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

Sun Tan reassigned NXS-899:
---

Assignee: Sun Tan

 Accessing to an operation chain from an action (edit link) is crashing if the 
 action id is 19 characters long and if the operation has the same id
 --

 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
Assignee: Sun Tan
 Fix For: 2.6




--
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: (NXS-899) Accessing to an operation chain from an action (edit link) is crashing if the action id is 19 characters long and if the operation has the same id


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

Sun Tan resolved NXS-899.
-

   Resolution: Fixed
Fix Version/s: (was: 2.5)
   2.6

 Accessing to an operation chain from an action (edit link) is crashing if the 
 action id is 19 characters long and if the operation has the same id
 --

 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
Assignee: Sun Tan
 Fix For: 2.6




--
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: (NXS-899) Accessing to an operation chain from an action (edit link) is crashing if the action id is 19 characters long and if the operation has the same id


[ 
https://jira.nuxeo.com/browse/NXS-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108785#comment-108785
 ] 

Sun Tan commented on NXS-899:
-

Fixed with
http://hgpriv.nuxeo.org/nuxeo-studio/rev/99dd7465c4bd

It wasn't about the length but it was randomly doing it in a specific order.

 Accessing to an operation chain from an action (edit link) is crashing if the 
 action id is 19 characters long and if the operation has the same id
 --

 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
Assignee: Sun Tan
 Fix For: 2.6




--
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-8359) Use new Actions management from WebActions for currentTab / CurrentSubTab/ ...


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

Thomas Roger updated NXP-8359:
--

Component/s: DAM

 Use new Actions management from WebActions for currentTab / CurrentSubTab/ ...
 --

 Key: NXP-8359
 URL: https://jira.nuxeo.com/browse/NXP-8359
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
  Components: DAM
Reporter: Thomas Roger
Assignee: Thomas Roger

 We don't need to store it anymore in the Dam*Actions bean, we can use 
 everywhere WebActions to handle our tabs / subtabs.

--
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-8243) Add nuxeo-quota addon


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

Thomas Roger updated NXP-8243:
--

Fix Version/s: ADDONS_5.5

 Add nuxeo-quota addon
 -

 Key: NXP-8243
 URL: https://jira.nuxeo.com/browse/NXP-8243
 Project: Nuxeo Enterprise Platform
  Issue Type: New Feature
Reporter: Thomas Roger
Assignee: Thomas Roger
 Fix For: ADDONS_5.5, 5.6


 {{QuotaStatsService}} to register {{QuotaStatsUpdater}}s that will update 
 specific metadata on documents. 
 Add an implementation to count non-folderish documents, that will be used in 
 an adapter implementing {{QuotaStatsNonFolderishCount}}.

--
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-8359) Use new Actions management from WebActions for currentTab / CurrentSubTab/ ...


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

Thomas Roger resolved NXP-8359.
---

   Resolution: Fixed
Fix Version/s: 5.5

 Use new Actions management from WebActions for currentTab / CurrentSubTab/ ...
 --

 Key: NXP-8359
 URL: https://jira.nuxeo.com/browse/NXP-8359
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
  Components: DAM
Reporter: Thomas Roger
Assignee: Thomas Roger
 Fix For: 5.5


 We don't need to store it anymore in the Dam*Actions bean, we can use 
 everywhere WebActions to handle our tabs / subtabs.

--
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-8200) User suggest box style changes when DAM is installed


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

Anahide Tchertchian reassigned NXP-8200:


Assignee: Lise Kemen

 User suggest box style changes when DAM is installed
 

 Key: NXP-8200
 URL: https://jira.nuxeo.com/browse/NXP-8200
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Web UI
Affects Versions: 5.5
Reporter: Solen Guitter
Assignee: Lise Kemen
Priority: Detail
 Fix For: 5.5.x

 Attachments: Screen Shot 2011-12-21 at 11.13.49.png, Screen Shot 
 2011-12-21 at 11.21.29.png


 When user installs CAP, DM, Social Collab, the user suggest box (used in 
 Access Rights tab for instance) has a white background. As soon as user 
 installs DAM, the box gets the old light blue background everywhere.

--
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-8396) Faceted search contrib is not registered due to new 5.5 packaging


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

Anahide Tchertchian updated NXP-8396:
-

Component/s: CMF

 Faceted search contrib is not registered due to new 5.5 packaging
 -

 Key: NXP-8396
 URL: https://jira.nuxeo.com/browse/NXP-8396
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: CMF
Affects Versions: 5.5
Reporter: Vladimir Pasquier
 Fix For: 5.5.x


 The addon faceted search contrib is not registered since we packaged cmf 
 (5.5) as an addon. 
 We need to remove this contribution waiting for NXP-8214 and then re-add it.

--
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-8396) Faceted search contrib is not registered due to new 5.5 packaging


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

Anahide Tchertchian updated NXP-8396:
-

Fix Version/s: 5.5.x

 Faceted search contrib is not registered due to new 5.5 packaging
 -

 Key: NXP-8396
 URL: https://jira.nuxeo.com/browse/NXP-8396
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: CMF
Affects Versions: 5.5
Reporter: Vladimir Pasquier
 Fix For: 5.5.x


 The addon faceted search contrib is not registered since we packaged cmf 
 (5.5) as an addon. 
 We need to remove this contribution waiting for NXP-8214 and then re-add it.

--
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-8219) Create a bank of flavors


[ 
https://jira.nuxeo.com/browse/NXP-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108800#comment-108800
 ] 

Anahide Tchertchian commented on NXP-8219:
--

please ban the word bank as it refers to something else for themes.

 Create a bank of flavors
 

 Key: NXP-8219
 URL: https://jira.nuxeo.com/browse/NXP-8219
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
  Components: Themes, Web UI
Affects Versions: 5.5
Reporter: Lise Kemen
Assignee: Lise Kemen
 Fix For: 5.5.x

   Original Estimate: 1 day
  Remaining Estimate: 1 day

 There is 2 default sets of flavor in the Platform: the Nuxeo default set and 
 a Rainbow set, to understand with colors which value is used where.
 We will now provide a bank of flavors, to help users to choose easily the 
 main color of their platform, and also allow them to use the local theme 
 configuration.

--
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-8200) User suggest box style changes when DAM is installed


[ 
https://jira.nuxeo.com/browse/NXP-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108801#comment-108801
 ] 

Thomas Roger commented on NXP-8200:
---

The RichFaces skin is still referenced in {{nuxeo-dam-web}}, should be removed.

 User suggest box style changes when DAM is installed
 

 Key: NXP-8200
 URL: https://jira.nuxeo.com/browse/NXP-8200
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Web UI
Affects Versions: 5.5
Reporter: Solen Guitter
Assignee: Lise Kemen
Priority: Detail
 Fix For: 5.5.x

 Attachments: Screen Shot 2011-12-21 at 11.13.49.png, Screen Shot 
 2011-12-21 at 11.21.29.png


 When user installs CAP, DM, Social Collab, the user suggest box (used in 
 Access Rights tab for instance) has a white background. As soon as user 
 installs DAM, the box gets the old light blue background everywhere.

--
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-8220) Create a Marketplace package for the bank of flavor


[ 
https://jira.nuxeo.com/browse/NXP-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108802#comment-108802
 ] 

Anahide Tchertchian commented on NXP-8220:
--

please ban the word bank as it refers to something else for themes.

 Create a Marketplace package for the bank of flavor
 ---

 Key: NXP-8220
 URL: https://jira.nuxeo.com/browse/NXP-8220
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
Affects Versions: 5.5
Reporter: Lise Kemen
Assignee: Vladimir Pasquier
 Fix For: 5.5.x




--
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-8222) The old dashboard is displayed when IE9 is in compatibility mode


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

Anahide Tchertchian updated NXP-8222:
-

Tags: bugday

probably trivial to fix (should check the browser detection code)

 The old dashboard is displayed when IE9 is in compatibility mode
 

 Key: NXP-8222
 URL: https://jira.nuxeo.com/browse/NXP-8222
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Dashboard / OpenSocial
Affects Versions: 5.5
 Environment: IE 9
 CAP + DM + SC
Reporter: Solen Guitter
 Fix For: 5.5.x

 Attachments: Screen Shot 2011-12-22 at 15.16.56.png, Screen Shot 
 2011-12-22 at 15.17.09.png


 When IE 9 is in compatibility view, the old dashboard is displayed instead of 
 the Open Social one.

--
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-8225) [IE] On creation form, focus is on Description instead of title


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

Anahide Tchertchian updated NXP-8225:
-

Tags: bugday

 [IE] On creation form, focus is on Description instead of title
 ---

 Key: NXP-8225
 URL: https://jira.nuxeo.com/browse/NXP-8225
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
Affects Versions: 5.5
 Environment: IE9, Win 7
Reporter: Solen Guitter
 Fix For: 5.5.x


 With IE 9, when I create a new document, the Description field is 
 automatically selected instead of the Title field.

--
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: (LIVED-206) Firefox protocol handler doesn't work with 6.0.x


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

Arnaud Kervern resolved LIVED-206.
--

   Resolution: Fixed
Fix Version/s: Protocol Handler 0.5.0

 Firefox protocol handler doesn't work with 6.0.x
 

 Key: LIVED-206
 URL: https://jira.nuxeo.com/browse/LIVED-206
 Project: Nuxeo Live Desktop
  Issue Type: Bug
  Components: Protocol Handler plugin
Affects Versions: Protocol Handler 0.5.0
 Environment: Windows 7 32bits
Reporter: Arnaud Kervern
Assignee: Arnaud Kervern
Priority: Major
 Fix For: Protocol Handler 0.5.0


 When using protocol handler with Firefox 6.0.x in Windows, the extension 
 installed correctly but nothing append while clicking icons for editing a 
 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: (LIVED-206) Firefox protocol handler doesn't work with 6.0.x


[ 
https://jira.nuxeo.com/browse/LIVED-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108806#comment-108806
 ] 

Arnaud Kervern commented on LIVED-206:
--

Yes, Protocol handler 0.5.0 was built for Firefox to version 6.x.
And protocol handler 0.5.1 to version 9.x.

 Firefox protocol handler doesn't work with 6.0.x
 

 Key: LIVED-206
 URL: https://jira.nuxeo.com/browse/LIVED-206
 Project: Nuxeo Live Desktop
  Issue Type: Bug
  Components: Protocol Handler plugin
Affects Versions: Protocol Handler 0.5.0
 Environment: Windows 7 32bits
Reporter: Arnaud Kervern
Assignee: Arnaud Kervern
Priority: Major
 Fix For: Protocol Handler 0.5.0


 When using protocol handler with Firefox 6.0.x in Windows, the extension 
 installed correctly but nothing append while clicking icons for editing a 
 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-663) Withdraw the blue line that separates the editors' title of the rest of the page


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

Anahide Tchertchian updated NXS-663:


Priority: Major  (was: Blocker)

 Withdraw the blue line that separates the editors' title of the rest of the 
 page
 

 Key: NXS-663
 URL: https://jira.nuxeo.com/browse/NXS-663
 Project: Nuxeo Studio
  Issue Type: Improvement
  Components: User Experience
Affects Versions: 2.1
Reporter: Alain Escaffre
Assignee: Bogdan Stefanescu
Priority: Major
 Fix For: Qualified but not a priority


 The reason is that, with this line, the upper contextuel help seems separated 
 from the area it is related to, which is strange and doesn't entice people to 
 read it.

--
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: (LIVED-197) Firefox addons : make it avalaible for Firefox 5


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

Arnaud Kervern resolved LIVED-197.
--

   Resolution: Fixed
Fix Version/s: Protocol Handler 0.4.12

 Firefox addons : make it avalaible for Firefox 5
 

 Key: LIVED-197
 URL: https://jira.nuxeo.com/browse/LIVED-197
 Project: Nuxeo Live Desktop
  Issue Type: Bug
  Components: DragDrop plugin, Protocol Handler plugin
Affects Versions: DragNDrop FF 0.9.9, Protocol Handler 0.4.11
 Environment: Firefox 5 ; Windows
Reporter: Sébastien De Nef
Assignee: Arnaud Kervern
Priority: Major
 Fix For: Protocol Handler 0.4.12


 Hi,
 After upgrading to Firefox 5 the Nuxeo addons (I just installed Protocl 
 Handler, but surely the same for DD) are disabled.
 Please check compatibility with FF5 and upgrade addons.
 Thanks

--
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-8224) Add a new automation chain to archive documents


[ 
https://jira.nuxeo.com/browse/NXP-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108809#comment-108809
 ] 

Anahide Tchertchian commented on NXP-8224:
--

is this done?
note that a NXS issue should be created for the operation to be available from 
Studio.

 Add a new automation chain to archive documents
 ---

 Key: NXP-8224
 URL: https://jira.nuxeo.com/browse/NXP-8224
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
Affects Versions: 5.6
Reporter: Delphine Renevey
Assignee: Mariana Cedica

 This automation chain must be configurable with : 
 - query or page provider
 - automation operation

--
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-887) Manage per-user/project persistence of default values for widgets properties


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

Anahide Tchertchian updated NXS-887:


Description: 
This request comes from the poll.
For instance, we want to be able to have the field Date formatting already 
pre-filled when dropping a date property in a layout.

TODO: suggest something for this feature

  was:
This request comes from the poll.
For instance, we want to be able to have the field Date formatting already 
pre-filled when dropping a date property in a layout.

TODO: propose something for this feature

Summary: Manage per-user/project persistence of default values for 
widgets properties  (was: Manage persistance of default values of widgets 
parameters per users)

 Manage per-user/project persistence of default values for widgets properties
 

 Key: NXS-887
 URL: https://jira.nuxeo.com/browse/NXS-887
 Project: Nuxeo Studio
  Issue Type: New Feature
Reporter: Alain Escaffre

 This request comes from the poll.
 For instance, we want to be able to have the field Date formatting already 
 pre-filled when dropping a date property in a layout.
 TODO: suggest something for this feature

--
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-8548) Suggestbox: the directory fields for user and group search should not be hardcoded

2012-01-03 Thread Olivier Grisel (JIRA NUXEO)

Suggestbox: the directory fields for user and group search should not be 
hardcoded
--

 Key: NXP-8548
 URL: https://jira.nuxeo.com/browse/NXP-8548
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Web UI
Affects Versions: 5.5
Reporter: Olivier Grisel
Assignee: Olivier Grisel


The UserGroupLookupSuggester class should lookup the UserManager service to 
find about the right field to query upon.

--
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: (NXS-886) Set up versioning rule from Studio


[ 
https://jira.nuxeo.com/browse/NXS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108812#comment-108812
 ] 

Anahide Tchertchian commented on NXS-886:
-

note that default versioning is added by default in the default configuration 
for now (see DefaultProject.java). This feature should not be available for all 
versions (i think 5.4.2 is the first to be ok, to check).

 Set up versioning rule from Studio
 --

 Key: NXS-886
 URL: https://jira.nuxeo.com/browse/NXS-886
 Project: Nuxeo Studio
  Issue Type: New Feature
Reporter: Alain Escaffre
 Fix For: Qualified but not a priority


 This comes from a request in polls:
 In versioning management, be able to initialize the version number. For 
 instance, set the version to directly 2.0.0 when necessary instead of having 
 to use the suggested increment on major/minor selection.

--
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-8238) Breadcrumb is not refreshed after edit title of document object.


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

Anahide Tchertchian updated NXP-8238:
-

Tags: bugday

 Breadcrumb is not refreshed after edit title of document  object.
 -

 Key: NXP-8238
 URL: https://jira.nuxeo.com/browse/NXP-8238
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Web UI
Affects Versions: 5.5
Reporter: kasab
 Attachments: suz_bug.JPG


 In folder of a workspace:
 1.I created File document object with title Suzanna. 
 2.Open Suzanna File object
 3.Click Edit tab
 4.Change title to Mona Lisa
 5.Click save.
 After that breadcrumb is not refreshed to Mona Lisa

--
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-8237) When click back page relations of a document object does not work correctly


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

Anahide Tchertchian updated NXP-8237:
-

Tags: bugday

 When click back page relations of a document object does not work correctly
 ---

 Key: NXP-8237
 URL: https://jira.nuxeo.com/browse/NXP-8237
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Web UI
Affects Versions: 5.5
Reporter: kasab

 On a workspace a File docuent object(F1) references two picture document 
 objects with different uploaded images - P1, P2.
 1. Choose Relations tab for F1, and you can see outgoing relation links, 
 which references to P1, P2.
 2. Choose P1 of the reletions (references) and open it - opens image of P1.
 3. Click BACK buton and go back to the list with relation links.
 4. Choose P2 and open it - it's opened again P2, you see view tab for P1.
 If choose and open again and again any one of relations - you cannot see 
 correct image, the system aways show you the image from your first choice.
 Only if you go to back for step 1 and 2 - image is refreshed.

--
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-8236) Relations are not refreshed when deleted


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

Anahide Tchertchian resolved NXP-8236.
--

Resolution: Won't Fix

It's been chosen that in the default application, relations are kept upon 
document deletion, but this can be easily customized = resolving as won't fix.

 Relations are not refreshed when deleted
 

 Key: NXP-8236
 URL: https://jira.nuxeo.com/browse/NXP-8236
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Web UI
Affects Versions: 5.5
Reporter: kasab

 One Nuxeo File object F1 rerences another one F2. If referenced document F2 
 is deleted and then navigate to F1 relations tab, the referencing document 
 still contains reference to the deleted one. 

--
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-8236) Relations are not refreshed when deleted


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

Anahide Tchertchian updated NXP-8236:
-

Status: Open  (was: Triage)

 Relations are not refreshed when deleted
 

 Key: NXP-8236
 URL: https://jira.nuxeo.com/browse/NXP-8236
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Web UI
Affects Versions: 5.5
Reporter: kasab

 One Nuxeo File object F1 rerences another one F2. If referenced document F2 
 is deleted and then navigate to F1 relations tab, the referencing document 
 still contains reference to the deleted one. 

--
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) Fix hotreload of a document allowed subtypes


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

Anahide Tchertchian updated NXP-8547:
-

Summary: Fix hotreload of a document allowed subtypes  (was: Allowed 
subtypes are not well hot reloaded)

 Fix hotreload of a document allowed subtypes
 

 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] Updated: (NXS-891) Add a Disable feature checkbox on every Studio feature


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

Anahide Tchertchian updated NXS-891:


Summary: Add a Disable feature checkbox on every Studio feature  (was: 
Have a Disable feature checkbox on every Studio feature)

 Add 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
 Fix For: 2.5.1, Short term backlog


 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] Commented: (NXS-890) Vocabularies without order doesn't work in studio


[ 
https://jira.nuxeo.com/browse/NXS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108814#comment-108814
 ] 

Anahide Tchertchian commented on NXS-890:
-

Could you add steps to reproduce? Thanks

 Vocabularies without order doesn't work in studio
 -

 Key: NXS-890
 URL: https://jira.nuxeo.com/browse/NXS-890
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sun Tan
 Fix For: 2.5.1, Short term backlog


 We should add a default value or add a validation on this order field
 In Nuxeo when loading a vocabulary without order:
 {code}
 2011-12-29 10:59:28,276 ERROR [facelets.viewhandler] Error Rendering 
 View[/view_admin.xhtml]
 com.sun.facelets.tag.TagAttributeException: /directory/view_directory.xhtml 
 @24,31 test=#{!isReadOnly} /directory/view_directory.xhtml @24,31 
 test=#{!isReadOnly}: /directory/view_directory.xhtml @20,68 
 value=#{directoryUIActions.readOnly}: Error reading 'readOnly' on type 
 org.nuxeo.ecm.webapp.directory.DirectoryUIActionsBean_$$_javassist_65
   at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:235)
   at com.sun.facelets.tag.TagAttribute.getBoolean(TagAttribute.java:79)
   at com.sun.facelets.tag.jstl.core.IfHandler.apply(IfHandler.java:49)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 org.nuxeo.ecm.platform.ui.web.binding.alias.AliasTagHandler.apply(AliasTagHandler.java:152)
   at 
 org.nuxeo.ecm.platform.ui.web.tag.handler.SetTagHandler.apply(SetTagHandler.java:108)
   at 
 org.nuxeo.ecm.platform.ui.web.binding.alias.AliasTagHandler.apply(AliasTagHandler.java:152)
   at 
 org.nuxeo.ecm.platform.ui.web.tag.handler.SetTagHandler.apply(SetTagHandler.java:108)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
   at 
 com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:256)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:306)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:280)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:169)
   at com.sun.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:65)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at com.sun.facelets.tag.jstl.core.IfHandler.apply(IfHandler.java:54)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
   at 
 com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:256)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:306)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:280)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:169)
   at com.sun.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:65)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
   at 
 com.sun.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:64)
   at 
 org.nuxeo.theme.jsf.facelets.CompositionHandler.apply(CompositionHandler.java:191)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:385)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:353)
   at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at com.sun.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:109)
   at

[JIRA] Updated: (NXP-8246) Fix FileUtils path problems under windows


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

Anahide Tchertchian updated NXP-8246:
-

Summary: Fix FileUtils path problems under windows  (was: FileUtils path 
problems under windows)

 Fix FileUtils path problems under windows
 -

 Key: NXP-8246
 URL: https://jira.nuxeo.com/browse/NXP-8246
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


 Two methods, FileUtils#getParentPath and FileUtils#getFileName are detecting 
 end of string with a slash /. Must be File.separator for windows 
 compliance.

--
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-8218) Fix class cast exception in publication tree building


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

Anahide Tchertchian updated NXP-8218:
-

Summary: Fix class cast exception in publication tree building  (was: class 
cast in publication tree building)

 Fix class cast exception in publication tree building
 -

 Key: NXP-8218
 URL: https://jira.nuxeo.com/browse/NXP-8218
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Publishing
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Stéphane Lacoin
Priority: Major
 Fix For: 5.4.2-HF15, 5.5.0-HF01, 5.6

   Original Estimate: 0 minutes
  Remaining Estimate: 0 minutes

 In {{SectionPublicationTree}}, if the current user do not have right for 
 accessing the node, a wrapper of type {{VirtualCoreFolderPublicationNode}} is 
 returned instead of {{CoreFolderPublicationNode}}. This causes the cast error 
  in the {{RootSectionsPublicationTree}}. 
 The cast can be eliminated easily as it's not required by the called API.
 {noformat}
 2011-12-15 11:26:36,160 ERROR 
 [org.nuxeo.ecm.platform.actions.DefaultActionFilter] evaluation of condition 
 SeamContext.get(publishActions).canPublishSelection failed: returning false
 java.lang.reflect.InvocationTargetException
   at sun.reflect.GeneratedMethodAccessor705.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:123)
   at 
 org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:287)
   at 
 org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:183)
   at 
 org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:73)
   at 
 org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:82)
   at 
 org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:56)
   at 
 org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:50)
   at 
 org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:79)
   at 
 org.nuxeo.runtime.expression.JexlExpression.eval(JexlExpression.java:36)
   at 
 org.nuxeo.ecm.platform.actions.DefaultActionFilter.checkConditions(DefaultActionFilter.java:263)
   at 
 org.nuxeo.ecm.platform.actions.DefaultActionFilter.checkRule(DefaultActionFilter.java:150)
   at 
 org.nuxeo.ecm.platform.actions.DefaultActionFilter.accept(DefaultActionFilter.java:114)
   at 
 org.nuxeo.ecm.platform.actions.ActionService.applyFilters(ActionService.java:81)
   at 
 org.nuxeo.ecm.platform.actions.ActionService.getActions(ActionService.java:108)
   at 
 org.nuxeo.ecm.webapp.action.WebActionsBean.getUnfiltredActionsList(WebActionsBean.java:126)
   at 
 org.nuxeo.ecm.webapp.action.WebActionsBean.getUnfiltredActionsList(WebActionsBean.java:135)
   at sun.reflect.GeneratedMethodAccessor533.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
   at 
 org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
   at 
 org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
   at 
 org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
   at 
 org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
   at 
 org.nuxeo.ecm.platform.ui.web.util.NuxeoBijectionInterceptor.aroundInvoke(NuxeoBijectionInterceptor.java:68)
   at 
 org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
   at 
 org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
   at 
 org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
   at 
 org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
   at 
 org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
   at 
 org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
   at 
 fr.gouv.education.acrennes.ged.document.AcarenWebActionsBean_$$_javassist_14.getUnfiltredActionsList(AcarenWebActionsBean_$$_javassist_14.java)
   at sun.reflect.GeneratedMethodAccessor532.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at

[JIRA] Updated: (NXP-8248) Fix preview generation with some files


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

Anahide Tchertchian updated NXP-8248:
-

Summary: Fix preview generation with some files  (was: Preview can not be 
generated)

 Fix preview generation with some files
 --

 Key: NXP-8248
 URL: https://jira.nuxeo.com/browse/NXP-8248
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: DAM
Affects Versions: 5.5
 Environment: NuxeoDAM-1.1-VM-vmx
Reporter: The Cat
 Fix For: 6.0

 Attachments: CNNInternational.wmv


 Trying to import the wmv file CNNInternational.wmv that you can download 
 here: http://dl.free.fr/bIYNQ7suI  (availlable for 30days).
 The preview (when I click on the document) return me:
 Preview can not be generated for this document
 Blob path: default
 org.nuxeo.ecm.platform.preview.api.PreviewException: Error during conversion

--
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-8538) Fix NPE in nuxeo-platform-importer addon when multi threaded


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

Anahide Tchertchian updated NXP-8538:
-

Summary: Fix NPE in nuxeo-platform-importer addon when multi threaded  
(was: NPE in nuxeo-platform-importer addon when multi threaded)

 Fix NPE in nuxeo-platform-importer addon when multi threaded
 

 Key: NXP-8538
 URL: https://jira.nuxeo.com/browse/NXP-8538
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: Importer
Affects Versions: 5.4.2, 5.5
Reporter: Benoit Delbosc
Assignee: Benoit Delbosc
 Fix For: 5.4.2-HF15, 5.5.0-HF01, 5.6


 NPE is raised when trying to access session from a document model.
 This happens when the session of the root document has been closed by another 
 thread/task.
 The root document of a new thread/task must be re/attached with the task 
 session.
 {code}
 7:37,171 [pool-1-thread-2] ERROR [NUXEO:base.GenericThreadedImportTask] 
 Unable to create leaf document for 
 /home/xml:java.lang.NullPointerException
 16:47:37,171 [pool-1-thread-2] ERROR [NUXEO:base.GenericThreadedImportTask] 
 Error during import
 java.lang.Exception: java.lang.NullPointerException
   at 
 org.nuxeo.ecm.platform.importer.base.GenericThreadedImportTask.doCreateLeafNode(GenericThreadedImportTask.java:223)
   at 
 org.nuxeo.ecm.platform.importer.base.GenericThreadedImportTask.recursiveCreateDocumentFromNode(GenericThreadedImportTask.java:330)
   at 
 org.nuxeo.ecm.platform.importer.base.GenericThreadedImportTask.recursiveCreateDocumentFromNode(GenericThreadedImportTask.java:325)
   at 
 org.nuxeo.ecm.platform.importer.base.GenericThreadedImportTask.run(GenericThreadedImportTask.java:366)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:619)
 Caused by: java.lang.NullPointerException
   at org.nuxeo.ecm.core.api.CoreInstance.getSession(CoreInstance.java:223)
   at 
 org.nuxeo.ecm.core.api.impl.DocumentModelImpl.getCoreSession(DocumentModelImpl.java:403)
   at 
 org.nuxeo.ecm.core.api.impl.DocumentModelImpl$RunWithCoreSession.execute(DocumentModelImpl.java:440)
   at 
 org.nuxeo.ecm.core.api.impl.DocumentModelImpl.getACP(DocumentModelImpl.java:878)
   at ...
 org.nuxeo.ecm.platform.importer.base.GenericThreadedImportTask.doCreateLeafNode(GenericThreadedImportTask.java:215)
   ... 6 more
 {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-8540) Fix windows path problems in Nuxeo core convert tests


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

Anahide Tchertchian updated NXP-8540:
-

Summary: Fix windows path problems in Nuxeo core convert tests  (was: Nuxeo 
core convert plugin tests - path windows problems)

 Fix windows path problems in Nuxeo core convert tests
 -

 Key: NXP-8540
 URL: https://jira.nuxeo.com/browse/NXP-8540
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


 Several problems about paths and EOL (windows compliance)

--
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-8539) Fix Nuxeo filesystem connectors path problems under windows


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

Anahide Tchertchian updated NXP-8539:
-

Summary: Fix Nuxeo filesystem connectors path problems under windows  (was: 
Nuxeo filesystem connectors path problems under windows)

 Fix Nuxeo filesystem connectors path problems under windows
 ---

 Key: NXP-8539
 URL: https://jira.nuxeo.com/browse/NXP-8539
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


 Several problems about paths and EOL (windows compliance)

--
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-8535) ContentViewImpl.getParametersChanged ignores some cases


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

Anahide Tchertchian updated NXP-8535:
-

Status: Open  (was: Triage)

 ContentViewImpl.getParametersChanged ignores some cases
 ---

 Key: NXP-8535
 URL: https://jira.nuxeo.com/browse/NXP-8535
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
Affects Versions: 5.5
Reporter: François-Denis Gonthier

 The method getParametersChanged returns false immediately once it has found 
 one parameter in the list has not changed from the last time the method was 
 called. The last 'return false' in the for loop should be removed so that the 
 decision of returning false is delayed until the very last parameter.

--
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-8535) ContentViewImpl.getParametersChanged ignores some cases


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

Anahide Tchertchian reassigned NXP-8535:


Assignee: Anahide Tchertchian

 ContentViewImpl.getParametersChanged ignores some cases
 ---

 Key: NXP-8535
 URL: https://jira.nuxeo.com/browse/NXP-8535
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
Affects Versions: 5.5
Reporter: François-Denis Gonthier
Assignee: Anahide Tchertchian

 The method getParametersChanged returns false immediately once it has found 
 one parameter in the list has not changed from the last time the method was 
 called. The last 'return false' in the for loop should be removed so that the 
 decision of returning false is delayed until the very last parameter.

--
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-8535) ContentViewImpl.getParametersChanged ignores some cases


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

Work on NXP-8535 started by Anahide Tchertchian.

 ContentViewImpl.getParametersChanged ignores some cases
 ---

 Key: NXP-8535
 URL: https://jira.nuxeo.com/browse/NXP-8535
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
Affects Versions: 5.5
Reporter: François-Denis Gonthier
Assignee: Anahide Tchertchian

 The method getParametersChanged returns false immediately once it has found 
 one parameter in the list has not changed from the last time the method was 
 called. The last 'return false' in the for loop should be removed so that the 
 decision of returning false is delayed until the very last parameter.

--
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: (NXS-894) Creation related event handlers doesn't work for types created by a content template


[ 
https://jira.nuxeo.com/browse/NXS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108817#comment-108817
 ] 

Anahide Tchertchian commented on NXS-894:
-

please add steps to reproduce and move this issue to NXP: this is not an issue 
in Studio.

 Creation related event handlers doesn't work for types created by a content 
 template
 

 Key: NXS-894
 URL: https://jira.nuxeo.com/browse/NXS-894
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sun Tan

 It seems that content templates uses a SimplePrincipal and not NuxeoPrincipal
 If the EL field is the only activation field filled
 {code}
 19:58:40,641 ERROR [OperationEventListener] Failed to handle event 
 aboutToCreate using chain: InitPropertiesListener
 java.lang.ClassCastException: org.nuxeo.ecm.core.api.SimplePrincipal cannot 
 be cast to org.nuxeo.ecm.core.api.NuxeoPrincipal
   at 
 org.nuxeo.ecm.automation.core.scripting.Scripting.initBindings(Scripting.java:87)
   at 
 org.nuxeo.ecm.automation.core.scripting.MvelExpression.eval(MvelExpression.java:38)
   at 
 org.nuxeo.ecm.automation.core.events.EventHandler.isEnabled(EventHandler.java:254)
   at 
 org.nuxeo.ecm.automation.core.events.EventHandlerRegistry.handleEvent(EventHandlerRegistry.java:195)
   at 
 org.nuxeo.ecm.automation.core.events.OperationEventListener.handleEvent(OperationEventListener.java:33)
   at 
 org.nuxeo.ecm.core.event.impl.EventServiceImpl.fireEvent(EventServiceImpl.java:195)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.fireEvent(AbstractSession.java:400)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.notifyEvent(AbstractSession.java:452)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.createDocument(AbstractSession.java:863)
   at 
 org.nuxeo.ecm.platform.content.template.factories.SimpleTemplateBasedFactory.createContentStructure(SimpleTemplateBasedFactory.java:67)
   at 
 org.nuxeo.ecm.platform.content.template.service.ContentTemplateServiceImpl.executeFactoryForType(ContentTemplateServiceImpl.java:179)
   at 
 org.nuxeo.ecm.platform.content.template.listener.ContentCreationListener.handleEvent(ContentCreationListener.java:60)
   at 
 org.nuxeo.ecm.core.event.impl.EventServiceImpl.fireEvent(EventServiceImpl.java:195)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.fireEvent(AbstractSession.java:400)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.notifyEvent(AbstractSession.java:452)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.createDocument(AbstractSession.java:896)
   at 
 org.nuxeo.ecm.platform.content.template.factories.SimpleTemplateBasedFactory.createContentStructure(SimpleTemplateBasedFactory.java:67)
   at 
 org.nuxeo.ecm.platform.content.template.service.ContentTemplateServiceImpl.executeFactoryForType(ContentTemplateServiceImpl.java:179)
   at 
 org.nuxeo.ecm.platform.content.template.listener.ContentCreationListener.handleEvent(ContentCreationListener.java:60)
   at 
 org.nuxeo.ecm.core.event.impl.EventServiceImpl.fireEvent(EventServiceImpl.java:195)
 {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-8536) Remove hardcoded nuxeo path in Opensocial Gadgets


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

Anahide Tchertchian updated NXP-8536:
-

Summary: Remove hardcoded nuxeo path in Opensocial Gadgets  (was: Remove 
hardcoded nuxeo in Opensocial Gadgets)

 Remove hardcoded nuxeo path in Opensocial Gadgets
 -

 Key: NXP-8536
 URL: https://jira.nuxeo.com/browse/NXP-8536
 Project: Nuxeo Enterprise Platform
  Issue Type: Task
  Components: Dashboard / OpenSocial
Affects Versions: 5.4.2, 5.5
Reporter: Lise Kemen
Assignee: Lise Kemen
 Fix For: 5.4.1-HF15, 5.4.2-HF15, 5.5.0-HF01, 5.5.x


 The list of concerned gadgets:
 - bookmark
 - flash
 - photo
 - richtext
 - ToDoList
 - Video
 + Container.css

--
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-896) Versioning: Impossible to release 2 versions with the same version number and different additional suffix


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

Anahide Tchertchian updated NXS-896:


Status: Open  (was: Triage)

 Versioning: Impossible to release 2 versions with the same version number and 
 different additional suffix 
 

 Key: NXS-896
 URL: https://jira.nuxeo.com/browse/NXS-896
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sun Tan

 The version number is automatically incremented

--
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: (NXS-896) Versioning: Impossible to release 2 versions with the same version number and different additional suffix


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

Anahide Tchertchian resolved NXS-896.
-

Resolution: Duplicate

NXS-886 dupl

 Versioning: Impossible to release 2 versions with the same version number and 
 different additional suffix 
 

 Key: NXS-896
 URL: https://jira.nuxeo.com/browse/NXS-896
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sun Tan

 The version number is automatically incremented

--
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-8545) Fix imaging windows problems


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

Anahide Tchertchian updated NXP-8545:
-

Summary: Fix imaging windows problems  (was: Nuxeo platform imaging windows 
problems)

 Fix imaging windows problems
 

 Key: NXP-8545
 URL: https://jira.nuxeo.com/browse/NXP-8545
 Project: Nuxeo Enterprise Platform
  Issue Type: Bug
  Components: DAM
Affects Versions: 5.5
Reporter: Vladimir Pasquier
Assignee: Vladimir Pasquier
 Fix For: 5.6


 Errors are found when cropping, resizing, converting and rotating pictures 
 (dam importer).

--
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-889) Fix display of referenced layouts


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

Anahide Tchertchian updated NXS-889:


Summary: Fix display of referenced layouts  (was: Using the new features 
external layouts is not taking default widget style in account)

 Fix display of referenced layouts
 -

 Key: NXS-889
 URL: https://jira.nuxeo.com/browse/NXS-889
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sun Tan
 Fix For: 2.5.1, Short term backlog

 Attachments: layout.png


 When creating external layouts in studio, we expect that the layout being 
 displayed exactly the same as if widget were created in the 
 Creation/Edit/View layout tab of the document feature.
 But
 - labels are not in bold
 - when importing several layouts, value widgets are not aligned with others 
 comming from the another layout

--
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-900) Fix random test failure because of extensions ordering in extensions.xml


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

Anahide Tchertchian updated NXS-900:


Summary: Fix random test failure because of extensions ordering in 
extensions.xml  (was: random test failure because of extensions ordering in 
extensions.xml)

 Fix random test failure because of extensions ordering in extensions.xml
 

 Key: NXS-900
 URL: https://jira.nuxeo.com/browse/NXS-900
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Bogdan Stefanescu
Assignee: Bogdan Stefanescu
Priority: Major

 The tests fails on my laptop because the extensions.xml compare done in unit 
 tests fails.
 They are passing on linux machines ... (on jenkins etc.)

--
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: (NXS-894) Creation related event handlers doesn't work for types created by a content template


[ 
https://jira.nuxeo.com/browse/NXS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108820#comment-108820
 ] 

Sun Tan commented on NXS-894:
-

- target platform Nuxeo DM 5.5
- Create an event handler associated to aboutToCreate event
- Don't add any filter/condition BUT an EL expression
- Deploy the studio project in an empty Nuxeo DM 5.5, run Nuxeo and the error 
appears.

 Creation related event handlers doesn't work for types created by a content 
 template
 

 Key: NXS-894
 URL: https://jira.nuxeo.com/browse/NXS-894
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sun Tan

 It seems that content templates uses a SimplePrincipal and not NuxeoPrincipal
 If the EL field is the only activation field filled
 {code}
 19:58:40,641 ERROR [OperationEventListener] Failed to handle event 
 aboutToCreate using chain: InitPropertiesListener
 java.lang.ClassCastException: org.nuxeo.ecm.core.api.SimplePrincipal cannot 
 be cast to org.nuxeo.ecm.core.api.NuxeoPrincipal
   at 
 org.nuxeo.ecm.automation.core.scripting.Scripting.initBindings(Scripting.java:87)
   at 
 org.nuxeo.ecm.automation.core.scripting.MvelExpression.eval(MvelExpression.java:38)
   at 
 org.nuxeo.ecm.automation.core.events.EventHandler.isEnabled(EventHandler.java:254)
   at 
 org.nuxeo.ecm.automation.core.events.EventHandlerRegistry.handleEvent(EventHandlerRegistry.java:195)
   at 
 org.nuxeo.ecm.automation.core.events.OperationEventListener.handleEvent(OperationEventListener.java:33)
   at 
 org.nuxeo.ecm.core.event.impl.EventServiceImpl.fireEvent(EventServiceImpl.java:195)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.fireEvent(AbstractSession.java:400)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.notifyEvent(AbstractSession.java:452)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.createDocument(AbstractSession.java:863)
   at 
 org.nuxeo.ecm.platform.content.template.factories.SimpleTemplateBasedFactory.createContentStructure(SimpleTemplateBasedFactory.java:67)
   at 
 org.nuxeo.ecm.platform.content.template.service.ContentTemplateServiceImpl.executeFactoryForType(ContentTemplateServiceImpl.java:179)
   at 
 org.nuxeo.ecm.platform.content.template.listener.ContentCreationListener.handleEvent(ContentCreationListener.java:60)
   at 
 org.nuxeo.ecm.core.event.impl.EventServiceImpl.fireEvent(EventServiceImpl.java:195)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.fireEvent(AbstractSession.java:400)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.notifyEvent(AbstractSession.java:452)
   at 
 org.nuxeo.ecm.core.api.AbstractSession.createDocument(AbstractSession.java:896)
   at 
 org.nuxeo.ecm.platform.content.template.factories.SimpleTemplateBasedFactory.createContentStructure(SimpleTemplateBasedFactory.java:67)
   at 
 org.nuxeo.ecm.platform.content.template.service.ContentTemplateServiceImpl.executeFactoryForType(ContentTemplateServiceImpl.java:179)
   at 
 org.nuxeo.ecm.platform.content.template.listener.ContentCreationListener.handleEvent(ContentCreationListener.java:60)
   at 
 org.nuxeo.ecm.core.event.impl.EventServiceImpl.fireEvent(EventServiceImpl.java:195)
 {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: (NXS-899) Fix crash when accessing to an operation chain from an action (edit link)


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

Anahide Tchertchian updated NXS-899:


Description: Crash happens only when the action id is 19 characters long 
and if the operation has the same id
Summary: Fix crash when accessing to an operation chain from an action 
(edit link)  (was: Accessing to an operation chain from an action (edit link) 
is crashing if the action id is 19 characters long and if the operation has the 
same id)

 Fix crash when accessing to an operation chain from an action (edit link)
 -

 Key: NXS-899
 URL: https://jira.nuxeo.com/browse/NXS-899
 Project: Nuxeo Studio
  Issue Type: Bug
Reporter: Sun Tan
Assignee: Sun Tan
 Fix For: 2.6


 Crash happens only when the action id is 19 characters long and if the 
 operation has the same id

--
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: (NXS-890) Vocabularies without order doesn't work in studio


[ 
https://jira.nuxeo.com/browse/NXS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108822#comment-108822
 ] 

Sun Tan commented on NXS-890:
-

In Studio with target Nuxeo 5.5
- Create a new Simple vocabulary
- add a new row with an id and a label (Studio let you add a row without order)
- deploy the jar in an empty Nuxeo DM 5.5
- Accessing in the Admin center to the vocabulary, it is failing creating it 
(see stack trace)

 Vocabularies without order doesn't work in studio
 -

 Key: NXS-890
 URL: https://jira.nuxeo.com/browse/NXS-890
 Project: Nuxeo Studio
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sun Tan
 Fix For: 2.5.1, Short term backlog


 We should add a default value or add a validation on this order field
 In Nuxeo when loading a vocabulary without order:
 {code}
 2011-12-29 10:59:28,276 ERROR [facelets.viewhandler] Error Rendering 
 View[/view_admin.xhtml]
 com.sun.facelets.tag.TagAttributeException: /directory/view_directory.xhtml 
 @24,31 test=#{!isReadOnly} /directory/view_directory.xhtml @24,31 
 test=#{!isReadOnly}: /directory/view_directory.xhtml @20,68 
 value=#{directoryUIActions.readOnly}: Error reading 'readOnly' on type 
 org.nuxeo.ecm.webapp.directory.DirectoryUIActionsBean_$$_javassist_65
   at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:235)
   at com.sun.facelets.tag.TagAttribute.getBoolean(TagAttribute.java:79)
   at com.sun.facelets.tag.jstl.core.IfHandler.apply(IfHandler.java:49)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 org.nuxeo.ecm.platform.ui.web.binding.alias.AliasTagHandler.apply(AliasTagHandler.java:152)
   at 
 org.nuxeo.ecm.platform.ui.web.tag.handler.SetTagHandler.apply(SetTagHandler.java:108)
   at 
 org.nuxeo.ecm.platform.ui.web.binding.alias.AliasTagHandler.apply(AliasTagHandler.java:152)
   at 
 org.nuxeo.ecm.platform.ui.web.tag.handler.SetTagHandler.apply(SetTagHandler.java:108)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
   at 
 com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:256)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:306)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:280)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:169)
   at com.sun.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:65)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at com.sun.facelets.tag.jstl.core.IfHandler.apply(IfHandler.java:54)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
   at 
 com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:256)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:306)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFacelet.include(DefaultFacelet.java:280)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:169)
   at com.sun.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:65)
   at 
 com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
   at 
 com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
   at 
 com.sun.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:64)
   at 
 org.nuxeo.theme.jsf.facelets.CompositionHandler.apply(CompositionHandler.java:191)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:385)
   at 
 org.nuxeo.theme.jsf.facelets.vendor.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:353)
   at

[JIRA] Updated: (NXS-900) Fix random test failure because of extensions ordering in extensions.xml