[jira] Commented: (DIRSTUDIO-331) Instant error when importing schema in a new schema-project

["Stefan Seelmann (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763880#action_12763880 ] 

Stefan Seelmann commented on DIRSTUDIO-331:
-------------------------------------------

The critical thing is to add the "system" core schema. It includes the built-in attributes (name, cn, uid, etc.) as well as all syntaxes and matching rules. However also when including the "system" schema there are errors because some syntaxes and matching rules are missing. I'll update the schema files from current OpenLDAP 2.4.

> Instant error when importing schema in a new schema-project
> -----------------------------------------------------------
>
>                 Key: DIRSTUDIO-331
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-331
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-schemaeditor
>    Affects Versions: 1.1.0
>         Environment: Windows XP+SP2, SunJava 1.6.0. Update 5
> also Windows XP+SP3, SunJava 1.5.0 Update 14
> also Ubuntu 8.04 with SunJava 1.5.0_15
>            Reporter: Marc
>            Priority: Blocker
>             Fix For: 1.5.0
>
>         Attachments: ads_schema_errors.jpg, ads_used_openldap_schema.jpg, core.schema
>
>
> We got plenty of errors everytime we imported a openldap-scheme. We did following steps:
> 1. Open Apache Studio
> 2. Open schema-editor view
> 3. Create a new schema-project (in this step don't import any schema)
> 4. After creating the new project, do a right-click and choose "import". Choose "open ldap".
> 5. Import "core" schema
> After importing the core schema, plenty of errors appears in the problems-view. We got the same problems on the windows box and
> on a ubuntu virtual machine. But the strange thing is, we got at least one installation running on a ubuntu machine (no virtual machine) without
> any problems. The schema-editor is not usable in this state.

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