[
https://issues.apache.org/jira/browse/DIRAPI-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRAPI-150.
--
Resolution: Not A Problem
Yes, this is on purpose.
When doing a lookup() or a
[
https://issues.apache.org/jira/browse/DIRSERVER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716176#comment-13716176
]
Kiran Ayyagari commented on DIRSERVER-1489:
---
Added another fix to provide
Emmanuel Lecharny created DIRSERVER-1872:
Summary: The JournalInterceptor is not present in the
configuration
Key: DIRSERVER-1872
URL: https://issues.apache.org/jira/browse/DIRSERVER-1872
[
https://issues.apache.org/jira/browse/DIRSERVER-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1872.
--
Resolution: Fixed
Fixed with http://svn.apache.org/r1505919
[
https://issues.apache.org/jira/browse/DIRSERVER-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716200#comment-13716200
]
Emmanuel Lecharny edited comment on DIRSERVER-1872 at 7/23/13 7:27 AM:
Hi Emmanuel,
Thanks, that's much better and far more readable. :)
This is an interesting issue.
I could play with the code you provided and I suspect an issue in the schema
handling. Either something not enabled correctly or something deeper in the
server.
Investigating...
Regards,
Hi,
I'm having odd issues with adding a new m-may attribute to a custom
metaObjectClass in our schema. We created a custom class in the initial
release of the software with the following ldif:
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.1.12, ou=objectClasses, cn=conneqt-config,
ou=schema
Hi Matthew,
Did you restart the server ?
Additions don't need a server-restart and are handled on the fly.
Modifications on an existing schema element, though, are not very recommended
(especially if you already have data using this schema element) and I'm not
really sure they are handled on
Le 7/23/13 4:53 PM, Pierre-Arnaud Marcelot a écrit :
Hi Matthew,
Did you restart the server ?
Additions don't need a server-restart and are handled on the fly.
Modifications on an existing schema element, though, are not very recommended
(especially if you already have data using this
Carlo Accorsi created DIRSERVER-1873:
Summary: Searching on member attribute (multivalued) for groups is
not working as expected
Key: DIRSERVER-1873
URL: https://issues.apache.org/jira/browse/DIRSERVER-1873
Richard Sand created DIRSTUDIO-940:
--
Summary: Have schema editor populate creatorsName attribute for
new objects (needed by ApacheDS)
Key: DIRSTUDIO-940
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-940
Richard Sand created DIRSTUDIO-941:
--
Summary: friendly name for attribute syntax not shown when
creating new attribute
Key: DIRSTUDIO-941
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-941
[
https://issues.apache.org/jira/browse/DIRSTUDIO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Sand updated DIRSTUDIO-941:
---
Attachment: screenshot-1.jpg
friendly name for attribute syntax not shown when
[
https://issues.apache.org/jira/browse/DIRSTUDIO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Sand updated DIRSTUDIO-941:
---
Attachment: screenshot-2.jpg
friendly name for attribute syntax not shown when
14 matches
Mail list logo