You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2009/12/03 18:59:46 UTC

[jira] Created: (DIRSERVER-1427) Errors should contain the associated SchemaObject when modifying the schema

Errors should contain the associated SchemaObject when modifying the schema
---------------------------------------------------------------------------

                 Key: DIRSERVER-1427
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1427
             Project: Directory ApacheDS
          Issue Type: New Feature
            Reporter: Emmanuel Lecharny
             Fix For: 2.0.0-RC1


Currently, when modifying the Schema, we just gather all the exceptions. Each one of them should be associated with the SchemaObject which generated this exception, in order to be used by Studio.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (DIRSERVER-1427) Errors should contain the associated SchemaObject when modifying the schema

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny reassigned DIRSERVER-1427:
--------------------------------------------

    Assignee: Emmanuel Lecharny

> Errors should contain the associated SchemaObject when modifying the schema
> ---------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1427
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1427
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>            Reporter: Emmanuel Lecharny
>            Assignee: Emmanuel Lecharny
>             Fix For: 2.0.0-RC1
>
>
> Currently, when modifying the Schema, we just gather all the exceptions. Each one of them should be associated with the SchemaObject which generated this exception, in order to be used by Studio.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.