http://blog.gmane.org/gmane.comp.apache.incubator.directory.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36671 <pre>Hi, so as of today, I have merged 37 out of 54 modules. The following modules still have to be merged : apacheds-core-api apacheds-core-shared apacheds-core apacheds-core-avl apacheds-xdbm-partition apacheds-ldif-partition apacheds-jdbm-partition apacheds-core-annotations apacheds-server-config apacheds-server-jndi apacheds-server-replication apacheds-xdbm-tools apacheds-core-integ apacheds-server-integ apacheds-kerberos-test ldap-client-test apacheds-service Some of them require few modifications, some other are more complex. I'll keep you informed as soon as I make progress. </pre> Emmanuel Lécharny 2012-05-22T15:14:37 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36670 <pre>Emmanuel Lecharny created DIRSERVER-1728: -------------------------------------------- Summary: Replace numeric errors by textual errors Key: DIRSERVER-1728 URL: https://issues.apache.org/jira/browse/DIRSERVER-1728 Project: Directory ApacheDS Issue Type: Task Affects Versions: 2.0.0-M7 Reporter: Emmanuel Lecharny Fix For: 2.0.0-RC1 We have declarations like : ERR_42=An entry with a ''referral'' ObjectClass must contains a ''ref'' Attribute It would be way better to have something like for clarity sake : ERR_42_REF_ATTRIBUTE_MISSING=An entry with a ''referral'' ObjectClass must contains a ''ref'' Attribute -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Emmanuel Lecharny (JIRA 2012-05-22T12:35:40 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36669 <pre>Hi guys, I'm currently facing some interesting challenge on this class, as we have removed the OneLevel and SubLevel index from trunk. This has some direct impact on the txn branch code, as we have to update the code accordingly. Methods like add/delete... are storing the changes done on those index : // Update the OneLevel index Index&lt;?&gt; oneLevelIdx = partition.getSystemIndex( ApacheSchemaConstants.APACHE_ONE_LEVEL_AT_OID ); indexChange = new IndexChange( oneLevelIdx, parentId, id, IndexChange.Type.ADD, true ); changeContainer.addChange( indexChange ); We have to remove those lines, but we also have to modify the RDN Index update. I'm be working on that, it may take a bit of time. In any case, the merge is way more complex than any other we have already done on the server, although I do expect to have it done by the end of this week. SVN is not helping a lot here... :/ </pre> Emmanuel Lécharny 2012-05-22T09:48:42 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36667 <pre>Why isn't &lt; at &gt;CreateDS annotation defined as &lt; at &gt;Inherited? I'm trying to write a base class that includes &lt; at &gt;CreateDS annotation, but it is not inherited. Thanks for any explanation of this. Duane Fletcher Alcatel-Lucent </pre> Fletcher, Duane W (Duane 2012-05-21T19:41:57 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36666 <pre>Peter Schwindt created DIRSTUDIO-815: ---------------------------------------- Summary: Tiny translation error [DE] Key: DIRSTUDIO-815 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-815 Project: Directory Studio Issue Type: Bug Affects Versions: 1.5.3 Reporter: Peter Schwindt Priority: Trivial When connecting to an LDAP source, after entering the password, the progress popup shows "Verbindungen am Öffenen". Despite this being a typo itself, I propose something like "Öffnen der Verbindung". Thanks, Peter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Peter Schwindt (JIRA 2012-05-21T12:29:41 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36661 <pre> [ https://issues.apache.org/jira/browse/DIR-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny deleted DIR-285: ---------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Emmanuel Lecharny (JIRA 2012-05-20T19:17:40 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36660 <pre> [ https://issues.apache.org/jira/browse/DIR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny deleted DIR-284: ---------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Emmanuel Lecharny (JIRA 2012-05-20T19:15:40 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36659 <pre>musa jadeja created DIR-285: ------------------------------- Summary: life issues Key: DIR-285 URL: https://issues.apache.org/jira/browse/DIR-285 Project: Directory Issue Type: Improvement Environment: Strong love spells +27764071887 Reporter: musa jadeja Assignee: Alex Karasulu Strong love spells +27764071887 How many times have you: .Been in love with a man who didn't love you back? .Thought your relationship was perfect, and then it fell apart? .Been scared because you didn't know how to fix your crumbling relationship or marriage? Wished you could be smarter about dating? Do you have to be Beautiful to Win a Man's Love? You don't know it yet, but what's been missing is the foundation for a rock-solid relationship. Without a foundation, you're just sitting on sand and the first wave that comes along will wash away everything, no matter how solid you thought it was. .I was married for 29 years. I thought I had a great marriage. Then, he decided we should have an open marriage. Can you imagine? I didn't want to lose my marriage that I valued so much, but there was just no way could I be okay with what he was asking…. So here's what I did. Instead of licking my wounds, I went into action… I Used Dr. Jadeja love spell we are now back again… Becky Sanders, Australia. Call Dr Jadeja on +27764071887 Skype, drjadeja99 Yahoo messenger, drjadeja99 drjadeja99-/E1597aS9LQAvxtiuMwx3w&lt; at &gt;public.gmane.org lostlove-psychic.webs.com -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> musa jadeja (JIRA 2012-05-20T17:53:41 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36658 <pre>musa jadeja created DIR-284: ------------------------------- Summary: Strong love spells +27764071887 Key: DIR-284 URL: https://issues.apache.org/jira/browse/DIR-284 Project: Directory Issue Type: Improvement Environment: Strong love spells +27764071887 Reporter: musa jadeja Assignee: Alex Karasulu Strong love spells +27764071887 How many times have you: .Been in love with a man who didn't love you back? .Thought your relationship was perfect, and then it fell apart? .Been scared because you didn't know how to fix your crumbling relationship or marriage? Wished you could be smarter about dating? Do you have to be Beautiful to Win a Man's Love? You don't know it yet, but what's been missing is the foundation for a rock-solid relationship. Without a foundation, you're just sitting on sand and the first wave that comes along will wash away everything, no matter how solid you thought it was. .I was married for 29 years. I thought I had a great marriage. Then, he decided we should have an open marriage. Can you imagine? I didn't want to lose my marriage that I valued so much, but there was just no way could I be okay with what he was asking…. So here's what I did. Instead of licking my wounds, I went into action… I Used Dr. Jadeja love spell we are now back again… Becky Sanders, Australia. Call Dr Jadeja on +27764071887 Skype, drjadeja99 Yahoo messenger, drjadeja99 drjadeja99-/E1597aS9LQAvxtiuMwx3w&lt; at &gt;public.gmane.org lostlove-psychic.webs.com -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> musa jadeja (JIRA 2012-05-20T17:53:41 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36657 <pre>Hi guys, I was mostly MIA the few past days, and will come back on monday afternoon. There are a few things pendng that require some action : - ApacheDS 2.0.0-M7 has been released, and we have to update the site and make the announcement - I'm fighting with the txn branch merge with trunk. Despite the fact that I have merged trunk into this branch mor ethan once, this is still a challenge. I'll propably spend most of my monday on that - I still have to review Göktürk mail about OSGi. Will do that asap. - We should decide how to fix the issue we have with cursor that aren't closed. This one is absolutly critical. Right now, the proposed solution is to read forward all the entries, and to store them either in memory, or on disk, before sending them to the client. Frankly, I don't see any better solution atm. At some point, we also have to discuss what we should put into M8. IMO, OSGification of the server should be included as soon as it's done, and we should then cut a milestone. That would close one important step toward 2.0. When done, I do think we should address the JIRAs we have, before piling up some new features. Otherwise, we still have some important features to add in the next few milestones : - Disaster Recovery System : what should the server do if it's brutally stopped ? - MMR replication : M/S replication is supposed to work (more or less, it seems wehave issues with subentries : to be checked) - Triggers and SP must be reviexed and fixed: currently, it does not work anymore due to the API modification (we aren't using JNDI anymore) - Administrative Model is still incomplete. We have to get it working with the complete X500 features - Caches must be improved - Kerberos needs a *lot* of love ! - HBase backend must be improved and included into trunk - We have to test JDBM3 There are probably more items I have not mentionned here, feel free to add what you have in mind. Thanks ! </pre> Emmanuel Lécharny 2012-05-20T16:32:28 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36656 <pre> [ https://issues.apache.org/jira/browse/DIRSERVER-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Göktürk Gezer deleted DIRSERVER-1672: ------------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Göktürk Gezer (JIRA 2012-05-19T00:10:32 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36655 <pre> [ https://issues.apache.org/jira/browse/DIRSERVER-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Göktürk Gezer deleted DIRSERVER-1671: ------------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Göktürk Gezer (JIRA 2012-05-19T00:10:31 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36649 <pre>Richard Lowden created DIRSERVER-1727: ----------------------------------------- Summary: LDAP Searches against boolean attributes with booleanMatch equality never return matches Key: DIRSERVER-1727 URL: https://issues.apache.org/jira/browse/DIRSERVER-1727 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M6 Reporter: Richard Lowden If you carry out a search trying to match on a boolean attribute (syntax: 1.3.6.1.4.1.1466.115.121.1.7) and an equality matching rule of booleanMatch then searching for classes with the attribute value equalling TRUE or FALSE never return results. Changing the equality matching rule on the attribute to caseIgnoreMatch will return results. Used to work in 1.5.7 but no longer works in 2.0.0-M6. To recreate try searching ober the ou=config entry for "ads-enabled = TRUE" as per the example below from the search logs, which should return "ads-directoryServiceId=default,ou=config" but returns no results. #!SEARCH REQUEST (667) OK #!CONNECTION ldap://localhost:10389 #!DATE 2012-05-16T16:34:51.265 # LDAP URL : ldap://localhost:10389/ou=config?objectClass?sub?(ads-enabled=TRUE) # command line : ldapsearch -H ldap://localhost:10389 -x -D "uid=admin,ou=system" -W -b "ou=config" -s sub -a always -z 1000 "(ads-enabled=TRUE)" "objectClass" # baseObject : ou=config # scope : wholeSubtree (2) # derefAliases : derefAlways (3) # sizeLimit : 1000 # timeLimit : 0 # typesOnly : False # filter : (ads-enabled=TRUE) # attributes : objectClass #!SEARCH RESULT DONE (667) OK #!CONNECTION ldap://localhost:10389 #!DATE 2012-05-16T16:34:51.265 # numEntries : 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Richard Lowden (JIRA 2012-05-16T15:39:02 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36648 <pre>Aleks M created DIRSTUDIO-814: --------------------------------- Summary: eDirectory networkAddress attribute Key: DIRSTUDIO-814 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-814 Project: Directory Studio Issue Type: Improvement Affects Versions: 2.0.0-M3 Reporter: Aleks M Priority: Minor It seems that the eDirectory networkAddress attribute is hard for Studio to read. There are several more attributes that use the same syntax (2.16.840.1.113719.1.1.5.1.12) When looking at a ncpServer object (objectClass=ncpServer) it has several values in that attribute. Studio displays them pretty well, they look like this: 13#l d a p : / / 1 7 2 . 1 6 . 2 4 2 . 7 4 : 6 3 6 Notice the space between each character. I believe its a \u0000 but I'm 100% sure. Anyway selecting a value and pressing CTRL+C gives me: 13#l I.e. only the first four characters up to the first "space". If I double click the value to edit it then Studio displays 13#l in the editor field. If you by accident click anywhere and you don't press ESC then the value will be changed to 13#l It would be nice if doubleclicking the attribute value wouldn't cause Studio to change the value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Aleks M (JIRA 2012-05-16T15:11:03 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36647 <pre>Aleks M created DIRSTUDIO-813: --------------------------------- Summary: Add default value editors for eDirectory Key: DIRSTUDIO-813 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-813 Project: Directory Studio Issue Type: Improvement Affects Versions: 2.0.0-M3 Reporter: Aleks M Priority: Minor Is it possible for Studio to open these eDirectory attributes in the correct editor by default so that I don't have to add them manually to Studio preferences on each computer? GUID = Entry UUID Editor userCertificate = Certificate Editor nDSPKIPublicKeyCertificate = Certificate Editor cACertificate = Certificate Editor ndsCrossCertificatePair = Certificate Editor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Aleks M (JIRA 2012-05-16T14:57:02 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36646 <pre>Aleks M created DIRSTUDIO-812: --------------------------------- Summary: Error while performing search Key: DIRSTUDIO-812 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-812 Project: Directory Studio Issue Type: Bug Affects Versions: 2.0.0-M3 Environment: Windows 7 SP1 64-bit Reporter: Aleks M I've come across a a directory where they have alot of objects named with #, e.g. 12345678911#38SA Sometimes the LDAP search fails in Studio while it works in other tools. If I search for something like this: (workforceID=200511230101) I should get two DNs back, Studio failes after retrieving the first one named 200511230101, the other is named 200511230101#38SA and Studio gives me this error: Error while performing search - expecting EOF, found '38' org.apache.directory.shared.ldap.model.exception.LdapInvalidDnException: expecting EOF, found '38' at org.apache.directory.shared.ldap.model.name.ComplexDnParser.parseDn(ComplexDnParser.java:56) at org.apache.directory.shared.ldap.model.name.Dn.parseInternal(Dn.java:1321) at org.apache.directory.shared.ldap.model.name.Dn.&lt;init&gt;(Dn.java:282) at org.apache.directory.shared.ldap.model.name.Dn.&lt;init&gt;(Dn.java:208) at org.apache.directory.studio.ldapbrowser.core.utils.JNDIUtils.getDn(JNDIUtils.java:46) at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.searchAndUpdateModel(SearchRunnable.java:329) at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.run(SearchRunnable.java:192) at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: line 1:16: expecting EOF, found '38' at antlr.Parser.match(Parser.java:211) at org.apache.directory.shared.ldap.model.name.AntlrDnParser.relativeDistinguishedNames(AntlrDnParser.java:338) at org.apache.directory.shared.ldap.model.name.ComplexDnParser.parseDn(ComplexDnParser.java:52) ... 8 more expecting EOF, found '38' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Aleks M (JIRA 2012-05-16T14:51:02 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36644 <pre>Richard Lowden created DIRSERVER-1726: ----------------------------------------- Summary: DefaultPasswordValidator always throws PasswordPolicyException when consecutive non-letter chars are in RDN Key: DIRSERVER-1726 URL: https://issues.apache.org/jira/browse/DIRSERVER-1726 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M6 Reporter: Richard Lowden When adding an entry with a userPassword attribute and the entry RDN contains two non-letter characters in a row (such as cn=test1-EHIbwFwGAZ1BDgjK7y7TUQ&lt; at &gt;public.gmane.org) then a CONSTRAINT_VIOLATION error is always received with the message "Password shouldn't contain parts of the username" regardless of what password you enter. If you remove the "1" character or the "&lt; at &gt;" character then the entry will be created successfully Believe the issue is caused by the regex expressions used within org.apache.directory.server.core.authn.ppolicy.DefaultPasswordValidator, as the String array of tokens will contain an empty string when two non-letter chars are together ("1&lt; at &gt;" in this case). Full error message is: Error while creating entry - [LDAP: error code 19 - CONSTRAINT_VIOLATION: failed for MessageType : ADD_REQUES javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 19 - CONSTRAINT_VIOLATION: failed for MessageType : ADD_REQUEST Message ID : 240 Add Request : Entry dn[n]: cn=test1-EHIbwFwGAZ1BDgjK7y7TUQ&lt; at &gt;public.gmane.org,o=unitTest objectClass: inetOrgPerson objectClass: organizationalPerson objectClass: person objectClass: top sn: Smith userPassword: '0x70 0x61 0x73 0x73 0x77 0x6F 0x72 0x64 0x31 0x31 ' cn: test1-EHIbwFwGAZ1BDgjK7y7TUQ&lt; at &gt;public.gmane.org : Password shouldn't contain parts of the username]; remaining name 'cn=test1-EHIbwFwGAZ1BDgjK7y7TUQ&lt; at &gt;public.gmane.org,o=unitTest' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source) at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source) at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source) at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(Unknown Source) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(Unknown Source) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(Unknown Source) at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper$4.run(JNDIConnectionWrapper.java:658) at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.runAndMonitor(JNDIConnectionWrapper.java:1272) at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.checkConnectionAndRunAndMonitor(JNDIConnectionWrapper.java:1203) at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.createEntry(JNDIConnectionWrapper.java:704) at org.apache.directory.studio.ldapbrowser.core.jobs.CreateEntryRunnable.createEntry(CreateEntryRunnable.java:226) at org.apache.directory.studio.ldapbrowser.core.jobs.CreateEntryRunnable.run(CreateEntryRunnable.java:117) at org.apache.directory.studio.connection.ui.RunnableContextRunner$1.run(RunnableContextRunner.java:113) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) [LDAP: error code 19 - CONSTRAINT_VIOLATION: failed for MessageType : ADD_REQUEST Message ID : 240 Add Request : Entry dn[n]: cn=test1-EHIbwFwGAZ1BDgjK7y7TUQ&lt; at &gt;public.gmane.org,o=unitTest objectClass: inetOrgPerson objectClass: organizationalPerson objectClass: person objectClass: top sn: Smith userPassword: '0x70 0x61 0x73 0x73 0x77 0x6F 0x72 0x64 0x31 0x31 ' cn: test1-EHIbwFwGAZ1BDgjK7y7TUQ&lt; at &gt;public.gmane.org : Password shouldn't contain parts of the username] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Richard Lowden (JIRA 2012-05-16T13:39:02 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36642 <pre>Josef Cacek created DIRKRB-85: --------------------------------- Summary: &lt; at &gt;CreateKdcServer should include searchBaseDn attribute Key: DIRKRB-85 URL: https://issues.apache.org/jira/browse/DIRKRB-85 Project: Directory Kerberos Issue Type: Bug Reporter: Josef Cacek Assignee: Emmanuel Lecharny Priority: Critical CreateKdcServer annotation doesn't contain searchBaseDn, so the KdcServer instance created by calling org.apache.directory.server.factory.ServerAnnotationProcessor.getKdcServer(DirectoryService, int) can't be used for domain other than "example.com". The KdcServer created from &lt; at &gt;CreateKdcServer configuration searches users always in "ou=users,dc=example,dc=com" (see to KdcServer constructor). For a LDAP server it's possible to change the search domain after the retrieving an instance from ServerAnnotationProcessor, but it doesn't work for the KdcServer, because the original value is already stored in a DirectoryPrincipalStore instance created by KdcServer.start() method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Josef Cacek (JIRA 2012-05-16T08:55:02 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36640 <pre>Hi Everyone, As i told you in OSGI branch update, JDBM is so immutable in runtime. Almost every setter calls checkInitialized() method first which throws an exception when its already initialized. We have to change that behavior in as much aspects of it as we can. Otherwise there is no point in going into OSGI. However i can't always be sure what my changes might lead on runtime. I need some serious help here, especially from those are actively working on JDBM, otherwise i'll jump into trial and error cycle which will probably last long. Here is the current configuration points for JdbmPartition: - cacheSize(int) - optimizerEnabled(boolean) - partitionPath(File) - suffixDn(Dn) - syncOnWrite(boolean) - indexedAttributes(List&lt;Index&gt;) Currently none of them is reconfigurable, once the partition is initialized. However i need to know which are actually reconfigurable among these ones. And which are not really reconfigurable and why? Every reconfiguration will invoke some setter method at desired configuration point. So i guess we can make this reconfigurations work actually based on it's initialized or not, rather than throwing an exception blindly. For your information, as we have the lifecycle control capability of components created from within ApacheDS, we can implement some fancy stuff. Like re-instantiating a component when one of its immutable property is changed, or stop it and remove from DirectoryService when one of its immutable property is changed to prevent accepting operations while reconfiguring. These migtht be implemented in case there is " no possibility! " to handle reconfigurations in live and initialized JdbmPartition reference. I appreciate every single idea on this matter ! Thanks, Gokturk </pre> Göktürk Gezer 2012-05-16T03:58:10 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36636 <pre>Hi guys, just FYI, I'm currently trying to merge the txn branch into trunk. Not sure Il'll be able to do it completely today, but I'll try. Thanks ! </pre> Emmanuel Lécharny 2012-05-15T09:21:59 http://comments.gmane.org/gmane.comp.apache.incubator.directory.devel/36635 <pre></pre> houmles (JIRA 2012-05-15T07:24:44 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.incubator.directory.devel