|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (DIRSTUDIO-403) cannot add refs when the ExtensibleObject OC has been added to a referralcannot add refs when the ExtensibleObject OC has been added to a referral
------------------------------------------------------------------------- Key: DIRSTUDIO-403 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 Project: Directory Studio Issue Type: Bug Affects Versions: 1.2.0 Reporter: Emmanuel Lecharny Fix For: 1.3.0 When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Updated: (DIRSTUDIO-403) cannot add refs when the ExtensibleObject OC has been added to a referral[ https://issues.apache.org/jira/browse/DIRSTUDIO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-403: --------------------------------------------- Component/s: studio-ldapbrowser > cannot add refs when the ExtensibleObject OC has been added to a referral > ------------------------------------------------------------------------- > > Key: DIRSTUDIO-403 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 1.2.0 > Reporter: Emmanuel Lecharny > Fix For: 1.3.0 > > > When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. > If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. > This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Updated: (DIRSTUDIO-403) cannot add refs when the ExtensibleObject OC has been added to a referral[ https://issues.apache.org/jira/browse/DIRSTUDIO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-403: --------------------------------------------- Fix Version/s: (was: 1.3.0) 1.4.0 Postponed for next version. > cannot add refs when the ExtensibleObject OC has been added to a referral > ------------------------------------------------------------------------- > > Key: DIRSTUDIO-403 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 1.2.0 > Reporter: Emmanuel Lecharny > Fix For: 1.4.0 > > > When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. > If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. > This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Updated: (DIRSTUDIO-403) cannot add refs when the ExtensibleObject OC has been added to a referral[ https://issues.apache.org/jira/browse/DIRSTUDIO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-403: -------------------------------------- Fix Version/s: (was: 1.4.0) 1.5.0 > cannot add refs when the ExtensibleObject OC has been added to a referral > ------------------------------------------------------------------------- > > Key: DIRSTUDIO-403 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 1.2.0 > Reporter: Emmanuel Lecharny > Fix For: 1.5.0 > > > When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. > If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. > This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Assigned: (DIRSTUDIO-403) cannot add refs when the ExtensibleObject OC has been added to a referral[ https://issues.apache.org/jira/browse/DIRSTUDIO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann reassigned DIRSTUDIO-403: ----------------------------------------- Assignee: Stefan Seelmann > cannot add refs when the ExtensibleObject OC has been added to a referral > ------------------------------------------------------------------------- > > Key: DIRSTUDIO-403 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 1.2.0 > Reporter: Emmanuel Lecharny > Assignee: Stefan Seelmann > Fix For: 1.5.0 > > > When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. > If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. > This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Resolved: (DIRSTUDIO-403) cannot add refs when the ExtensibleObject OC has been added to a referral[ https://issues.apache.org/jira/browse/DIRSTUDIO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-403. --------------------------------------- Resolution: Fixed This works now > cannot add refs when the ExtensibleObject OC has been added to a referral > ------------------------------------------------------------------------- > > Key: DIRSTUDIO-403 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 1.2.0 > Reporter: Emmanuel Lecharny > Assignee: Stefan Seelmann > Fix For: 1.5.0 > > > When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. > If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. > This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Updated: (DIRSTUDIO-403) Cannot add refs when the ExtensibleObject OC has been added to a referral[ https://issues.apache.org/jira/browse/DIRSTUDIO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-403: --------------------------------------------- Summary: Cannot add refs when the ExtensibleObject OC has been added to a referral (was: cannot add refs when the ExtensibleObject OC has been added to a referral) > Cannot add refs when the ExtensibleObject OC has been added to a referral > ------------------------------------------------------------------------- > > Key: DIRSTUDIO-403 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 1.2.0 > Reporter: Emmanuel Lecharny > Assignee: Stefan Seelmann > Fix For: 1.5.0 > > > When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. > If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. > This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Closed: (DIRSTUDIO-403) Cannot add refs when the ExtensibleObject OC has been added to a referral[ https://issues.apache.org/jira/browse/DIRSTUDIO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot closed DIRSTUDIO-403. -------------------------------------------- Apache Directory Studio version 1.5.0 has been released. > Cannot add refs when the ExtensibleObject OC has been added to a referral > ------------------------------------------------------------------------- > > Key: DIRSTUDIO-403 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-403 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 1.2.0 > Reporter: Emmanuel Lecharny > Assignee: Stefan Seelmann > Fix For: 1.5.0 > > > When creating a referral, if we also select the extensibleObject ObjectClass, we can't add the ref mandatory attributeType. It seems that the entry is locked. > If I remove the extensibleObject OC from the ObjectClass lists, then suddenly the ref is available. > This is a serious bug, as the extensibleObjectClass is almost mandatory in order to accept attributeTypes which are not availablme locally, but declared on the distant LDAP server the referrl is pointing to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
| Free embeddable forum powered by Nabble | Forum Help |