Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Java

      Description

      As per your email:
      (It is in OpenLDAP format - verified)

      Attach your
      schema to the JIRA (do not cut and paste into comments) I will include
      this into the build (takes 2 seconds).

      BTW your schema file should be in OpenLDAP syntax.

        Activity

        Hide
        Emmanuel Lecharny added a comment -

        Closing all issues created in 2005 and before which are marked resolved

        Show
        Emmanuel Lecharny added a comment - Closing all issues created in 2005 and before which are marked resolved
        Hide
        Alex Karasulu added a comment -

        I'm pulling out of this. If Mark get's his own IANA number we can add this back, or he can just use the schemas JNDI property to add it himself when embedding.

        Removed in commit revision 158876.

        Show
        Alex Karasulu added a comment - I'm pulling out of this. If Mark get's his own IANA number we can add this back, or he can just use the schemas JNDI property to add it himself when embedding. Removed in commit revision 158876.
        Hide
        Alex Karasulu added a comment -

        Looks like the schema parser in the plugin is case sensitive and was blowing chunks on objectClass with a capital C. Don't know how this should be handled for now.

        Regardless I have added the schema now. The server should build with you're schema objects. I added the files on revision 109923 here:

        http://svn.apache.org/viewcvs.cgi?rev=109923&view=rev

        Cheers,
        Alex

        Show
        Alex Karasulu added a comment - Looks like the schema parser in the plugin is case sensitive and was blowing chunks on objectClass with a capital C. Don't know how this should be handled for now. Regardless I have added the schema now. The server should build with you're schema objects. I added the files on revision 109923 here: http://svn.apache.org/viewcvs.cgi?rev=109923&view=rev Cheers, Alex
        Hide
        Alex Karasulu added a comment -

        Oooops just saw the deps you had in the schema file, my bad!

        1. $Id:$
          #
        2. ScheduleWorld's directory schema items
          #
        3. depends upon:
        4. core.schema
        5. cosine.schema
        6. inetorgperson.schema
          #
        Show
        Alex Karasulu added a comment - Oooops just saw the deps you had in the schema file, my bad! $Id:$ # ScheduleWorld's directory schema items # depends upon: core.schema cosine.schema inetorgperson.schema #
        Hide
        Alex Karasulu added a comment -

        Let's call this a task so I can create a subtask and assign it to you.

        Show
        Alex Karasulu added a comment - Let's call this a task so I can create a subtask and assign it to you.
        Hide
        Alex Karasulu added a comment -

        Also looks like you pulled these OIDs out of a hat hehe. This can be dangerous because it can introduce conflicts. Do me a favor and just apply for a private enterprise number from IANA and use it to create your own OIDs for schedule world. Here's where you can apply for this:

        http://www.iana.org/cgi-bin/enterprise.pl

        For now I will add em but will have to change the ScheduleWorldPerson OID since it conflicts with the OpenLDAPperson here:

        objectClass ( 1.3.6.1.4.1.4203.1.4.5 NAME 'OpenLDAPperson'
        DESC 'OpenLDAP Person'
        SUP ( pilotPerson $ inetOrgPerson )
        MUST ( uid $ cn )
        MAY ( givenName $ labeledURI $ o ) )

        We would not have this in our schema set but you never know. The OID 0.9.2342.19200300.100.1.61 did not show up on a google search but you never know. I will replace 1.3.6.1.4.1.4203.1.4.5 with 0.9.2342.19200300.100.1.62 for the ScheduleWorldPerson.

        Alex

        Show
        Alex Karasulu added a comment - Also looks like you pulled these OIDs out of a hat hehe. This can be dangerous because it can introduce conflicts. Do me a favor and just apply for a private enterprise number from IANA and use it to create your own OIDs for schedule world. Here's where you can apply for this: http://www.iana.org/cgi-bin/enterprise.pl For now I will add em but will have to change the ScheduleWorldPerson OID since it conflicts with the OpenLDAPperson here: objectClass ( 1.3.6.1.4.1.4203.1.4.5 NAME 'OpenLDAPperson' DESC 'OpenLDAP Person' SUP ( pilotPerson $ inetOrgPerson ) MUST ( uid $ cn ) MAY ( givenName $ labeledURI $ o ) ) We would not have this in our schema set but you never know. The OID 0.9.2342.19200300.100.1.61 did not show up on a google search but you never know. I will replace 1.3.6.1.4.1.4203.1.4.5 with 0.9.2342.19200300.100.1.62 for the ScheduleWorldPerson. Alex
        Hide
        Alex Karasulu added a comment -

        What other schemas does your schema depend on? You must have all dependent schemas available and listed such as cosine, core, et. cetera.

        Show
        Alex Karasulu added a comment - What other schemas does your schema depend on? You must have all dependent schemas available and listed such as cosine, core, et. cetera.

          People

          • Assignee:
            Alex Karasulu
            Reporter:
            Mark Swanson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development