directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <akaras...@apache.org>
Subject Re: [studio] directory studio & schema files
Date Wed, 09 Jan 2008 13:46:10 GMT
Just got an idea after hitting send ...

Might be nice to have the import and export capabilities understand these
kinds of server specifics based on a kind of server profile.  This way
studio can accommodate these kinds of changes for some rudimentary ETL like
operations.

On Jan 9, 2008 8:44 AM, Alex Karasulu <akarasulu@apache.org> wrote:

> Schema extensions are server specific and optional.  Also the LDIF loader
> used by studio should load I think because the description is just an
> attribute value.  The thing is ApacheDS will not accept X-ORIGIN because
> this is specific to Netscape derived servers. ApacheDS uses a similar
> extension called X-SCHEMA which tells you what schema the schema element
> comes from.
>
> Alex
>
>
> On Jan 9, 2008 2:20 AM, Emmanuel Lecharny <elecharny@gmail.com> wrote:
>
> > Hi Torgeir !
> >
> > Torgeir Veimo wrote:
> > >
> > > On 8 Jan 2008, at 22:16, Emmanuel Lecharny wrote:
> > >
> > >> I have modified the parser to accept empty DESC.
> > >
> > >
> > > Ok, now I get an error message which is very helpful. Thx!
> > >
> > > I exported a schema from a Fedora LDAP server with Studio, and it
> > > contains X-ORIGIN statements for all attribute types. This breaks the
> > > import into Apache DS. X-ORIGIN is allowed by the RFC for schema
> > files?
> >
> > I'm afraid that the current parser does not support extensions right
> > now. This is something we must add into the parser. Can you fill a JIRA
> > for this?
> >
> > Thanks a lot for all those reports ! This help us a lot !
> > >
> > > --Torgeir Veimo
> > > torgeir@pobox.com
> > >
> > >
> > >
> > >
> >
> >
> > --
> > --
> > cordialement, regards,
> > Emmanuel L├ęcharny
> > www.iktek.com
> > directory.apache.org
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message