[JIRA] Closed: (NXP-1493) [JODTransform]Return the input document if he is already with the good mimetype

2007-08-28 Thread Laurent Godard (JIRA NUXEO)

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

Laurent Godard closed NXP-1493.
---

   Resolution: Fixed
Fix Version/s: 5.2 M1

not backported as not absolutelly needed

> [JODTransform]Return the input document if he is already with the good 
> mimetype
> ---
>
> Key: NXP-1493
> URL: http://jira.nuxeo.org/browse/NXP-1493
> Project: Nuxeo Enterprise Platform 5
>  Issue Type: New Feature
>  Components: Transforms
>Affects Versions: 5.2 M1
>Reporter: Laurent Godard
>Assignee: Laurent Godard
> Fix For: 5.2 M1
>
>
> the typical example is that for any2pdf, a application/pdf input document 
> generates an exception
> we should avoid this and return the input document instead
> nevertheless, it may be usefull for the transforms to ODF that it can be 
> re-enterred so that ODF file are post-processed by OOo when manually forge
> use case:
> to respect the usual ODF mimetype detection that rely on an implemntation 
> detail (mimetype at pos38).
> our detector do not rely on this but external one yes, so forged document 
> could appear as broken
> post-processing by OOo let things go well
> so, implementation will be
> - if sourceMimetype = destinationMimetype and sourceMimetype not in the 
> supportedMimemtype list of the  transform plugin
> --> return the input file
> --> otherwise, process as usual

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Created: (NXP-1497) Configuration problem of your nuxeo.war/WEB-INF/pages.xml.

2007-08-28 Thread Solen Guitter (JIRA NUXEO)
Configuration problem of your nuxeo.war/WEB-INF/pages.xml.
--

 Key: NXP-1497
 URL: http://jira.nuxeo.org/browse/NXP-1497
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Bug
 Environment: 5.2 08/28 build
Reporter: Solen Guitter
Assignee: Thierry Delprat
Priority: Blocker
 Fix For: 5.2 M1


If you can read this in your browser, this probably because of a configuration 
problem of your nuxeo.war/WEB-INF/pages.xml. To change this, edit the 
OSGI-INF/deployment-fragment.xml of your project at extension pages#PAGES.

Before that I couldn't log in to the application (after some time on the login 
page without touching it). So I restarted it. And got the error above when I 
tried to log in again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Updated: (NXP-1497) Configuration problem of your nuxeo.war/WEB-INF/pages.xml.

2007-08-28 Thread Solen Guitter (JIRA NUXEO)

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

Solen Guitter updated NXP-1497:
---

Attachment: server.log

I attach the log file.

> Configuration problem of your nuxeo.war/WEB-INF/pages.xml.
> --
>
> Key: NXP-1497
> URL: http://jira.nuxeo.org/browse/NXP-1497
> Project: Nuxeo Enterprise Platform 5
>  Issue Type: Bug
> Environment: 5.2 08/28 build
>Reporter: Solen Guitter
>Assignee: Thierry Delprat
>Priority: Blocker
> Fix For: 5.2 M1
>
> Attachments: server.log
>
>
> If you can read this in your browser, this probably because of a 
> configuration problem of your nuxeo.war/WEB-INF/pages.xml. To change this, 
> edit the OSGI-INF/deployment-fragment.xml of your project at extension 
> pages#PAGES.
> Before that I couldn't log in to the application (after some time on the 
> login page without touching it). So I restarted it. And got the error above 
> when I tried to log in again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Commented: (NXP-1497) Configuration problem of your nuxeo.war/WEB-INF/pages.xml.

2007-08-28 Thread Solen Guitter (JIRA NUXEO)

[ 
http://jira.nuxeo.org/browse/NXP-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_24972
 ] 

Solen Guitter commented on NXP-1497:


I restarted again, and this time it worked !

> Configuration problem of your nuxeo.war/WEB-INF/pages.xml.
> --
>
> Key: NXP-1497
> URL: http://jira.nuxeo.org/browse/NXP-1497
> Project: Nuxeo Enterprise Platform 5
>  Issue Type: Bug
> Environment: 5.2 08/28 build
>Reporter: Solen Guitter
>Assignee: Thierry Delprat
>Priority: Blocker
> Fix For: 5.2 M1
>
> Attachments: server.log
>
>
> If you can read this in your browser, this probably because of a 
> configuration problem of your nuxeo.war/WEB-INF/pages.xml. To change this, 
> edit the OSGI-INF/deployment-fragment.xml of your project at extension 
> pages#PAGES.
> Before that I couldn't log in to the application (after some time on the 
> login page without touching it). So I restarted it. And got the error above 
> when I tried to log in again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Created: (NXP-1499) Transformer chains implementation

2007-08-28 Thread Julien Anguenot (JIRA NUXEO)
Transformer chains implementation
-

 Key: NXP-1499
 URL: http://jira.nuxeo.org/browse/NXP-1499
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Bug
  Components: Transforms
Affects Versions: 5.1.0.GA
Reporter: Julien Anguenot
Assignee: Julien Anguenot
 Fix For: 5.1.1


Check mimetype of the actual binary to transform with the input mimetypes of a 
plugin before sending the binary to a plugin which might not check the input 
format before trying to perfrom the actual transformation.  (c.f : issue with 
pdf documents using injector on 5.1.GA)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Assigned: (NXP-1498) index Picture type

2007-08-28 Thread Alain Escaffre (JIRA NUXEO)

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

Alain Escaffre reassigned NXP-1498:
---

Assignee: Julien Anguenot  (was: Thierry Delprat)

> index Picture type
> --
>
> Key: NXP-1498
> URL: http://jira.nuxeo.org/browse/NXP-1498
> Project: Nuxeo Enterprise Platform 5
>  Issue Type: Task
>Affects Versions: 5.1.0.GA
>Reporter: Alain Escaffre
>Assignee: Julien Anguenot
>
> the schema can be found in nuxeo-platform-imaging-core project, I guess there 
> may be a problem : it is a complex type. Can you confirm ? 
> Without considering this problem, the following attributes   should be in the 
> full text : 
>
>  
> 
> 
> 
>   
> 
> there is no special field to index separately, exepct the one that are 
> already in the dublin core (title ...) and I suppose there is nothing to do 
> for that ? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Created: (NXP-1498) index Picture type

2007-08-28 Thread Alain Escaffre (JIRA NUXEO)
index Picture type
--

 Key: NXP-1498
 URL: http://jira.nuxeo.org/browse/NXP-1498
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Task
Affects Versions: 5.1.0.GA
Reporter: Alain Escaffre
Assignee: Thierry Delprat


the schema can be found in nuxeo-platform-imaging-core project, I guess there 
may be a problem : it is a complex type. Can you confirm ? 

Without considering this problem, the following attributes   should be in the 
full text : 


 
 
  
  
  



there is no special field to index separately, exepct the one that are already 
in the dublin core (title ...) and I suppose there is nothing to do for that ? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Created: (NXP-1500) UserManager with multiple directories

2007-08-28 Thread Florent Guillaume (JIRA NUXEO)
UserManager with multiple directories
-

 Key: NXP-1500
 URL: http://jira.nuxeo.org/browse/NXP-1500
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Task
Affects Versions: 5.1.0.GA
Reporter: Florent Guillaume
Assignee: Florent Guillaume
Priority: Major
 Fix For: 5.1.1


(Extracted from NXP-1082 and rewritten)

1. Parallel directories
We have several directories with different schemas.
user fields = n fields from directory A + m fields from Directory B 
uids must have correspondances in all directories.
This is comparable to a "meta directory" in CPS.

1.1 A special case of parallelism is the fact that we can have a different 
directory to do the authentication (which is already implemented but will have 
to be generalized).

2. Serial directories
We have several directories with the same schema.
users = users from directory A + users from Directory B 
uids must be distinct in all directories.
This is comparable to a "stacking directory" in CPS.

3. We may allow the directories in a serial case to be actually built from 
parallel directories. Not the other way around.

At login time, the user will be searched in all directories and authentication 
will occur on first match. 



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Updated: (NXP-1082) NXDirectories improvments

2007-08-28 Thread Florent Guillaume (JIRA NUXEO)

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

Florent Guillaume updated NXP-1082:
---

Description: 
UserManager Improvements


Performances and robustness
---
Done in M3.


Mapping
---

The virtual group mapping should be indirect to administrators and members.
These virtual groups are very much like roles. The name of these roles should 
be configurable.
We should reintroduice the Role Directiry concepts.

This role mapping should occur at userManager level.
At directory level, we must provide an automatic group mapping :
 - all users from one directory = group with the same name as the directory
 - all users from one directory => member of some other groups

Directories Improvements
=

Group Mapping :
---
Directories must support virtual group mapping.
2 built-in virtual group per directory :
 - one for all users
 - one for directory admins

Domain association :

A directory is a community of users.
A domain is a community of content.

Directory level groups will be used to define permission at domain level.
Users from one directory can have access to one or several domain.

Symetrically, from one domain, users can have access to one or more directories.

A dedicated ACL could be used to store this at domain level.

  was:
UserManager Improvements


Performances and robustness
---
Done in M3.


Mapping
---

The virtual group mapping should be indirect to administrators and members.
These virtual groups are very much like roles. The name of these roles should 
be configurable.
We should reintroduice the Role Directiry concepts.

This role mapping should occur at userManager level.
At directory level, we must provide an automatic group mapping :
 - all users from one directory = group with the same name as the directory
 - all users from one directory => member of some other groups

Multi-Directory support
---
UserManager should support several directories for users.
For groups, we have the same need, we need al least aggregated directories when 
groups are handled directly in a LDAP server.

As in CPS Directories can be :
 - stacked : users = users from directory A + users from Directory B
 - aggregated : 1 user = n fields from directory A + m fields from Directory B

The typical use case for the méta-directory is Users from LDAP with some 
application specific fields that are stored in a separated database.

Unlike in CPS, we could simplify the complexity of Meta and Stacking 
directories by only addressing the user/group use case :
 - the stacking and meta aggregation are done by user manager not by the 
directory
 - stacking and meta are only supported at one level : meta over stacking

There could be uses cases for more complex associations, but we will handle it 
when needed ...

At login time, the user will be searched in all directories and authentication 
will occur on first match.

Directories Improvements
=

Group Mapping :
---
Directories must support virtual group mapping.
2 built-in virtual group per directory :
 - one for all users
 - one for directory admins

Domain association :

A directory is a community of users.
A domain is a community of content.

Directory level groups will be used to define permission at domain level.
Users from one directory can have access to one or several domain.

Symetrically, from one domain, users can have access to one or more directories.

A dedicated ACL could be used to store this at domain level.


Multiple directories support for UserManager moved to a separate task NXP-1500.



> NXDirectories improvments
> -
>
> Key: NXP-1082
> URL: http://jira.nuxeo.org/browse/NXP-1082
> Project: Nuxeo Enterprise Platform 5
>  Issue Type: Improvement
>Reporter: Thierry Delprat
>Assignee: George Lefter
> Fix For: 5.2 M1
>
>
> UserManager Improvements
> 
> Performances and robustness
> ---
> Done in M3.
> Mapping
> ---
> The virtual group mapping should be indirect to administrators and members.
> These virtual groups are very much like roles. The name of these roles should 
> be configurable.
> We should reintroduice the Role Directiry concepts.
> This role mapping should occur at userManager level.
> At directory level, we must provide an automatic group mapping :
>  - all users from one directory = group with the same name as the directory
>  - all users from one directory => member of some other groups
> Directories Improvements
> =
> Group Mapping :
> ---
> Directories must support virtual group mapping.
> 2 built-in virtual group

[JIRA] Created: (NXP-1501) Better UserManager extension overrides

2007-08-28 Thread Florent Guillaume (JIRA NUXEO)
Better UserManager extension overrides
--

 Key: NXP-1501
 URL: http://jira.nuxeo.org/browse/NXP-1501
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Improvement
Affects Versions: 5.1.0.GA
Reporter: Florent Guillaume
Assignee: Florent Guillaume
 Fix For: 5.1.1


A contribution that wishes to override the userManager extension point has to 
repeat all the old configuration.
In particular, it has to repeat the implementation class, and specify a 
 (otherwise "FULL" is the default).
This is not very useable.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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


[JIRA] Resolved: (NXP-1501) Better UserManager extension overrides

2007-08-28 Thread Florent Guillaume (JIRA NUXEO)

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

Florent Guillaume resolved NXP-1501.


Resolution: Fixed

Done in rev 24337 (24338 in 5.1 branch).
(It's in the branch because a customer needs some things on top of that.)



> Better UserManager extension overrides
> --
>
> Key: NXP-1501
> URL: http://jira.nuxeo.org/browse/NXP-1501
> Project: Nuxeo Enterprise Platform 5
>  Issue Type: Improvement
>Affects Versions: 5.1.0.GA
>Reporter: Florent Guillaume
>Assignee: Florent Guillaume
> Fix For: 5.1.1
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> A contribution that wishes to override the userManager extension point has to 
> repeat all the old configuration.
> In particular, it has to repeat the implementation class, and specify a 
>  (otherwise "FULL" is the default).
> This is not very useable.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


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