Re: [Fortress] Mailing list
Looks good to me. Thanks Emmanuel ! Regards, Pierre-Arnaud On 17 Oct 2014, at 07:59, Emmanuel Lécharny elecha...@gmail.com wrote: Le 16/10/14 09:46, Emmanuel Lécharny a écrit : Hi guys, I wonder if we should create a new mailing list for Fortress ? At least, one for users ? wdyt ? Ok, I have requested the mailing list fortr...@directory.apache.org to be created. I'll inform you when it's done. I have set Kiran, Pierre-Arnaud, Stefan and me as moderators. Please feel free to tell me if you want to be added or removed from the moderator list. Thanks !
Re: [Fortress] Mailing list
+1 Regards, Pierre-Arnaud On 16 Oct 2014, at 09:46, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, I wonder if we should create a new mailing list for Fortress ? At least, one for users ? wdyt ?
Re: [Fortress] Git import and JIRA migration on their way
Thanks for the update Emmanuel. Are you sure it is possible to request the creation of a GIT repo for Fortress while the rest of the Directory project is still on SVN? Regards, Pierre-Arnaud On 15 Oct 2014, at 16:27, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, I have requested teh import of the current Git repo and the migration of the existing JIRA : https://issues.apache.org/jira/browse/INFRA-8470 and https://issues.apache.org/jira/browse/INFRA-8483 It might take a few days. Thanks !
Re: svn commit: r1631698 - in /directory/site/trunk/content: images/team/pierresmits.png team.mdtext
Thanks Emmanuel. :) Regards, Pierre-Arnaud On 16 Oct 2014, at 10:41, Emmanuel Lécharny elecha...@gmail.com wrote: Le 16/10/14 10:32, Pierre Smits a écrit : Thanks, Pierre-Arnoud, Could you grant me committer permissions to the issues regarding the website in Jira. So that I can assign to myself the ones that I create? I have added you to the list of committers on JIRA, you should now be able to assign you to a JIRA. Just let me know if you still have some issue ! Thanks !
[jira] [Commented] (DIR-308) Improve website header to include meta stuff for better SEO
[ https://issues.apache.org/jira/browse/DIR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173662#comment-14173662 ] Pierre-Arnaud Marcelot commented on DIR-308: Good idea. The best would be to take advantage of the headers section in our *.mdtext files for the website. Currently we use 'title' and 'notice'. Only 'title' is being used on the website. We could add extra ones for description, keywords, etc. Doing so, we would be able to specify that on a per page basis. Improve website header to include meta stuff for better SEO --- Key: DIR-308 URL: https://issues.apache.org/jira/browse/DIR-308 Project: Directory Issue Type: Improvement Components: miscellaneous Reporter: Pierre Smits Assignee: Alex Karasulu Currently we don't have any SEO enhancements, (meta tags) in the header of our website. Stuff like: * description * keywords * etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DIR-308) Improve website header to include meta stuff for better SEO
[ https://issues.apache.org/jira/browse/DIR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIR-308: --- Attachment: articles.mdtext header.html Example files attached. Improve website header to include meta stuff for better SEO --- Key: DIR-308 URL: https://issues.apache.org/jira/browse/DIR-308 Project: Directory Issue Type: Improvement Components: miscellaneous Reporter: Pierre Smits Assignee: Alex Karasulu Attachments: articles.mdtext, header.html Currently we don't have any SEO enhancements, (meta tags) in the header of our website. Stuff like: * description * keywords * etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [Fortress] Git import and JIRA migration on their way
Perfect, I thought that the whole project had to use the same version control system. :) Regards, Pierre-Arnaud On 16 Oct 2014, at 14:04, Emmanuel Lécharny elecha...@gmail.com wrote: Le 16/10/14 14:00, Pierre-Arnaud Marcelot a écrit : Thanks for the update Emmanuel. Are you sure it is possible to request the creation of a GIT repo for Fortress while the rest of the Directory project is still on SVN? Why not ? Switching the other projects to Git is probably a bit premature, but we can perfectly use a dedicated git repo for another project.
Re: svn commit: r1631698 - in /directory/site/trunk/content: images/team/pierresmits.png team.mdtext
Congratulations, as well, on your first commit at the Directory Project, Pierre! Cheers, Pierre-Arnaud On 14 Oct 2014, at 11:36, pierresm...@apache.org wrote: Author: pierresmits Date: Tue Oct 14 09:36:41 2014 New Revision: 1631698 URL: http://svn.apache.org/r1631698 Log: Adjusted details of committer Pierre Smits, including photo and website Added: directory/site/trunk/content/images/team/pierresmits.png (with props) Modified: directory/site/trunk/content/team.mdtext Added: directory/site/trunk/content/images/team/pierresmits.png URL: http://svn.apache.org/viewvc/directory/site/trunk/content/images/team/pierresmits.png?rev=1631698view=auto == Binary file - no diff available. Propchange: directory/site/trunk/content/images/team/pierresmits.png -- svn:mime-type = application/octet-stream Modified: directory/site/trunk/content/team.mdtext URL: http://svn.apache.org/viewvc/directory/site/trunk/content/team.mdtext?rev=1631698r1=1631697r2=1631698view=diff == --- directory/site/trunk/content/team.mdtext (original) +++ directory/site/trunk/content/team.mdtext Tue Oct 14 09:36:41 2014 @@ -44,7 +44,7 @@ Notice: Licensed to the Apache Software | Jan Rellermeyer |Committer| |[](http://people.inf.ethz.ch/rjan)|| | Lucas Thiesen |Committer | Martin Alderson |Committer -| Pierre Smits |Committer +| Pierre Smits |Committer||[](http://www.orrtiz.com)|| | Selcuk Aya |Committer | Shawn McKinney |Committer||[](http://symas.com/products/symas-enforcement-foundry/)||
Re: [VOTE] Release Apache Mavibot 1.0.0-M5
[X] +1 Release Mavibot 1.0.0-M5 Regards, Pierre-Arnaud On 29 Jun 2014, at 18:02, Emmanuel Lécharny elecha...@gmail.com wrote: Hi ! This is the first release of Apache Mavibot, the MVCC BTree in Java ! This milestone is the fifth step toward a complete MVCC implementation. The main added features are : - bulk load implementation - subtrees handling Some other fixes have been applied, and some preliminary work toward transaction support and free pages management. The tests done on bulk load shows good performances so far : we can load 30 000 entries in around 20 seconds (1500/s). So let's vote now ! The revision : http://svn.apache.org/r1606519 The SVN tag: https://svn.apache.org/repos/asf/directory/mavibot/tags/1.0.0-M5/ The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-1006/ Please cast your votes: [ ] +1 Release Mavibot 1.0.0-M5 [ ] 0 abstain [ ] -1 Do not release Mavibot 1.0.0-M5 Emmanuel
Re: [VOTE] Release of LDAP API 1.0.0-M23
[X] +1 Release Shared/LDAP API 1.0.0-M23 Regards, Pierre-Arnaud On 30 Jun 2014, at 07:32, Emmanuel Lécharny elecha...@gmail.com wrote: Hi, This is a vote for the 23th milestone of the 1.0.0 LDAP API/Shared, 1.0.0-M23. It's a bug fix release. It contains a few bug fixes and improvements, and some feature added by Lucas (Templating for LdapConnection) : Bugs * [DIRAPI-190 https://issues.apache.org/jira/browse/DIRAPI-190] - Search request time limit should override connection timeout * [DIRAPI-192 https://issues.apache.org/jira/browse/DIRAPI-192] - Rdn.escapeValue() should not escape unicode characters Improvement --- * [DIRAPI-168 https://issues.apache.org/jira/browse/DIRAPI-168] - Create an LdapConnectionFactory that is not pooled to create LdapConnection objects for an LdapConnectionConfig The revision : http://svn.apache.org/r1606612 The SVN tag: http://svn.apache.org/repos/asf/directory/shared/tags/1.0.0-M23 The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-1007 Please cast your votes: [ ] +1 Release Shared/LDAP API 1.0.0-M23 [ ] 0 abstain [ ] -1 Do not release Shared/LDAP API 1.0.0-M23 Emmanuel -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: [VOTE] Release of Apache Directory Server 2.0.0-M17
[X] +1 : release ApacheDS 2.0.0-M17 Regards, Pierre-Arnaud On 30 Jun 2014, at 16:53, Emmanuel Lécharny elecha...@gmail.com wrote: A small mistake : - SVN tag : http://svn.apache.org/r1606636 Le 30/06/2014 16:44, Emmanuel Lécharny a écrit : Hi, it's time for a new release of ApacheDS, version 2.0.0-M17. Still a bug fix release, but we added the bulk_loader feature in a separate module. The list of fixed bugs and improvments is the following : Bugs * [DIRSERVER-1971 https://issues.apache.org/jira/browse/DIRSERVER-1971] - Allow any sort of modification on operational attriutes while processing replication events in the consumer * [DIRSERVER-1976 https://issues.apache.org/jira/browse/DIRSERVER-1976] - JDBM partition is not building new indices added to the configuration * [DIRSERVER-1979 https://issues.apache.org/jira/browse/DIRSERVER-1979] - Adding child entries can't be found after restarting server * [DIRSERVER-1980 https://issues.apache.org/jira/browse/DIRSERVER-1980] - pwdReset isn't replicated properly * [DIRSERVER-1982 https://issues.apache.org/jira/browse/DIRSERVER-1982] - Couldn't see KDC Principal field under Kerberos settings * [DIRSERVER-1986 https://issues.apache.org/jira/browse/DIRSERVER-1986] - Delegated authentication fails when password policy is enabled New Features [DIRSERVER-1967 https://issues.apache.org/jira/browse/DIRSERVER-1967] - Add the support for the WhoAmI extended operation Here are the associated links : ApacheDS 2.0.0-M17 -- - SVN tag : http://svn.apache.org/r1575355 https://svn.apache.org/repos/asf/directory/apacheds/tags/2.0.0-M17/ - Nexus repository: https://repository.apache.org/content/repositories/orgapachedirectory-1008/ - Distribution packages: http://people.apache.org/~elecharny [ ] +1 : release ApacheDS 2.0.0-M17 [ ] ± 0 : I don't care [ ] -1 : No, don't release ApacheDS 2.0.0-M17 -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: Git ?
On 26 Jun 2014, at 20:41, Stefan Seelmann m...@stefan-seelmann.de wrote: On 06/26/2014 06:35 PM, Emmanuel Lécharny wrote: Hi guys, since the inception of the project, we are using Subversion (well, at the very begining, it was on CVS). We are all used to it, but I'm quite sure that most of us are also using Git on a side project. I'm a bit fed up of switching from Git to Svn, and back. I work a few weeks using SVN, then when I come back to Git, I have to read the doco again, because I don't remember all the fancy commands to use it efficiently. The very same things after a few weeks using Git. What about moving the full project to git ? Do you think it would be too much of a pain ? I'm ok with it, but I can also live with svn. Same for me. Although I’m working more on Git these days, I’m still comfortable with SVN. If we move we need to discuss the repo structure. Should we put the whole svn into a single git repo (I think no) or create a git repo per subproject (yes IMHO)? +1 for me too. We have many subprojects now (shared/api, mavibot, jdbm, server, studio, escimo) which deserve its own git repo. What about the smaller repos (parent-project, buildtools (is this still required?) clients). I think sandbox and deceased don't need to be migrated, as SVN will still be available read-only. +1. Sounds reasonable too me. I have a small concern regarding the studio repo, as it includes binaries from various Eclipse versions, the .git directory of the current git-mirror is 700 MB. That means when cloning the studio git repo on has to download the full 700 MB. That’s indeed a big concern. I’d be tempted to have that in another repository, that we can even use online as a real maven repository. Without requiring us to have it checked out on our computers. Other things to consider (not a complete list) * Is there a mailing list integration for commits * Maven release should work with git, update of scm section in POMs is required * Is there are a git alternative to viewvc, or just use github instead? +1 on those questions. Mina has move to git a few years (months) ago I guess, Emmanuel, are all these things available yet? Regards, Pierre-Arnaud Kind Regards, Stefan
[jira] [Commented] (DIRSTUDIO-937) No password confirmation while changing it
[ https://issues.apache.org/jira/browse/DIRSTUDIO-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14031964#comment-14031964 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-937: -- I just added the missing french translation. No password confirmation while changing it -- Key: DIRSTUDIO-937 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-937 Project: Directory Studio Issue Type: Improvement Environment: Apache Directory Studio plugin 2.0.0 in Eclipse Kepler Reporter: Askat Asanaliev Assignee: Stefan Seelmann Priority: Minor Fix For: 2.0.0-M9 When I change my password there is only one field new password. There is no any confirmation field. If I enter a new password with a typo I will not be able to log in next time. I have to ask an administrator to change my password again. With the confirmation field such case can be eliminated. -- This message was sent by Atlassian JIRA (v6.2#6252)
ApacheCon CFP closes June 25
Dear Apache Directory enthusiast, As you may be aware, ApacheCon will be held this year in Budapest, on November 17-23. (See http://apachecon.eu for more info.) The Call For Papers for that conference is still open, but will be closing soon. We need you talk proposals, to represent Apache Directory at ApacheCon. We need all kinds of talks - deep technical talks, hands-on tutorials, introductions for beginners, or case studies about the awesome stuff you're doing with Apache Directory. Please consider submitting a proposal, at http://events.linuxfoundation.org//events/apachecon-europe/program/cfp Thanks! Pierre-Arnaud Marcelot (on behalf of the Apache Directory PMC)
Re: [VOTE] Release of Apache Directory Server 2.0.0-M16, take 2
[X] +1 : release ApacheDS 2.0.0-M16 Regards, Pierre-Arnaud On 10 Mar 2014, at 15:39, Emmanuel Lécharny elecha...@gmail.com wrote: Hi, This is a replacement for the release done last saturday, as the two following critical bugs were found and fixed : Bugs [DIRSERVER-1962] - Replication Consumer Enabled checkbox not working [DIRSERVER-1963] - Add contextCSN attribute to the list of ignored attributes in ReplicationConsumerImpl I restart the vote, the original contain remains the same : it's time for a long expected release of ApacheDS, version 2.0.0-M16. We postponed this release expecting to get a release candidate out, but at this point, we are depending on Mavibot, and it's not ready. This release fixes many critical bugs. We also have done some cleanup in the Kerberos server. The list of fixed bugs and improvments is the following : Bugs [DIRSERVER-1092] - org.apache.directory.server.dns.store.RecordStore not support ordered multiple resource record answers [DIRSERVER-1252] - Server tools dump command broken due to use of old paths [DIRSERVER-1412] - Modifying the schema with more than one mod may fail [DIRSERVER-1471] - Providing a right fix for DIRSERVER-1459 [DIRSERVER-1761] - Unable to use external keystore for SSL [DIRSERVER-1810] - Test case org.apache.directory.server.replication.ClientServerReplicationIT.testModDn() fails permanently [DIRSERVER-1845] - Sporadic failure on CollectivAttributeServiceIT [DIRSERVER-1855] - java.lang.IllegalStateException: Can't overwrite cause at org.apache.directory.server.core.authz.GroupCache.initialize(GroupCache.java:190) [DIRSERVER-1860] - Invalid DN in returned entry [DIRSERVER-1870] - Persistent control is not decoded properly [DIRSERVER-1873] - Searching on member attribute (multivalued) for groups is not working as expected [DIRSERVER-1884] - Incorrect length specified in PaswordUtil.splitCredentials [DIRSERVER-1885] - The JDBM index cache configuration is not used at all [DIRSERVER-1888] - Some pwdPolicy schema AT are incorrect [DIRSERVER-1894] - Multi-Master replicated startup does not complete [DIRSERVER-1900] - Password hashing interceptor is not encrypting the passwords [DIRSERVER-1902] - Concurrent reads cause LDAP:Error 80, LDAP: Error 1 and LDAP: error code 49 errors [DIRSERVER-1905] - KeytabDecoder should use '/' instead of '\' to separate principal name components [DIRSERVER-1906] - We still store entryUUID associated with 'top' in the OC index [DIRSERVER-1909] - Integer cannot be cast to java.lang.Long in JdbmTable prevents service start [DIRSERVER-1911] - Incorrect installation presumption toward user naming convention [DIRSERVER-1917] - Class Cast Exception when doing paged search [DIRSERVER-1921] - Indexes dont work on distinguishedNameMatch attributeType [DIRSERVER-1922] - Not Operator in Ldap Filter on Indexed Attributes [DIRSERVER-1928] - PasswordPolicy should be ignored from Admin session [DIRSERVER-1932] - Password policy pwdMinAge check should check for required reset [DIRSERVER-1948] - NPE in AuthenticationInterceptor when password policy is in place and user does not have a pwdChangedTime [DIRSERVER-1953] - entryDn attribute is not returned when requested along with wildcard attribute symbol * [DIRSERVER-1954] - Second startup of an embedded server fails (after an ungraceful shutdown of the first startup) [DIRSERVER-1955] - Directory Apacheds sends wrong empty response for password policy request [DIRSERVER-1957] - chpass/passwd failure (Linux) [DIRSERVER-1959] - Certificates corruption during replication [DIRSERVER-1961] - Searches wth Object level scope and non-existing attribute assertion in filter are not working Improvements [DIRSERVER-1081] - Injecting more information in the opContext structure [DIRSERVER-1294] - Add size() and hasNext() methods to cursors [DIRSERVER-1338] - Allow non-Jdbm schema partition [DIRSERVER-1460] - Add locale to configuration [DIRSERVER-1534] - Improving implementation of loading LDIF files during startup [DIRSERVER-1601] - New index to add : PrescriptiveACI, member, uniqueMember [DIRSERVER-1634] - Add a DN cache for Stores [DIRSERVER-1676] - Provide a set of error codes along with an AuthenticationException to indicate its root cause. [DIRSERVER-1716] - Add a ParentIdAndRdn cache [DIRSERVER-1920] - Refactor DefaultDirectoryServiceFactory/DefaultDirectoryService for extensability [DIRSERVER-1926] - Supply Entry to PasswordValidator instead of username [DIRSERVER-1935] - Include password policy control in the password modify extended operation response if requested New Features [DIRSERVER-264] - Add Support for Sort Control [DIRSERVER-265] - In-memory backend storage support
Re: Result [VOTE] Release of LDAP API 1.0.0-M21
I missed this vote but obviously it has my late +1. Congrats on this new version being released! :) Regards, Pierre-Arnaud On 12 Mar 2014, at 09:10, Emmanuel Lécharny elecha...@gmail.com wrote: Hi, I'm closing this vote, we received 4 +1 : - Felix - Kiran - Stefan and me I'll update the site and move the released package to the servers. I'll do the annoncement tomorrow. Le 3/8/14 4:48 PM, Emmanuel Lécharny a écrit : Hi, This is a vote for the 21th milestone of the 1.0.0 LDAP API/Shared, 1.0.0-M21. It's a bug fix release, and it will be followed by a release of ApachedDS 2.0.0-M16 this afternoon. It contains a few bug fixes and improvements : Bugs * [DIRAPI-126 https://issues.apache.org/jira/browse/DIRAPI-126] - Timeout Exception on bind while pwdExpireWarning period * [DIRAPI-128 https://issues.apache.org/jira/browse/DIRAPI-128] - FilterEncoder.format() should accept String varargs * [DIRAPI-152 https://issues.apache.org/jira/browse/DIRAPI-152] - Attribute.toString() method appends newline * [DIRAPI-157 https://issues.apache.org/jira/browse/DIRAPI-157] - Calling the add() method with a multi-value attribute and a null value throws an NPE * [DIRAPI-160 https://issues.apache.org/jira/browse/DIRAPI-160] - DSML engine is not setting the 'requestID' value in BatchResponse when output stream instance is provided * [DIRAPI-161 https://issues.apache.org/jira/browse/DIRAPI-161] - Timeout does not apply to connect method * [DIRAPI-173 https://issues.apache.org/jira/browse/DIRAPI-173] - When using TLS and multiple binds, LdapNetworkConnection attempts to start TLS multiple times * [DIRAPI-176 https://issues.apache.org/jira/browse/DIRAPI-176] - LDIFReader does not accept empty DN (rootDSE) Improvements * [DIRAPI-137 https://issues.apache.org/jira/browse/DIRAPI-137] - Add Control support for RFC 2891 - LDAP Control Extension for Server Side Sorting of Search Results http://www.faqs.org/rfcs/rfc2891.html * [DIRAPI-153 https://issues.apache.org/jira/browse/DIRAPI-153] - Implement efficient reuse of schema loading * [DIRAPI-159 https://issues.apache.org/jira/browse/DIRAPI-159] - Add a method to set a SchemaManager in LdapConnection * [DIRAPI-169 https://issues.apache.org/jira/browse/DIRAPI-169] - Formalize the contract of PasswordPolicyResponse by stating that -1 is returned if no value is set. * [DIRAPI-170 https://issues.apache.org/jira/browse/DIRAPI-170] - Allow StandaloneLdapApiServices to be configured without system properties * [DIRAPI-175 https://issues.apache.org/jira/browse/DIRAPI-175] - LdifReader should handle empty New Feature --- * [DIRAPI-143 https://issues.apache.org/jira/browse/DIRAPI-143] - Add Controls to support server-side sorting The revision : http://svn.apache.org/r1574930 The SVN tag: http://svn.apache.org/repos/asf/directory/shared/tags/1.0.0-M21 The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-1000 Please cast your votes: [ ] +1 Release Shared/LDAP API 1.0.0-M21 [ ] 0 abstain [ ] -1 Do not release Shared/LDAP API 1.0.0-M21 Emmanuel -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: Result [VOTE] Release Apache Mavibot 1.0.0-M4
Same comment as previous mail. Great to see Mavibot continue to move forward! :) Regards, Pierre-Arnaud On 12 Mar 2014, at 09:10, Emmanuel Lécharny elecha...@gmail.com wrote: Hi, I'm closing this vote, we received 4 +1 : - Felix - Kiran - Stefan and me I'll update the site and move the released package to the servers. I'll do the annoncement tomorrow. Le 3/9/14 8:28 AM, Emmanuel Lécharny a écrit : Hi ! This is the forth release of Apache Mavibot, the MVCC BTree in Java ! This version brings some new improvements in the API and the performances. The In-memory and Persisted B-trees classes have been moved into the same package, to avoid exposing the methods to the external world. We also have shared the common methods. Some specific exceptions have been created. This is by far not the latest milestone, the next one will bring major changes : revisions support, transaction support. ApacheDS has already been tested with Mavibot 1.0.-M4-SNAPSHOT. Here are the list of fixed issues : Bug --- [MAVIBOT-20] - Btree created with the duplicateValues flag to false still accept duplicate values Improvements [MAVIBOT-25] - Don't update the RMHeader for each free page we get [MAVIBOT-27] - Aggregate the Persisted and InMemory common methods [MAVIBOT-28] - Move the Persited and InMemory classes into the same package [MAVIBOT-29] - Use a BtreeFactory to create BTrees [MAVIBOT-30] - Replace the RuntimeException by specific exceptions [MAVIBOT-33] - Serializer and comparator should be static instances So let's vote now ! The revision : http://svn.apache.org/r1574993 The SVN tag: http://svn.apache.org/repos/asf/directory/mavibot/tags/1.0.0-M4/ The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-1001/ Please cast your votes: [ ] +1 Release Mavibot 1.0.0-M4 [ ] 0 abstain [ ] -1 Do not release Mavibot 1.0.0-M4 -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[jira] [Commented] (DIRSTUDIO-971) connections.xml should not be globally-readable
[ https://issues.apache.org/jira/browse/DIRSTUDIO-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13878838#comment-13878838 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-971: -- Indeed, see DIRSTUDIO-901. https://issues.apache.org/jira/browse/DIRSTUDIO-901 connections.xml should not be globally-readable --- Key: DIRSTUDIO-971 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-971 Project: Directory Studio Issue Type: Bug Components: studio-connection Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Linux Reporter: Andrew Findlay Connection parameters are stored in the file connections.xml This can include bind DNs and passwords, which are stored in clear text. The file is globally-readable, exposing these passwords to great risk. Another bug notes that encrypted storage would be better, but please at least set the file mode so that it can only be read by its owner. The file is re-created every time a connection is edited, so changing the file mode by hand does not solve the problem. A possible workaround for Linux is: chmod 700 ~/.ApacheDirectoryStudio -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (DIRAPI-85) Provide a class allowing 'parent-first' sorting of entries from a search result
[ https://issues.apache.org/jira/browse/DIRAPI-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13857373#comment-13857373 ] Pierre-Arnaud Marcelot commented on DIRAPI-85: -- Awesome Kiran! :) Provide a class allowing 'parent-first' sorting of entries from a search result --- Key: DIRAPI-85 URL: https://issues.apache.org/jira/browse/DIRAPI-85 Project: Directory Client API Issue Type: New Feature Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 1.0.0-RC1 Provide a class allowing 'parent-first' sorting of entries from a search result. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (DIRSHARED-134) Missing artifact org.apache.directory.jdbm:apacheds-jdbm2:bundle:2.0.0-M1 when depending on apacheds-server-jndi
[
https://issues.apache.org/jira/browse/DIRSHARED-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822427#comment-13822427
]
Pierre-Arnaud Marcelot commented on DIRSHARED-134:
--
Hi Robert,
Did you try the advice I gave in the first comment?
Adding the 'org.apache.felix:maven-bundle-plugin' plugin should do the trick.
{code}
build
plugins
[...]
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
inheritedtrue/inherited
extensionstrue/extensions
/plugin
[...]
/plugins
/build
{code}
Missing artifact org.apache.directory.jdbm:apacheds-jdbm2:bundle:2.0.0-M1
when depending on apacheds-server-jndi
Key: DIRSHARED-134
URL: https://issues.apache.org/jira/browse/DIRSHARED-134
Project: Directory Shared (Please use DIRAPI instead)
Issue Type: Bug
Affects Versions: 1.0.0-M11
Reporter: Hendy Irawan
Assignee: Pierre-Arnaud Marcelot
Fix For: 1.0.0-M12
Missing artifact org.apache.directory.jdbm:apacheds-jdbm2:bundle:2.0.0-M1
when depending on :
dependency
groupIdorg.apache.directory.server/groupId
artifactIdapacheds-server-jndi/artifactId
version2.0.0-M6/version
/dependency
It should transitively depend on a jar type, not a bundle.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Re: [VOTE] Release Apache Mavibot 1.0.0-M2
[X] +1 Release Mavibot 1.0.0-M2 Successfully built the sources from the tag (tests included). That said, I'm having a failure on project 'apacheds-mavibot-partition' with the current trunk. Maybe it's related, maybe not. I have no idea. Regards, Pierre-Arnaud On 29 oct. 2013, at 10:23, Emmanuel Lécharny elecha...@gmail.com wrote: Hi ! This is the second release of Apache Mavibot, the MVCC BTree in Java ! This milestone is an improvement on the way we handle data in the BTree, more specifically when we reach the memory limits. We switch from using WeakReference to favor a cache, which guarantee way better performances. We also split the API into two different BTree : o in-memory btrees o managed btrees The Managed BTree use the disk to store the data. We also optimized the way we manage tree traversal when we have a lot of page being swapped out of the cache, avoiding a lot of useless deserialization of values and keys, leading to a net gain in performance. ApacheDS has already been tested with Mavibot 1.0.-M2-SNAPSHOT, and it offers pretty good performances compared to JDBM, with a 2.5x faster addition. So let's vote now ! The revision : http://svn.apache.org/r1536610 The SVN tag: https://svn.apache.org/repos/asf/directory/mavibot/tags/1.0.0-M2/ The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-042/ Please cast your votes: [ ] +1 Release Mavibot 1.0.0-M2 [ ] 0 abstain [ ] -1 Do not release Mavibot 1.0.0-M2 -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: [Studio] Try to add a new plugin in Studio
On 29 oct. 2013, at 22:03, Stefan Seelmann m...@stefan-seelmann.de wrote: Hi Laurent, Can you please also post your manifest.mf? Event better if you could publish your plugin sources e.g. to github or send me a private zip archive, then I'll have a look. +1 Any suspicious information in Apache Directory Studio's log file (located at ~/.ApacheDirectoryStudio/.metadata/.log)? Regards, Pierre-Arnaud Kind Regards, Stefan On 10/29/2013 01:22 PM, laurent cop wrote: Hello, - I try to add a new plugin in Studio - I checkout last release on svn repo. Compile my plugin using mvn and then studio using mvn which generates a ApacheDirectoryStudio-win32-x86--SNAPSHOT.zip - I unzip it and got the exe and my plugin in plugindir of extracted archive - When I run the exe, every plugins is loaded except mine :-( - I look in the in Display error log in Configuration tab / in A propos window that my plugin is installed . But in the plugin tab, my plugin is not displayed. - I click on Activate this-plugin when one of it's classes is loaded and use extension point to extend Studio and features. As bellow, I expect a display of a popupMenu when selection of IEntry and display the content of an attributeCertificateAttribute plugin extension point=org.eclipse.ui.popupMenus objectContribution id=rolemanager.popupMenu objectClass=org.apache.directory.studio.ldapbrowser.core.model.IEntry menu id=rolemanager.menu1 label=%menu.label path=additions separator name=group1 /separator /menu action class=org.apache.directory.studio.rolemanager.popup.actions.DelegateRole enablesFor=1 id=rolemanager.delegateAction label=%action.label menubarPath=rolemanager.menu1/group1 tooltip=%action.tooltip /action action class=org.apache.directory.studio.rolemanager.popup.actions.RevokeRole enablesFor=1 id=rolemanager.revokeAction label=%action.label.0 menubarPath=rolemanager.menu1/group1 tooltip=%action.tooltip.0 /action /objectContribution /extension extension point=org.apache.directory.studio.valueeditors valueEditorclass=org.apache.directory.studio.rolemanager.valueeditor.certificate.AttributeCertificateValueEditor icon=resources/icons/certificateeditor.pngname=attribute certificate X509 editor syntax syntaxOID=1.3.6.1.4.1.1466.115.121.1.8 / attribute attributeType=attributeCertificateAttribute / /valueEditor /extension Help appreciated, Thanks
[jira] [Created] (DIRSTUDIO-951) Nightly builds produce faulty Mac OS X distributions (32 and 64 bit)
Pierre-Arnaud Marcelot created DIRSTUDIO-951: Summary: Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) Key: DIRSTUDIO-951 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-951 Project: Directory Studio Issue Type: Bug Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Priority: Critical Attachments: Screen Shot 2013-09-18 at 08.44.31.png Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-951) Nightly builds produce faulty Mac OS X distributions (32 and 64 bit)
[ https://issues.apache.org/jira/browse/DIRSTUDIO-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-951: - Attachment: Screen Shot 2013-09-18 at 08.44.31.png The ZIP file seems buggy. Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) Key: DIRSTUDIO-951 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-951 Project: Directory Studio Issue Type: Bug Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Priority: Critical Attachments: Screen Shot 2013-09-18 at 08.44.31.png Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-951) Nightly builds produce faulty distributions
[ https://issues.apache.org/jira/browse/DIRSTUDIO-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-951: - Summary: Nightly builds produce faulty distributions (was: Nightly builds produce faulty Mac OS X distributions (32 and 64 bit)) Nightly builds produce faulty distributions --- Key: DIRSTUDIO-951 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-951 Project: Directory Studio Issue Type: Bug Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Priority: Critical Attachments: Screen Shot 2013-09-18 at 08.44.31.png Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-951) Nightly builds produce faulty Mac OS X distributions (32 and 64 bit)
[ https://issues.apache.org/jira/browse/DIRSTUDIO-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770728#comment-13770728 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-951: -- It appears there was a problem in the previous build since the size of the distribution is susceptibly lower than usual. I relaunched a new build and the size is back to correct standards. #92718 sept. 2013 11:37:52 935MB #92618 sept. 2013 05:00:44 570MB That said, the distributions still show an upacking problem (zip and tar.gz). Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) Key: DIRSTUDIO-951 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-951 Project: Directory Studio Issue Type: Bug Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Priority: Critical Attachments: Screen Shot 2013-09-18 at 08.44.31.png Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-951) Nightly builds produce faulty distributions
[ https://issues.apache.org/jira/browse/DIRSTUDIO-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771352#comment-13771352 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-951: -- It seems to be an issue with the assembly plugin. A workaround is indicated in this JIRA issue: http://jira.codehaus.org/browse/MASSEMBLY-557 Nightly builds produce faulty distributions --- Key: DIRSTUDIO-951 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-951 Project: Directory Studio Issue Type: Bug Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Priority: Critical Attachments: Screen Shot 2013-09-18 at 08.44.31.png Nightly builds produce faulty Mac OS X distributions (32 and 64 bit) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DIRSERVER-1899) Custom objectClass is not visible while creating an entry from Apache Directory Studio
[ https://issues.apache.org/jira/browse/DIRSERVER-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot closed DIRSERVER-1899. - Resolution: Not A Problem Fix Version/s: (was: 2.0.0-M15) Assignee: Pierre-Arnaud Marcelot Cool, let me close the issue then. Thanks for the feedback. Custom objectClass is not visible while creating an entry from Apache Directory Studio -- Key: DIRSERVER-1899 URL: https://issues.apache.org/jira/browse/DIRSERVER-1899 Project: Directory ApacheDS Issue Type: Bug Components: ldap Affects Versions: 2.0.0-M15 Environment: Windows 7 - 64 bit Reporter: prahlad Assignee: Pierre-Arnaud Marcelot Labels: security Attachments: Screen Shot 2013-09-16 at 16.34.19.png Original Estimate: 96h Remaining Estimate: 96h I have created a custom ldap schema from Apache Schema editor, exported the schema for ApacheDS. Started the ApacheDS server and launched Apache Directory Studio, created a connection then imported the schema which i exported in apacheDS. After importing I restarted the ldapserver. I am seeing the imported schema entry inside ou=schema. When I am trying to create an entry from Apache Directory Studio, objectClass which i imported is not showing at Object Classes page of New Entry. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Supporting PKCS5S2 Password Hashing
I'm also preparing its integration in the Password Editor of Apache Directory Studio as well. Regards, Pierre-Arnaud On 17 sept. 2013, at 11:29, Kiran Ayyagari kayyag...@apache.org wrote: support for PKCS5S2 is now included in the server, see https://issues.apache.org/jira/browse/DIRSERVER-1898 On Fri, Mar 22, 2013 at 8:37 PM, Kiran Ayyagari kayyag...@apache.org wrote: if you want to implement, then 1. create a subclass of PasswordHashingInterceptor [1] supporting the said hashing mechanism 2. package it as a jar and copy it to lib directory 3. go to the entry ads-interceptorId=passwordHashingInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config 4. change the value of ads-interceptorclassname to your new class's FQCN 5. restart the server If you want to see an example implementation take a look at [2] [1] http://svn.apache.org/repos/asf/directory/apacheds/trunk/interceptors/hash/src/main/java/org/apache/directory/server/core/hash/PasswordHashingInterceptor.java [2] http://svn.apache.org/repos/asf/directory/apacheds/trunk/interceptors/hash/src/main/java/org/apache/directory/server/core/hash/Sha256PasswordHashingInterceptor.java On Fri, Mar 22, 2013 at 8:19 PM, Ashma Shrestha ashres...@crl.edu wrote: Hi, Are there any plans on implementing PKCS5S2 Password Hashing? If not can anyone provide me some pointers on how this can be implemented. Thank you. Ashma Shrestha -- Kiran Ayyagari http://keydap.com -- Kiran Ayyagari http://keydap.com
[jira] [Created] (DIRSTUDIO-950) Add support for PKCS5S2 hashing mechanism in Password Dialog
Pierre-Arnaud Marcelot created DIRSTUDIO-950: Summary: Add support for PKCS5S2 hashing mechanism in Password Dialog Key: DIRSTUDIO-950 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-950 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M9, 2.0.0 Add support for PKCS5S2 hashing mechanism in Password Dialog -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSTUDIO-950) Add support for PKCS5S2 hashing mechanism in Password Dialog
[ https://issues.apache.org/jira/browse/DIRSTUDIO-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-950. -- Resolution: Fixed Fixed at revision 1524098. http://svn.apache.org/r1524098 Add support for PKCS5S2 hashing mechanism in Password Dialog Key: DIRSTUDIO-950 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-950 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M9, 2.0.0 Add support for PKCS5S2 hashing mechanism in Password Dialog -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Mavibot] Value storage
I would go with a simple Iterator. Regards, Pierre-Arnaud On 16 sept. 2013, at 11:51, Emmanuel Lécharny elecha...@gmail.com wrote: Le 9/16/13 11:41 AM, Kiran Ayyagari a écrit : On Mon, Sep 16, 2013 at 3:00 PM, Emmanuel Lécharny elecha...@gmail.comwrote: Le 9/14/13 9:45 AM, Kiran Ayyagari a écrit : On Sat, Sep 14, 2013 at 1:00 PM, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, /** * @return The array of stored values. */ V[] getValues(); shouldn't this be returning a BTreeV,V? cause we don't support an array as a holder of multiple values The fact that it's stored as a BTree is implementation dependent, I'm not sure the user of the API should know about it. What the user wants is to get back the stored values, and this is convenient to get back an array. IMO, it is not convenient, we cannot copy all the values into an array and return, and returning an iterator is not going to help either, both will severely affect the search performance If needed, we can wrap it an immutable structure and return the BTree to prevent direct updates, but I wish to differ this until we see the impact on partition implementation. Except that from the BTree interface, the one the users see, you have : public V get( K key ) throws IOException, KeyNotFoundException public DuplicateKeyValV getValues( K key ) throws IOException, KeyNotFoundException so the users has no clue about the underlying data structure. Now, I'm not sure if it makes any sense to expose a getValues() method returning an array. May be an iterator is enough.. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[jira] [Created] (DIRSTUDIO-949) Add the ability to configure a Mavibot partition
Pierre-Arnaud Marcelot created DIRSTUDIO-949: Summary: Add the ability to configure a Mavibot partition Key: DIRSTUDIO-949 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-949 Project: Directory Studio Issue Type: New Feature Components: studio-apacheds-configuration Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-M9 Add the ability to configure a Mavibot partition, alonside JDBM partition as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSERVER-1899) Custom objectClass is not visible while creating an entry from Apache Directory Studio
[ https://issues.apache.org/jira/browse/DIRSERVER-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSERVER-1899: -- Attachment: Screen Shot 2013-09-16 at 16.34.19.png Could you try reload the schema in the Object Class page using this icon? Thanks Custom objectClass is not visible while creating an entry from Apache Directory Studio -- Key: DIRSERVER-1899 URL: https://issues.apache.org/jira/browse/DIRSERVER-1899 Project: Directory ApacheDS Issue Type: Bug Components: ldap Affects Versions: 2.0.0-M15 Environment: Windows 7 - 64 bit Reporter: prahlad Labels: security Fix For: 2.0.0-M15 Attachments: Screen Shot 2013-09-16 at 16.34.19.png Original Estimate: 96h Remaining Estimate: 96h I have created a custom ldap schema from Apache Schema editor, exported the schema for ApacheDS. Started the ApacheDS server and launched Apache Directory Studio, created a connection then imported the schema which i exported in apacheDS. After importing I restarted the ldapserver. I am seeing the imported schema entry inside ou=schema. When I am trying to create an entry from Apache Directory Studio, objectClass which i imported is not showing at Object Classes page of New Entry. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSTUDIO-949) Add the ability to configure a Mavibot partition
[ https://issues.apache.org/jira/browse/DIRSTUDIO-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-949. -- Resolution: Fixed Fix Version/s: 2.0.0 Fixed at revision 1523681. http://svn.apache.org/r1523681 Add the ability to configure a Mavibot partition Key: DIRSTUDIO-949 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-949 Project: Directory Studio Issue Type: New Feature Components: studio-apacheds-configuration Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-M9, 2.0.0 Add the ability to configure a Mavibot partition, alonside JDBM partition as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSERVER-1897) Download apache issue link does not work
[
https://issues.apache.org/jira/browse/DIRSERVER-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot resolved DIRSERVER-1897.
---
Resolution: Fixed
Assignee: Pierre-Arnaud Marcelot
Fixed at revision 1523001.
http://svn.apache.org/r1523001
Download apache issue link does not work
Key: DIRSERVER-1897
URL: https://issues.apache.org/jira/browse/DIRSERVER-1897
Project: Directory ApacheDS
Issue Type: Bug
Environment: Safari and Chrome
Reporter: Nicolas Leroux
Assignee: Pierre-Arnaud Marcelot
Attachments: Screen Shot 2013-09-13 at 2.40.26 PM.png
The download link does not work.
Reproduction step:
* Go to http://directory.apache.org/apacheds/
* Click on {{Download}}
* Observe that nothing happens
Workaround:
Go to
https://dist.apache.org/repos/dist/release/directory/apacheds/dist/2.0.0-M15/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1897) Download apache issue link does not work
[
https://issues.apache.org/jira/browse/DIRSERVER-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766588#comment-13766588
]
Pierre-Arnaud Marcelot commented on DIRSERVER-1897:
---
Thanks s much Nicolas for letting us know.
I'm ashamed I didn't pay attention to it sooner!
It's one thing to display big download buttons but it's another thing to not
forget to link them to the correct page.
I must have had my head elsewhere the day I modified this.
Thanks again!
Download apache issue link does not work
Key: DIRSERVER-1897
URL: https://issues.apache.org/jira/browse/DIRSERVER-1897
Project: Directory ApacheDS
Issue Type: Bug
Environment: Safari and Chrome
Reporter: Nicolas Leroux
Attachments: Screen Shot 2013-09-13 at 2.40.26 PM.png
The download link does not work.
Reproduction step:
* Go to http://directory.apache.org/apacheds/
* Click on {{Download}}
* Observe that nothing happens
Workaround:
Go to
https://dist.apache.org/repos/dist/release/directory/apacheds/dist/2.0.0-M15/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-948) Sorting search results does not work with over 1000 results
[ https://issues.apache.org/jira/browse/DIRSTUDIO-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762888#comment-13762888 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-948: -- Hi Joakim, Are we talking about sorting in the LDAP Browser view (the tree-view on the left of the perspective)? If yes, did you have a look at the Sorting options (accessible from the little triangle menu)? See this page on the documentation for more details: http://directory.apache.org/studio/users-guide/ldap_browser/tools_browser_view_overview.html#tools_browser_view_sortdialog Hope this helps. Sorting search results does not work with over 1000 results --- Key: DIRSTUDIO-948 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-948 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Joakim Ganse Priority: Critical When Searching a large directory sorting is not possible if there are more than 1000 results. What I do is a standard search and then click on the attribute tab. If I have fewer that 1000 results they sort nicely but with more than 1000 no sorting occurs. I can understand this from an performance perspective but it would be nice to have the option to set the limit as we have in other areas. Maybe it is possible but I just have not found the right place to adjust it. Thanks Joakim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-948) Sorting search results does not work with over 1000 results
[ https://issues.apache.org/jira/browse/DIRSTUDIO-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762918#comment-13762918 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-948: -- Sorry, I did miss the Search Results keyword in the issue description. Thanks for the screenshot. :) Looking at the code, indeed we have a hard coded limitation set to 1000 search results. Maybe we should have a field for that in the preference page of Search Result Editor to allow our users to increase it (with a tooltip indicating that it's a very costly operation). Thanks for the report, that's a perfectly valid observation! Sorting search results does not work with over 1000 results --- Key: DIRSTUDIO-948 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-948 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Joakim Ganse Priority: Critical Attachments: ejfbhjae.png When Searching a large directory sorting is not possible if there are more than 1000 results. What I do is a standard search and then click on the attribute tab. If I have fewer that 1000 results they sort nicely but with more than 1000 no sorting occurs. I can understand this from an performance perspective but it would be nice to have the option to set the limit as we have in other areas. Maybe it is possible but I just have not found the right place to adjust it. Thanks Joakim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-948) Sorting search results does not work with over 1000 results
[ https://issues.apache.org/jira/browse/DIRSTUDIO-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-948: - Fix Version/s: 2.0.0-M10 Assignee: Pierre-Arnaud Marcelot Sorting search results does not work with over 1000 results --- Key: DIRSTUDIO-948 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-948 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Joakim Ganse Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-M10 Attachments: ejfbhjae.png When Searching a large directory sorting is not possible if there are more than 1000 results. What I do is a standard search and then click on the attribute tab. If I have fewer that 1000 results they sort nicely but with more than 1000 no sorting occurs. I can understand this from an performance perspective but it would be nice to have the option to set the limit as we have in other areas. Maybe it is possible but I just have not found the right place to adjust it. Thanks Joakim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-948) Sorting search results does not work with over 1000 results
[ https://issues.apache.org/jira/browse/DIRSTUDIO-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-948: - Fix Version/s: (was: 2.0.0-M10) 2.0.0-M9 Sorting search results does not work with over 1000 results --- Key: DIRSTUDIO-948 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-948 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Joakim Ganse Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-M9 Attachments: ejfbhjae.png When Searching a large directory sorting is not possible if there are more than 1000 results. What I do is a standard search and then click on the attribute tab. If I have fewer that 1000 results they sort nicely but with more than 1000 no sorting occurs. I can understand this from an performance perspective but it would be nice to have the option to set the limit as we have in other areas. Maybe it is possible but I just have not found the right place to adjust it. Thanks Joakim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSTUDIO-948) Sorting search results does not work with over 1000 results
[ https://issues.apache.org/jira/browse/DIRSTUDIO-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-948. -- Resolution: Fixed Fix Version/s: 2.0.0 Fixed at revision 1521528. http://svn.apache.org/r1521528 Sorting search results does not work with over 1000 results --- Key: DIRSTUDIO-948 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-948 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Joakim Ganse Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-M9, 2.0.0 Attachments: ejfbhjae.png When Searching a large directory sorting is not possible if there are more than 1000 results. What I do is a standard search and then click on the attribute tab. If I have fewer that 1000 results they sort nicely but with more than 1000 no sorting occurs. I can understand this from an performance perspective but it would be nice to have the option to set the limit as we have in other areas. Maybe it is possible but I just have not found the right place to adjust it. Thanks Joakim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-948) Sorting search results does not work with over 1000 results
[ https://issues.apache.org/jira/browse/DIRSTUDIO-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-948: - Attachment: Screen Shot 2013-09-10 at 17.47.36.png I added a new integer text field to specify the 'Sort/Filter Limit' in the 'Search Result Editor' preference page. The limit has been raised to 10.000 by default. Sorting search results does not work with over 1000 results --- Key: DIRSTUDIO-948 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-948 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Joakim Ganse Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-M9, 2.0.0 Attachments: ejfbhjae.png, Screen Shot 2013-09-10 at 17.47.36.png When Searching a large directory sorting is not possible if there are more than 1000 results. What I do is a standard search and then click on the attribute tab. If I have fewer that 1000 results they sort nicely but with more than 1000 no sorting occurs. I can understand this from an performance perspective but it would be nice to have the option to set the limit as we have in other areas. Maybe it is possible but I just have not found the right place to adjust it. Thanks Joakim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-946) Add the ability of saving common attributes list
[ https://issues.apache.org/jira/browse/DIRSTUDIO-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13758959#comment-13758959 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-946: -- Hi Jean-Marie, Could you explain why the existing drop-down list isn't easy to use? I don't see the point that adding Save/Load buttons would improve the usability of the list. Thanks, Pierre-Arnaud Add the ability of saving common attributes list Key: DIRSTUDIO-946 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-946 Project: Directory Studio Issue Type: Improvement Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Jean-Marie Damas Priority: Minor Labels: filter, load, save, search In search GUI (and certainly in others screens), it would be useful to be able to save (and so, further, reload) the commonly used attributes list. The actual drop-down list stores the precedent used lists but it isn't so easy to use. For example, by creating an Attribute List Editor with buttons Save and Load ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-946) Add the ability of saving common attributes list
[ https://issues.apache.org/jira/browse/DIRSTUDIO-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759092#comment-13759092 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-946: -- How about defining different searches since those are saved with the connection (and displayed at the end of the source tree)? It would allow you to switch rapidly between those you frequently run. That's exactly what they are here for. Along with DIRSTUDIO-786 (Add support for shared searches across all connections) [Yet to be implemented], it would allow you to have a set of favorite searches you run often on most of your connections. Add the ability of saving common attributes list Key: DIRSTUDIO-946 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-946 Project: Directory Studio Issue Type: Improvement Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Jean-Marie Damas Priority: Minor Labels: filter, load, save, search Attachments: ADS_SearchGUI.jpg, SOFTERRA_SearchGUI.jpg In search GUI (and certainly in others screens), it would be useful to be able to save (and so, further, reload) the commonly used attributes list. The actual drop-down list stores the precedent used lists but it isn't so easy to use. For example, by creating an Attribute List Editor with buttons Save and Load ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Website] New landing (index) pages for all 4 Apache Directory sub-projects
Thanks for the feedback guys. It's now live. Regards, Pierre-Arnaud On 22 août 2013, at 21:20, Stefan Seelmann m...@stefan-seelmann.de wrote: Very nice! you have my +1. On 08/21/2013 04:40 PM, Pierre-Arnaud Marcelot wrote: Hi, I have just pushed on staging new versions for the landing pages for all 4 Apache Directory sub-projects: - ApacheDS (http://directory.staging.apache.org/apacheds/) - Apache Directory Studio (http://directory.staging.apache.org/studio/) [Note: it mostly identical to the previous page] - Apache LDAP API (http://directory.staging.apache.org/api/) - Apache Mavibot (http://directory.staging.apache.org/mavibot/) I'd like to get your feedback on them. Should we push this design to the production site? If yes, I'd require some help with the text of the ApacheDS feature highlights which contains random Lorem Ipsum text at the moment. Regards, Pierre-Arnaud
Re: MIA for one week
Have a good one! I'll be following starting next tuesday (august 27th) up until next next wednesday (september 4th). Regards, Pierre-Arnaud On 23 août 2013, at 12:16, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, I'll be MIA for one week. Have fun in the mean time ! -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: Next steps...
On 21 août 2013, at 11:47, Kiran Ayyagari kayyag...@apache.org wrote: On Wed, Aug 21, 2013 at 1:38 PM, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, as I'm going to be off for one week, and as we just cuut a new reelase, I'd like to share some random thoughts about the server, the API, Mavibot and some other aspects of our project, where we are now, and what remains to be done in thenear future... First, I think we are slowly but consistently closing the gap to a 2.0-RC1. The last release was mainly about fixing some bugs, and the next one is probably the first RC. What remains to be done in order to cut this RC1 ? ApacheDS o Make Mavibot a first class partition (althouh still experimental). It should be possible for anyone to configure the server so that the partition uses either JDBM or Mavibot, without having to use any weird JVM options. This is a work in progress, Kiran already pushed some code that makes it possible to declare a Mavibot partition. o Avoid the cloning of entries we are returning o Check the bug list and fix the low hanging fruits Mavibot --- o make the handling of multiple values more performant. We shuld define a threshold after which we use a subBtree, instead of creating a subBtree everytime o improve the performance of writes : we are updating the BTree headers and teh RM headers after each phisical page update, whihc is adding ahuge penalty o complete the bulk load implementation API --- Not too much in this area. We are close to completion, at least for 1.0. The doco is still really poor... Studio -- o Add the support of ADS 2.0-RC1 o Add support of Mavibot partition That's all for the short term tasks, as I can see them. I may have missed some, so please complete this list. Otherwise, in a middle term vision, we have many areas where we can improve the server and the other projects : ApacheDS o switch to MINA 3 o review the way we handle writes : we should wait for the messageSent event before writing a new message, otherwise we cumulate them in memory o review the encoding part : using a pre-allocated buffer stored in a ThreadLocal storage would save us some CPU cycle, as we could get rid of the allocation of a buffer o review the ACI subsystem o fix the administrative model, which is not complete o add the delta-syncrepl protocol for the MMR subsystem o implement the missing LDAP entities (NameForm, DCR, DSR, MRU...) o make the server OSGi compliant o ditch JDBM as a backend o get rid of most of the locks used for JDBM API --- o implement the missing LDAP entities (NameForm, DCR, DSR, MRU...) o implement a better support for some other server schema (OpenLDAP, OpenDJ, AD, etc) Mavibot --- o implement the transaction support o manage MVCC free pages o add a checker and a fixer after a crash Studio -- o go for a full web based Studio o add configuration support for other servers This list is just limited, again, please add the items you think it's important to have. you have covered everything :) +1. Nothing much to add here. Very thorough analysis of what's left to do in short and longer terms. Regards, Pierre-Arnaud o I would like to get eSCIMo done before 2.0 gets released (though this is not included in ApacheDS distribution there will be support for easily including eSCIMo as a webapp) o there is some interest in having DHCP support in ApacheDS we might need to look into that post 2.0 Comments very welcome ! -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com -- Kiran Ayyagari http://keydap.com
[jira] [Commented] (DIRSTUDIO-943) GC overhead limit exceeded when running an LDIF export
[ https://issues.apache.org/jira/browse/DIRSTUDIO-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13746026#comment-13746026 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-943: -- Ouch! Looks like you've hit the amount of memory allocated for Studio. Could you try increasing heap memory? Here's how, from the FAQ: http://directory.apache.org/studio/faqs.html#how-to-increase-the-heap-memory Regards, Pierre-Arnaud GC overhead limit exceeded when running an LDIF export -- Key: DIRSTUDIO-943 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-943 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Mikael Grahn Priority: Minor Fix For: 2.0.0-M8 (2.0.0.v20130628) I try to make a full LDAP export and after some minutes hangs the application and an inormation window shows following message: An internal error occurred during: LDIF Export. GC overhead limit exceeded I found in a file following message: !ENTRY org.eclipse.core.jobs 4 2 2013-08-21 11:22:23.931 !MESSAGE An internal error occurred during: LDIF Export. !STACK 0 java.lang.OutOfMemoryError: GC overhead limit exceeded at java.util.regex.Pattern.newSlice(Unknown Source) at java.util.regex.Pattern.atom(Unknown Source) at java.util.regex.Pattern.sequence(Unknown Source) at java.util.regex.Pattern.expr(Unknown Source) at java.util.regex.Pattern.compile(Unknown Source) at java.util.regex.Pattern.init(Unknown Source) at java.util.regex.Pattern.compile(Unknown Source) at java.lang.String.replaceAll(Unknown Source) at org.apache.directory.studio.ldifparser.model.lines.LdifLineBase.unfold(LdifLineBase.java:145) at org.apache.directory.studio.ldifparser.model.lines.LdifValueLineBase.getUnfoldedValueType(LdifValueLineBase.java:64) at org.apache.directory.studio.ldifparser.model.lines.LdifValueLineBase.isValueTypeSafe(LdifValueLineBase.java:252) at org.apache.directory.studio.ldifparser.model.lines.LdifValueLineBase.getValueAsObject(LdifValueLineBase.java:208) at org.apache.directory.studio.ldapbrowser.core.utils.ModelConverter.ldifAttrValLineToValue(ModelConverter.java:271) at org.apache.directory.studio.ldapbrowser.core.utils.AttributeComparator.compare(AttributeComparator.java:80) at java.util.TimSort.binarySort(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at org.apache.directory.studio.ldapbrowser.core.jobs.ExportLdifRunnable.export(ExportLdifRunnable.java:205) at org.apache.directory.studio.ldapbrowser.core.jobs.ExportLdifRunnable.run(ExportLdifRunnable.java:156) at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:119) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-943) GC overhead limit exceeded when running an LDIF export
[ https://issues.apache.org/jira/browse/DIRSTUDIO-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13746065#comment-13746065 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-943: -- Thanks for the feedback. I don't think the .ApacheDirectoryStudio has much to do with it. It might have been an uninstall error as you suggest or a typo in the name of the .ini file maybe (our Eclipse base is really picky on naming). Anyways, I'm glad it finally worked in the end and solved the issue. Regards, Pierre-Arnaud GC overhead limit exceeded when running an LDIF export -- Key: DIRSTUDIO-943 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-943 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Environment: Windows 7 Reporter: Mikael Grahn Priority: Minor Fix For: 2.0.0-M8 (2.0.0.v20130628) I try to make a full LDAP export and after some minutes hangs the application and an inormation window shows following message: An internal error occurred during: LDIF Export. GC overhead limit exceeded I found in a file following message: !ENTRY org.eclipse.core.jobs 4 2 2013-08-21 11:22:23.931 !MESSAGE An internal error occurred during: LDIF Export. !STACK 0 java.lang.OutOfMemoryError: GC overhead limit exceeded at java.util.regex.Pattern.newSlice(Unknown Source) at java.util.regex.Pattern.atom(Unknown Source) at java.util.regex.Pattern.sequence(Unknown Source) at java.util.regex.Pattern.expr(Unknown Source) at java.util.regex.Pattern.compile(Unknown Source) at java.util.regex.Pattern.init(Unknown Source) at java.util.regex.Pattern.compile(Unknown Source) at java.lang.String.replaceAll(Unknown Source) at org.apache.directory.studio.ldifparser.model.lines.LdifLineBase.unfold(LdifLineBase.java:145) at org.apache.directory.studio.ldifparser.model.lines.LdifValueLineBase.getUnfoldedValueType(LdifValueLineBase.java:64) at org.apache.directory.studio.ldifparser.model.lines.LdifValueLineBase.isValueTypeSafe(LdifValueLineBase.java:252) at org.apache.directory.studio.ldifparser.model.lines.LdifValueLineBase.getValueAsObject(LdifValueLineBase.java:208) at org.apache.directory.studio.ldapbrowser.core.utils.ModelConverter.ldifAttrValLineToValue(ModelConverter.java:271) at org.apache.directory.studio.ldapbrowser.core.utils.AttributeComparator.compare(AttributeComparator.java:80) at java.util.TimSort.binarySort(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at org.apache.directory.studio.ldapbrowser.core.jobs.ExportLdifRunnable.export(ExportLdifRunnable.java:205) at org.apache.directory.studio.ldapbrowser.core.jobs.ExportLdifRunnable.run(ExportLdifRunnable.java:156) at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:119) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[Website] New landing (index) pages for all 4 Apache Directory sub-projects
Hi, I have just pushed on staging new versions for the landing pages for all 4 Apache Directory sub-projects: - ApacheDS (http://directory.staging.apache.org/apacheds/) - Apache Directory Studio (http://directory.staging.apache.org/studio/) [Note: it mostly identical to the previous page] - Apache LDAP API (http://directory.staging.apache.org/api/) - Apache Mavibot (http://directory.staging.apache.org/mavibot/) I'd like to get your feedback on them. Should we push this design to the production site? If yes, I'd require some help with the text of the ApacheDS feature highlights which contains random Lorem Ipsum text at the moment. Regards, Pierre-Arnaud
Re: Strange failure in LDAP API...
Hi Emmanuel, Same thing as Kiran, I couldn't reproduce it. However I do get random build failures on my machine when I build with the -Dapacheds.partition.factory=org.apache.directory.server.core.factory.MavibotPartitionFactory suffix. These failures are not always the same but they always appears when building ApacheDS Core Integration (apacheds-core-integ). Here are some I get: *Iteration 1* Failed tests: SearchAuthorizationIT.testPerscriptiveGrantWithEntryDenial:792 null SearchAuthorizationIT.testPerscriptiveGrantWithEntryDenialWithPrecidence:863 null Tests run: 693, Failures: 2, Errors: 0, Skipped: 132 *Iteration 2* Failed tests: AliasSearchIT.testOuUsers:171-verifyCounts:557 expected:2 but was:1 AliasSearchIT.testOuPeople:194-verifyCounts:560 expected:2 but was:1 AliasSearchIT.testOuEngineering:274-verifyCounts:557 expected:1 but was:0 Tests run: 693, Failures: 3, Errors: 0, Skipped: 132 It finally passed on iteration #3. It's seem to be must likely related to a concurrency problem at some point in the build. Regards, Pierre-Arnaud On 19 août 2013, at 08:19, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, this morning, while running a mvn clean install, I've got this error : --- Test set: org.apache.directory.api.dsmlv2.abandonRequest.AbandonRequestTest --- Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.558 sec FAILURE! - in org.apache.directory.api.dsmlv2.abandonRequest.AbandonRequestTest testRequestWith1Control(org.apache.directory.api.dsmlv2.abandonRequest.AbandonRequestTest) Time elapsed: 0.049 sec ERROR! java.lang.IllegalStateException: The LdapCodecService is already set to an instance of org.apache.directory.api.ldap.codec.api.LdapApiServiceFactory at org.apache.directory.api.ldap.codec.api.LdapApiServiceFactory.initialize(LdapApiServiceFactory.java:113) at org.apache.directory.api.ldap.codec.api.LdapApiServiceFactory.getSingleton(LdapApiServiceFactory.java:89) at org.apache.directory.api.dsmlv2.AbstractTest.init(AbstractTest.java:42) at org.apache.directory.api.dsmlv2.abandonRequest.AbandonRequestTest.init(AbandonRequestTest.java:53) This is quite weaird, as this tes never failed. Is it something due to the OSGi framework, or some concurrent issue with the tests ? -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re:
[X] +1 : release ApacheDS 2.0.0-M15 Regards, Pierre-Arnaud On 15 août 2013, at 03:29, Emmanuel Lécharny elecha...@gmail.com wrote: Hi, I'd like to release ApacheDS 2.0.0-M15, which is a bug fix release. There are some huge performance improvements in this relzase, plus a few bugs have been fixed. The list of fixed bugs and improvments is the following : Bug * [DIRSERVER-1871 https://issues.apache.org/jira/browse/DIRSERVER-1871] - Logging Not Working in M14 * [DIRSERVER-1872 https://issues.apache.org/jira/browse/DIRSERVER-1872] - The JournalInterceptor is not present in the configuration * [DIRSERVER-1874 https://issues.apache.org/jira/browse/DIRSERVER-1874] - Persistent search is not considering the scope of the search * [DIRSERVER-1875 https://issues.apache.org/jira/browse/DIRSERVER-1875] - Persistent search is not filtering the attributes before returning entries * [DIRSERVER-1879 https://issues.apache.org/jira/browse/DIRSERVER-1879] - Incorrect check on result code done in the PwdModifyResponseImpl constructor * [DIRSERVER-1880 https://issues.apache.org/jira/browse/DIRSERVER-1880] - ApacheDS failed to start on boot * [DIRSERVER-1882 https://issues.apache.org/jira/browse/DIRSERVER-1882] - KertabEncoder.write() method should take into account the size of the entries list to determine the buffer size * [DIRSERVER-1883 https://issues.apache.org/jira/browse/DIRSERVER-1883] - Searching for entries starting at the rootDSE does not work Improvement * [DIRSERVER-1049 https://issues.apache.org/jira/browse/DIRSERVER-1049] - [PERF] Speed improvement in Search operation * [DIRSERVER-1519 https://issues.apache.org/jira/browse/DIRSERVER-1519] - [perf] The MoveAndRename operation is not optimal Here are the associated links : ApacheDS 2.0.0-M15 -- - SVN tag : http://svn.apache.org/r1513909 https://svn.apache.org/repos/asf/directory/apacheds/tags/2.0.0-M15/ - Nexus repository: https://repository.apache.org/content/repositories/orgapachedirectory-094/ - Distribution packages: http://people.apache.org/~elecharny http://people.apache.org/%7Eelecharny [ ] +1 : release ApacheDS 2.0.0-M15 [ ] ± 0 : I don't care [ ] -1 : No, don't release ApacheDS 2.0.0-M15 -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: [VOTE] Release of LDAP API 1.0.0-M20
[X] +1 Release Shared/LDAP API 1.0.0-M20 Regards, Pierre-Arnaud On 14 août 2013, at 12:03, Emmanuel Lécharny elecha...@gmail.com wrote: Hi, This is a vote for the 18th milestone of the 1.0.0 LDAP API/Shared, 1.0.0-M20. It's a bug fix release, and it will be followed by a release of ApachedDS 2.0.0-M15 this afternoon. It contains a few bug fixes and improvements : Bug * [DIRAPI-98 https://issues.apache.org/jira/browse/DIRAPI-98] - Add generic support for Extended operations * [DIRAPI-120 https://issues.apache.org/jira/browse/DIRAPI-120] - Deleted an attribute leads to an error * [DIRAPI-148 https://issues.apache.org/jira/browse/DIRAPI-148] - We can't inject entries with attributes containing a null value * [DIRAPI-151 https://issues.apache.org/jira/browse/DIRAPI-151] - Result codes from extended operations are lost New Feature * [DIRAPI-129 https://issues.apache.org/jira/browse/DIRAPI-129] - Add support for PwdModify extended operation The revision : http://svn.apache.org/r1513760 The SVN tag: http://svn.apache.org/repos/asf/directory/shared/tags/1.0.0-M20 The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-091/ Please cast your votes: [ ] +1 Release Shared/LDAP API 1.0.0-M20 [ ] 0 abstain [ ] -1 Do not release Shared/LDAP API 1.0.0-M20 Emmanuel -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[jira] [Resolved] (DIRSERVER-1880) ApacheDS failed to start on boot
[ https://issues.apache.org/jira/browse/DIRSERVER-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSERVER-1880. --- Resolution: Fixed Fix Version/s: 2.0.0-RC1 Assignee: Pierre-Arnaud Marcelot Fixed at revision 1512266. http://svn.apache.org/r1512266 ApacheDS failed to start on boot Key: DIRSERVER-1880 URL: https://issues.apache.org/jira/browse/DIRSERVER-1880 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Environment: uname -a Linux central-server 3.2.0-49-virtual #75-Ubuntu SMP Tue Jun 18 17:59:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux cat /etc/issue.net Ubuntu 12.04.2 LTS java -version java version 1.6.0_27 OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.2) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Reporter: Frank Ren Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-RC1 cat /var/lib/apacheds-2.0.0-M14/default/log/wrapper.log STATUS | wrapper | 2013/08/01 19:55:48 | -- Wrapper Started as Daemon STATUS | wrapper | 2013/08/01 19:55:48 | Launching a JVM... INFO | jvm 1| 2013/08/01 19:55:52 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1| 2013/08/01 19:55:52 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1| 2013/08/01 19:55:52 | ERROR | wrapper | 2013/08/01 19:56:26 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2013/08/01 19:56:26 | JVM did not exit on request, terminated INFO | wrapper | 2013/08/01 19:56:26 | JVM exited on its own while waiting to kill the application. STATUS | wrapper | 2013/08/01 19:56:26 | JVM exited in response to signal SIGKILL (9). FATAL | wrapper | 2013/08/01 19:56:26 | There were 1 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2013/08/01 19:56:26 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2013/08/01 19:56:26 | -- Wrapper Stopped It's an empty file, /var/lib/apacheds-2.0.0-M14/default/log/apacheds.log -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1880) ApacheDS failed to start on boot
[ https://issues.apache.org/jira/browse/DIRSERVER-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13734689#comment-13734689 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1880: --- Agreed and just committed. ;) ApacheDS failed to start on boot Key: DIRSERVER-1880 URL: https://issues.apache.org/jira/browse/DIRSERVER-1880 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Environment: uname -a Linux central-server 3.2.0-49-virtual #75-Ubuntu SMP Tue Jun 18 17:59:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux cat /etc/issue.net Ubuntu 12.04.2 LTS java -version java version 1.6.0_27 OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.2) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Reporter: Frank Ren cat /var/lib/apacheds-2.0.0-M14/default/log/wrapper.log STATUS | wrapper | 2013/08/01 19:55:48 | -- Wrapper Started as Daemon STATUS | wrapper | 2013/08/01 19:55:48 | Launching a JVM... INFO | jvm 1| 2013/08/01 19:55:52 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1| 2013/08/01 19:55:52 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1| 2013/08/01 19:55:52 | ERROR | wrapper | 2013/08/01 19:56:26 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2013/08/01 19:56:26 | JVM did not exit on request, terminated INFO | wrapper | 2013/08/01 19:56:26 | JVM exited on its own while waiting to kill the application. STATUS | wrapper | 2013/08/01 19:56:26 | JVM exited in response to signal SIGKILL (9). FATAL | wrapper | 2013/08/01 19:56:26 | There were 1 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2013/08/01 19:56:26 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2013/08/01 19:56:26 | -- Wrapper Stopped It's an empty file, /var/lib/apacheds-2.0.0-M14/default/log/apacheds.log -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Upgrade Jenkins Jobs to Java 6/7
All good to me. Thanks Stefan! Regards, Pierre-Arnaud On 7 août 2013, at 23:49, Stefan Seelmann m...@stefan-seelmann.de wrote: On 08/05/2013 09:34 AM, Pierre-Arnaud Marcelot wrote: On 4 août 2013, at 06:52, Emmanuel Lécharny elecha...@gmail.com wrote: Le 8/3/13 9:19 PM, Stefan Seelmann a écrit : Hi, we still have some Jenkins job that use Java 5. With the latest Jenkins upgrade Java 5 is no more supported (at least not for Maven style jobs, but for freestyle jobs) I'll upgrade all to use Java 6. Java 5 has reachead EOL long time ago. I'll also try to setup some Java 7 builds. Go for Java 7 only. Java 6 has EOLed at the end of last year too, and Java 7 is 20% faster than Java 6. +1. Just a quick status update: * shared, server, jdbm, mavibot builds use Java7 now, I also removed the -jdk16- infix from the job names. * studio and other side projects will follow within the next days * I'd like to delete the api-manual and apacheds-manual jobs as the manuals are now managed in the CMS. * I also created a mavibot build on Windows, but BTreeFlushTest fails with OOME (Java Heap Space), Anyone has an idea why? Otherwise I'll investigate. Kind Regards, Stefan
Re: [API] [ApacheDS] Problems with extended operations
On 2 août 2013, at 20:50, Kiran Ayyagari kayyag...@apache.org wrote: On Fri, Aug 2, 2013 at 10:43 PM, Pierre-Arnaud Marcelot p...@marcelot.net wrote: Hi, Recently, a user raised an issue on the LDAP API indicating that result codes from extended operations were lost. See https://issues.apache.org/jira/browse/DIRAPI-151. I took some time to debug the issue and it turns out it's true and it's even bigger than that, the response is simply not parsed correctly and internally in the API the object we return is just a newly created response for the given extended operation. The result code returned from the server is completely forgotten, same thing for the specific values included in the extended operation response. On the server, Emmanuel also found that responses were not correctly encoded. We're currently fixing that. This issue lead us to have a look at how the extended operations are loaded and I took a chance at simplifying a bit (which will help resolving the issue) the list of factories we need to append in the command line. We had properties like: - default.controls - extra.controls - default.extendedOperation.requests - default.extendedOperation.responses - extra.extendedOperations In the end, those default/extra distinctions didn't mean much and we needed to have them all the time. Also, the titles of the properties like 'default.extendedOperation.responses' were misleading as it was only intended for some specific kind of unsolicited response (having no request). I simplified it to two simple properties: - apacheds.controls - apacheds.extendedOperations +1 for the move, but please support the old properties as well to keep this change backward compatible cause these properties(old and new as well) are not so explicit and many users may not think of these while debugging an issue, so backward compatibility saves them a lot of time when they update their server libraries (but using the old scripts/classes in their applications to start the server) Sure, good idea. Regards, Pierre-Arnaud All tests, scripts and installers have been updated to reflect this change, so everything should be covered. Thoughts? Regards, Pierre-Arnaud -- Kiran Ayyagari http://keydap.com
Re: Upgrade Jenkins Jobs to Java 6/7
On 4 août 2013, at 06:52, Emmanuel Lécharny elecha...@gmail.com wrote: Le 8/3/13 9:19 PM, Stefan Seelmann a écrit : Hi, we still have some Jenkins job that use Java 5. With the latest Jenkins upgrade Java 5 is no more supported (at least not for Maven style jobs, but for freestyle jobs) I'll upgrade all to use Java 6. Java 5 has reachead EOL long time ago. I'll also try to setup some Java 7 builds. Go for Java 7 only. Java 6 has EOLed at the end of last year too, and Java 7 is 20% faster than Java 6. +1. Regards, Pierre-Arnaud -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: [Result] [VOTE] Make Mavibot a Directory subproject
Awesome! Congrats guys! Regards, Pierre-Arnaud On 4 août 2013, at 11:44, Kiran Ayyagari kayyag...@apache.org wrote: moved mavibot to directory SVN [1] set up a jenkins job to build and deploy to snapshot repo [2] committed the mavibot based partition factory and added mavibot-partition module in the apacheds/pom.xml now anyone who want to run tests with mavibot should pass the below argument to the JVM -Dapacheds.partition.factory=org.apache.directory.server.core.factory.MavibotPartitionFactory [1] https://svn.apache.org/repos/asf/directory/mavibot [2] https://builds.apache.org/job/dir-mavibot On Sat, Aug 3, 2013 at 2:38 PM, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, I close this vote. We have had 6 +1 binding votes : Alex Emmanuel Felix Kiran Pierre-Arnaud Stefan I will move the code base in Directory, and update the site to expose the project. Thanks ! -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com -- Kiran Ayyagari http://keydap.com
Re: Server performance improvements
Awesome! Regards, Pierre-Arnaud On 3 août 2013, at 02:35, Emmanuel Lécharny elecha...@gmail.com wrote: Hi, I applied one of the modifications I suggested in one of my previous mail : we pre-compte the set of candidates in the count() method, attach the set to the filter node (thanks god, we have a way to attach anything to the Node structure !) and use this set instead of constructing it again in the computeEquality() method. The gain is clear : CoreSession === Mavibot 10K entries --- Add : 80s, 125/s Search : 5091/s --- 15000/s Jdbm 10k entries Add : 167s, 59/s Search : 654/s --- 10009/s NetworkeSession === Mavibot 10K entries --- Add : 85s, 117/s Search : 1802/s --- 3467/s Jdbm 10k entries Add : 176s, 56/s Search : 506/s --- 3009/s That more than doubled the server's performance... We have many more ways to improve the server... But still, this was a second easy improvement after the previous 45% gain ! Side note 1 : the old JDBM performances were horribly low. It seems really strange that we are now able to get 6 times better result. I will re-run the tests without my last change to see what I get. Side note 2 : for the network tests, the cost of the encoding/decoding is high, and is paid twice (on the server and on the client). This is why we have much lower performances compared to the CoreSession tests. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: Weird behavior in Server-integ tests
Yay ! Regards, Pierre-Arnaud On 2 août 2013, at 10:54, Emmanuel Lécharny elecha...@gmail.com wrote: I have removed the MiltiThreadMultiInvoker from the server-integ tests, and I'm able to run server-integ in 4 mins instead of 15 ! -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[API] [ApacheDS] Problems with extended operations
Hi, Recently, a user raised an issue on the LDAP API indicating that result codes from extended operations were lost. See https://issues.apache.org/jira/browse/DIRAPI-151. I took some time to debug the issue and it turns out it's true and it's even bigger than that, the response is simply not parsed correctly and internally in the API the object we return is just a newly created response for the given extended operation. The result code returned from the server is completely forgotten, same thing for the specific values included in the extended operation response. On the server, Emmanuel also found that responses were not correctly encoded. We're currently fixing that. This issue lead us to have a look at how the extended operations are loaded and I took a chance at simplifying a bit (which will help resolving the issue) the list of factories we need to append in the command line. We had properties like: - default.controls - extra.controls - default.extendedOperation.requests - default.extendedOperation.responses - extra.extendedOperations In the end, those default/extra distinctions didn't mean much and we needed to have them all the time. Also, the titles of the properties like 'default.extendedOperation.responses' were misleading as it was only intended for some specific kind of unsolicited response (having no request). I simplified it to two simple properties: - apacheds.controls - apacheds.extendedOperations All tests, scripts and installers have been updated to reflect this change, so everything should be covered. Thoughts? Regards, Pierre-Arnaud
Re: Slight possible improvement in the search operation
+1 as well.
Regards,
Pierre-Arnaud
On 31 juil. 2013, at 22:29, Kiran Ayyagari kayyag...@apache.org wrote:
without further ado, my +1
On Thu, Aug 1, 2013 at 1:47 AM, Emmanuel Lécharny elecha...@gmail.com wrote:
Hi guys,
I have done some profiling on the search operation, and I have found
that for each processed search, we call the modifyFilter() operation,
which tries to optimize the filter. In this method, we check if the
search is done on the SubSchema Subentry. To do that, we get the rootDSE
from the Nexus, and get the SubschemaSubentry Dn :
private boolean isSubSchemaSubEntrySearch( LdapSession session,
SearchRequest req ) throws Exception
{
Dn base = req.getBase();
String baseNormForm = ( base.isSchemaAware() ?
base.getNormName() : base.getNormName() );
// get the rootDSE from the nexus
DirectoryService ds =
session.getCoreSession().getDirectoryService();
PartitionNexus nexus = ds.getPartitionNexus();
Value? subschemaSubentry = nexus.getRootDse( null ).get(
SchemaConstants.SUBSCHEMA_SUBENTRY_AT ).get();
// Grab the SubschemaSubentry from the rootDSE, and transform it
to a Dn
Dn subschemaSubentryDn = new Dn( ds.getSchemaManager(),
subschemaSubentry.getString() );
String subschemaSubentryDnNorm = subschemaSubentryDn.getNormName();
return subschemaSubentryDnNorm.equals( baseNormForm );
}
The two commented operations are extremely costly :
- we clone the root DSE just to get one single attrinbute from it
- and we parse a DN which is not lakely to change, ever.
We could most certainly spare us the CPU to do those two operations. The
RootDSE is initialized once when we start the server, and never updated
later, so the getRootDSE() method could perfectly be returned as is (and
duringthe initialization, we can encapsulate the rootDse in a
ImmutableEntry to protect it against any modification.
The very same for the subschemaSubentry DN : we could store a pre-parsed
version of it in the rootDSE, to avoid a parsing every time we do a search.
The gain would be around 8%, per the proviling session I have conducted.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
--
Kiran Ayyagari
http://keydap.com
Re: [VOTE] Make Mavibot a Directory subproject
[X] +1 : make Mavibot a Directory Subproject This is going to make a huge different for ApacheDS. Regards, Pierre-Arnaud PS: Should the Labs ML be in copy of the vote? On 1 août 2013, at 13:29, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, last year, I started an experiment in l...@apache.org, the Mavibot MVCC Btree. It has reached a first step, we can now use it as a backend for ApacheDS, thanks to Kiran - who joined me on the Mavibot effort, making it stable enough to be used in ApacheDS). This morning, I conducted some performance tests, comparing JDBM and Mavibot on a 10K entries base : CoreSession === Mavibot 10K entries --- Add : 80s, 125/s Search : 7392/s Jdbm 10k entries Add : 167s, 59/s Search : 654/s NetworkeSession === Mavibot 10K entries --- Add : 85s, 117/s Search : 1802/s Jdbm 10k entries Add : 176s, 56/s Search : 506/s As we can see, either on CoreSession, or through the network, the gain over JDBM is really clear. It's ten time faster. So this vote to integrate Mavibot as a Directory Subproject, in order to be able to release it and use it as our base backend in a near future. It's not feature complete yet, but the core BTree already works. So let's vote : [ ] +1 : make Mavibot a Directory Subproject [ ] +/-0 : I don't mind [ ] -1 : No, Mavibot should not become a Directory subproject Thanks ! and of course, my +1 -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[jira] [Updated] (DIRSTUDIO-903) Clicking Accept when no changes have been made on the password edit dialog changes the password
[ https://issues.apache.org/jira/browse/DIRSTUDIO-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-903: - Component/s: (was: studio-connection) studio-ldapbrowser Clicking Accept when no changes have been made on the password edit dialog changes the password - Key: DIRSTUDIO-903 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-903 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M6 (2.0.0.v20130308) Environment: Windows 7 x64 Reporter: Guillermo López Alejos Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M9, 2.0.0 Original Estimate: 4h Remaining Estimate: 4h Double clicking a password entry opens the password edit dialog. If I press Accept without making any change, then the password is changed (presumably to an empty string). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-903) Clicking Accept when no changes have been made on the password edit dialog changes the password
[ https://issues.apache.org/jira/browse/DIRSTUDIO-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-903: - Component/s: studio-connection Clicking Accept when no changes have been made on the password edit dialog changes the password - Key: DIRSTUDIO-903 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-903 Project: Directory Studio Issue Type: Bug Components: studio-connection Affects Versions: 2.0.0-M6 (2.0.0.v20130308) Environment: Windows 7 x64 Reporter: Guillermo López Alejos Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M9, 2.0.0 Original Estimate: 4h Remaining Estimate: 4h Double clicking a password entry opens the password edit dialog. If I press Accept without making any change, then the password is changed (presumably to an empty string). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-942) Description for OID 1.3.18.0.2.32.99 missing
[ https://issues.apache.org/jira/browse/DIRSTUDIO-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-942: - Component/s: studio-connection Description for OID 1.3.18.0.2.32.99 missing Key: DIRSTUDIO-942 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-942 Project: Directory Studio Issue Type: Improvement Components: studio-connection Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Frank Brandt Assignee: Pierre-Arnaud Marcelot Priority: Minor Fix For: 2.0.0-M9 In Root DSE Features, for Tivoli Directory Server 6.3 the description is missing for OID 1.3.18.0.2.32.99. According to this IBM site http://pic.dhe.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=%2Fcom.ibm.IBMDS.doc%2Fadmin_gd510.htm the OID indicates Support for SHA-2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1880) ApacheDS failed to start on boot
[ https://issues.apache.org/jira/browse/DIRSERVER-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726850#comment-13726850 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1880: --- It's most likely the server took too much time to start (slow machine/VM?) and the wrapper killed it. You can try to increase the wrapper.ping.timeout parameter of the wrapper in the wrapper.conf file from the conf directory of the ApacheDS installation. (See http://directory.apache.org/apacheds/advanced-ug/5.1-layout.html) You may also switch to Oracle's JVM. Hope this helps. ApacheDS failed to start on boot Key: DIRSERVER-1880 URL: https://issues.apache.org/jira/browse/DIRSERVER-1880 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Environment: uname -a Linux central-server 3.2.0-49-virtual #75-Ubuntu SMP Tue Jun 18 17:59:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux cat /etc/issue.net Ubuntu 12.04.2 LTS java -version java version 1.6.0_27 OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.2) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Reporter: Frank Ren cat /var/lib/apacheds-2.0.0-M14/default/log/wrapper.log STATUS | wrapper | 2013/08/01 19:55:48 | -- Wrapper Started as Daemon STATUS | wrapper | 2013/08/01 19:55:48 | Launching a JVM... INFO | jvm 1| 2013/08/01 19:55:52 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1| 2013/08/01 19:55:52 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1| 2013/08/01 19:55:52 | ERROR | wrapper | 2013/08/01 19:56:26 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2013/08/01 19:56:26 | JVM did not exit on request, terminated INFO | wrapper | 2013/08/01 19:56:26 | JVM exited on its own while waiting to kill the application. STATUS | wrapper | 2013/08/01 19:56:26 | JVM exited in response to signal SIGKILL (9). FATAL | wrapper | 2013/08/01 19:56:26 | There were 1 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2013/08/01 19:56:26 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2013/08/01 19:56:26 | -- Wrapper Stopped It's an empty file, /var/lib/apacheds-2.0.0-M14/default/log/apacheds.log -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1877) No-dependency ditribution for apache ds should be made available
[ https://issues.apache.org/jira/browse/DIRSERVER-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725062#comment-13725062 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1877: --- Of course, I understand and agree too. But in the real world, the situation is a bit more complicated than that. Most of our users are using Maven or Ant (+ Ivy) and we already build and deliver 14 different packages for each release, which need to be maintained and tested. I'm absolutely not against a no-dependency distribution, It would be a great thing to have. But it's always a (difficult) matter of finding the good balance between the time spent building and maintaining it and how much benefit it brings to the community. The Apache Directory Team is small and does not have infinite amount of time to work on the project, which forces us to makes choices. We're sorry about the inconvenience and I hope that, at least, you managed to find what you wanted with our indications. That's how Open Source works. Contributions are greatly welcomed. ;) No-dependency ditribution for apache ds should be made available Key: DIRSERVER-1877 URL: https://issues.apache.org/jira/browse/DIRSERVER-1877 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M13 Reporter: Anshuman Labels: apacheds, distribution, nodep The ApacheDS currently ships as a single service jar. This however includes all the dependencies bundled within it (ex: javax.servlet.*, mina, slf4j, etc). There should be option to download just the ApacheDS code so that when working in an embedded environment, unwanted dependencies can be avoided and for mandatory dependencies like mina, the application may chose a different version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRAPI-151) Result codes from extended operations are lost
[
https://issues.apache.org/jira/browse/DIRAPI-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723675#comment-13723675
]
Pierre-Arnaud Marcelot commented on DIRAPI-151:
---
I was able to reproduce the issue.
Working on it...
Result codes from extended operations are lost
--
Key: DIRAPI-151
URL: https://issues.apache.org/jira/browse/DIRAPI-151
Project: Directory Client API
Issue Type: Bug
Reporter: Daniel Fisher
Invoking LdapConnection#extended(String, byte[]) always returns success.
Performing a PasswordModifyOperation with an incorrect old password should
result in an error code 53, unwilling to perform.
However, the API returns error code 0, success, for the following code:
{code}
ExtendedResponse response = conn.extended(
1.3.6.1.4.1.4203.1.11.1,
new byte[] {...});
response.getLdapResult(); // always returns success
{code}
The bug may be around line 3106 of LdapNetworkConnection, where the actual
response is discarded in favor of a response built from the request object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRAPI-151) Result codes from extended operations are lost
[
https://issues.apache.org/jira/browse/DIRAPI-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot updated DIRAPI-151:
--
Affects Version/s: 1.0.0-M19
Fix Version/s: 1.0.0-RC1
Assignee: Pierre-Arnaud Marcelot
Result codes from extended operations are lost
--
Key: DIRAPI-151
URL: https://issues.apache.org/jira/browse/DIRAPI-151
Project: Directory Client API
Issue Type: Bug
Affects Versions: 1.0.0-M19
Reporter: Daniel Fisher
Assignee: Pierre-Arnaud Marcelot
Fix For: 1.0.0-RC1
Invoking LdapConnection#extended(String, byte[]) always returns success.
Performing a PasswordModifyOperation with an incorrect old password should
result in an error code 53, unwilling to perform.
However, the API returns error code 0, success, for the following code:
{code}
ExtendedResponse response = conn.extended(
1.3.6.1.4.1.4203.1.11.1,
new byte[] {...});
response.getLdapResult(); // always returns success
{code}
The bug may be around line 3106 of LdapNetworkConnection, where the actual
response is discarded in favor of a response built from the request object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRSERVER-1879) Incorrect check on result code done in the PwdModifyResponseImpl constructor
Pierre-Arnaud Marcelot created DIRSERVER-1879: - Summary: Incorrect check on result code done in the PwdModifyResponseImpl constructor Key: DIRSERVER-1879 URL: https://issues.apache.org/jira/browse/DIRSERVER-1879 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-RC1 Incorrect check on result code done in the PwdModifyResponseImpl constructor. RFC states that: The server MAY return adminLimitExceeded, busy, confidentialityRequired, operationsError, unavailable, unwillingToPerform, or other non-success resultCode as appropriate to indicate that it was unable to successfully complete the operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSERVER-1879) Incorrect check on result code done in the PwdModifyResponseImpl constructor
[ https://issues.apache.org/jira/browse/DIRSERVER-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSERVER-1879. --- Resolution: Fixed Fixed at revision 1508543. http://svn.apache.org/r1508543 Incorrect check on result code done in the PwdModifyResponseImpl constructor Key: DIRSERVER-1879 URL: https://issues.apache.org/jira/browse/DIRSERVER-1879 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-RC1 Incorrect check on result code done in the PwdModifyResponseImpl constructor. RFC states that: The server MAY return adminLimitExceeded, busy, confidentialityRequired, operationsError, unavailable, unwillingToPerform, or other non-success resultCode as appropriate to indicate that it was unable to successfully complete the operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Mavibot backend is now working ! Time to move it as a subproject of Directory ?
That's an awesome news and very great results and improvements. My +1 to make Mavibot an Apache Directory sub-project. Regards, Pierre-Arnaud On 28 juil. 2013, at 09:47, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys ! a good news : I was able to successfully to run all the tests with the Mavibot backend (althouh I had some random errors in some tests, which has to be understood : not sure that the backend itself is responsible for that, instead of one of the various caches we are using). Now, as Mavibot is in labs, I think we have to move it to Directory, to make it a subproject. This is just a decision we have to make at this point. I'll start a vote on mondyay on this matter. ATM, Mavibot is used pretty much the same way we use JDBM, with many locks, as we aren't yet leveraging the MVCC layer. However, even without using this feature, we have a clear gain in performance : JDBM search : - Object : 47 370/s One: 67 590/s sub: 75 990/s Mavibot search : Object : 70 681/s +49% One: 93 195/s +38% sub: 114 670/s +51% (those tests are for CoreSession, the network layer being too intrusive to show the ral increase of performance.) For an Add operation, the gain is even greater : JDBM add : 85/s Mavibot add : 187/s +120% More to come later. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[jira] [Commented] (DIRSERVER-1877) No-dependency ditribution for apache ds should be made available
[ https://issues.apache.org/jira/browse/DIRSERVER-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722293#comment-13722293 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1877: --- Here's the dependencies graph run on the apacheds-service project: [INFO] [INFO] Building ApacheDS Service 2.0.0-M15-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ apacheds-service --- [INFO] org.apache.directory.server:apacheds-service:jar:2.0.0-M15-SNAPSHOT [INFO] +- org.apache.directory.server:apacheds-core-annotations:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-core:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-core-shared:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-admin:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-authn:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-authz:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-changelog:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-collective:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-event:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-exception:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-journal:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-normalization:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-operational:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-referral:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-schema:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-subtree:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-interceptors-trigger:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | \- bouncycastle:bcprov-jdk15:jar:140:compile [INFO] | +- org.apache.directory.server:apacheds-ldif-partition:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-i18n:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-jdbm-partition:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | +- org.apache.directory.server:apacheds-core-avl:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | \- org.apache.directory.jdbm:apacheds-jdbm1:bundle:2.0.0-M2:compile [INFO] | +- org.apache.directory.server:apacheds-xdbm-partition:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | \- commons-io:commons-io:jar:2.4:compile [INFO] +- org.apache.directory.server:apacheds-core-api:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- commons-lang:commons-lang:jar:2.6:compile [INFO] | +- org.apache.directory.server:apacheds-core-constants:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.api:api-i18n:jar:1.0.0-M20-SNAPSHOT:compile [INFO] | +- org.apache.directory.api:api-asn1-api:jar:1.0.0-M20-SNAPSHOT:compile [INFO] | +- org.apache.directory.api:api-ldap-client-api:jar:1.0.0-M20-SNAPSHOT:compile [INFO] | | \- commons-pool:commons-pool:jar:1.6:compile [INFO] | +- org.apache.directory.api:api-ldap-codec-core:jar:1.0.0-M20-SNAPSHOT:compile [INFO] | +- org.apache.directory.api:api-ldap-extras-aci:jar:1.0.0-M20-SNAPSHOT:compile [INFO] | +- org.apache.directory.api:api-ldap-extras-util:jar:1.0.0-M20-SNAPSHOT:compile [INFO] | +- org.apache.mina:mina-core:jar:2.0.7:compile [INFO] | \- net.sf.ehcache:ehcache-core:jar:2.4.4:compile [INFO] +- org.apache.directory.server:apacheds-service-builder:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-interceptors-hash:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | \- org.apache.directory.api:api-ldap-extras-trigger:jar:1.0.0-M20-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-kerberos-codec:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-protocol-dhcp:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-protocol-dns:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | | \- org.apache.directory.server:apacheds-core-jndi:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-protocol-kerberos:jar:2.0.0-M15-SNAPSHOT:compile [INFO] | +- org.apache.directory.server:apacheds-protocol-ldap:jar:2.0.0-M15-SNAPSHOT:compile [INFO
[jira] [Commented] (DIRSERVER-1877) No-dependency ditribution for apache ds should be made available
[ https://issues.apache.org/jira/browse/DIRSERVER-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722294#comment-13722294 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1877: --- And here's another listing of what jars are included in the final jar: [INFO] Including org.apache.directory.server:apacheds-core-annotations:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-core:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-core-shared:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-admin:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-authn:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-authz:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-changelog:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-collective:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-event:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-exception:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-journal:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-normalization:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-operational:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-referral:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-schema:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-subtree:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-trigger:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including bouncycastle:bcprov-jdk15:jar:140 in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-ldif-partition:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-i18n:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-jdbm-partition:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-core-avl:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.jdbm:apacheds-jdbm1:bundle:2.0.0-M2 in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-xdbm-partition:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including commons-io:commons-io:jar:2.4 in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-core-api:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including commons-lang:commons-lang:jar:2.6 in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-core-constants:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-i18n:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-asn1-api:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-client-api:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including commons-pool:commons-pool:jar:1.6 in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-codec-core:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-extras-aci:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-extras-util:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.mina:mina-core:jar:2.0.7 in the shaded jar. [INFO] Including net.sf.ehcache:ehcache-core:jar:2.4.4 in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-service-builder:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-hash:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-extras-trigger:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-kerberos-codec:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-protocol-dhcp:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-protocol-dns:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-core
[jira] [Commented] (DIRSTUDIO-941) friendly name for attribute syntax not shown when creating new attribute
[ https://issues.apache.org/jira/browse/DIRSTUDIO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722296#comment-13722296 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-941: -- Good catch! Thanks for the report. Probably something changed in the underlying syntax classes and we forgot to update the display in this dialog. Thanks! friendly name for attribute syntax not shown when creating new attribute Key: DIRSTUDIO-941 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-941 Project: Directory Studio Issue Type: Improvement Components: studio-schemaeditor Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Richard Sand Attachments: screenshot-1.jpg, screenshot-2.jpg When creating new attributes, in the attribute syntax dropdown the OID is shown twice instead of the friendly name + OID, in contrast to the attribute editor window. See attached screenshots -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1877) No-dependency ditribution for apache ds should be made available
[ https://issues.apache.org/jira/browse/DIRSERVER-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722308#comment-13722308 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1877: --- In the dependencies tree, dependencies with scope 'compile' are mandatory, those with scopes 'provided' or 'test' are optional (only required for unit tests). In the dependencies list, jars are all mandatory. They are all included in the final all-in-one jar. No-dependency ditribution for apache ds should be made available Key: DIRSERVER-1877 URL: https://issues.apache.org/jira/browse/DIRSERVER-1877 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M13 Reporter: Anshuman Labels: apacheds, distribution, nodep The ApacheDS currently ships as a single service jar. This however includes all the dependencies bundled within it (ex: javax.servlet.*, mina, slf4j, etc). There should be option to download just the ApacheDS code so that when working in an embedded environment, unwanted dependencies can be avoided and for mandatory dependencies like mina, the application may chose a different version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1877) No-dependency ditribution for apache ds should be made available
[ https://issues.apache.org/jira/browse/DIRSERVER-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722397#comment-13722397 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1877: --- I took the example of the apacheds-service jar, which is the jar bundled with all our standalone distributions. It explains why it bundles also Log4J, because we want a façade for SLF4J, to be able to log events. Now, if you're to embed ApacheDS into your own code with your own requirements, of course, Log4J isn't mandatory and you're safe to decide whatever SLF4J façade you prefer. On the Jetty part, is it mandatory because ApacheDS has a feature to launch an embedded HTTP server. The idea here, is to be able to provide things like a DSML gateway or a JSON access service for example. If you don't plan to run the HTTP server in your embedded ApacheDS instance, you can forget it. No-dependency ditribution for apache ds should be made available Key: DIRSERVER-1877 URL: https://issues.apache.org/jira/browse/DIRSERVER-1877 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M13 Reporter: Anshuman Labels: apacheds, distribution, nodep The ApacheDS currently ships as a single service jar. This however includes all the dependencies bundled within it (ex: javax.servlet.*, mina, slf4j, etc). There should be option to download just the ApacheDS code so that when working in an embedded environment, unwanted dependencies can be avoided and for mandatory dependencies like mina, the application may chose a different version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-941) Friendly name for attribute syntax not shown when creating new attribute
[ https://issues.apache.org/jira/browse/DIRSTUDIO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-941: - Summary: Friendly name for attribute syntax not shown when creating new attribute (was: friendly name for attribute syntax not shown when creating new attribute) Friendly name for attribute syntax not shown when creating new attribute Key: DIRSTUDIO-941 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-941 Project: Directory Studio Issue Type: Improvement Components: studio-schemaeditor Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Richard Sand Attachments: screenshot-1.jpg, screenshot-2.jpg When creating new attributes, in the attribute syntax dropdown the OID is shown twice instead of the friendly name + OID, in contrast to the attribute editor window. See attached screenshots -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSTUDIO-941) Friendly name for attribute syntax not shown when creating new attribute
[ https://issues.apache.org/jira/browse/DIRSTUDIO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-941. -- Resolution: Fixed Fix Version/s: 2.0.0 2.0.0-M9 Assignee: Pierre-Arnaud Marcelot Fixed at revision 1508048. http://svn.apache.org/r1508048 Friendly name for attribute syntax not shown when creating new attribute Key: DIRSTUDIO-941 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-941 Project: Directory Studio Issue Type: Improvement Components: studio-schemaeditor Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Richard Sand Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M9, 2.0.0 Attachments: screenshot-1.jpg, screenshot-2.jpg When creating new attributes, in the attribute syntax dropdown the OID is shown twice instead of the friendly name + OID, in contrast to the attribute editor window. See attached screenshots -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRSERVER-1878) Bad warning from 'maven-shade-plugin' when creating the 'apacheds-service' jar
Pierre-Arnaud Marcelot created DIRSERVER-1878: - Summary: Bad warning from 'maven-shade-plugin' when creating the 'apacheds-service' jar Key: DIRSERVER-1878 URL: https://issues.apache.org/jira/browse/DIRSERVER-1878 Project: Directory ApacheDS Issue Type: Bug Reporter: Pierre-Arnaud Marcelot The 'maven-shade-plugin' reports a bad warning when creating the 'apacheds-service' jar: [WARNING] apacheds-protocol-kerberos-2.0.0-M15-SNAPSHOT.jar, apacheds-kerberos-codec-2.0.0-M15-SNAPSHOT.jar define 2 overlappping classes: [WARNING] - org.apache.directory.server.kerberos.protocol.codec.KerberosDecoder [WARNING] - org.apache.directory.server.kerberos.protocol.codec.KerberosEncoder [WARNING] maven-shade-plugin has detected that some .class files [WARNING] are present in two or more JARs. When this happens, only [WARNING] one single version of the class is copied in the uberjar. [WARNING] Usually this is not harmful and you can skeep these [WARNING] warnings, otherwise try to manually exclude artifacts [WARNING] based on mvn dependency:tree -Ddetail=true and the above [WARNING] output [WARNING] See http://docs.codehaus.org/display/MAVENUSER/Shade+Plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSERVER-1878) Bad warning from 'maven-shade-plugin' when creating the 'apacheds-service' jar
[ https://issues.apache.org/jira/browse/DIRSERVER-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSERVER-1878: -- Affects Version/s: 2.0.0-M14 Fix Version/s: 2.0.0-RC1 Bad warning from 'maven-shade-plugin' when creating the 'apacheds-service' jar -- Key: DIRSERVER-1878 URL: https://issues.apache.org/jira/browse/DIRSERVER-1878 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Reporter: Pierre-Arnaud Marcelot Fix For: 2.0.0-RC1 The 'maven-shade-plugin' reports a bad warning when creating the 'apacheds-service' jar: [WARNING] apacheds-protocol-kerberos-2.0.0-M15-SNAPSHOT.jar, apacheds-kerberos-codec-2.0.0-M15-SNAPSHOT.jar define 2 overlappping classes: [WARNING] - org.apache.directory.server.kerberos.protocol.codec.KerberosDecoder [WARNING] - org.apache.directory.server.kerberos.protocol.codec.KerberosEncoder [WARNING] maven-shade-plugin has detected that some .class files [WARNING] are present in two or more JARs. When this happens, only [WARNING] one single version of the class is copied in the uberjar. [WARNING] Usually this is not harmful and you can skeep these [WARNING] warnings, otherwise try to manually exclude artifacts [WARNING] based on mvn dependency:tree -Ddetail=true and the above [WARNING] output [WARNING] See http://docs.codehaus.org/display/MAVENUSER/Shade+Plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1878) Bad warning from 'maven-shade-plugin' when creating the 'apacheds-service' jar
[ https://issues.apache.org/jira/browse/DIRSERVER-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722523#comment-13722523 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1878: --- Here's the complete output of the build for the 'apacheds-service' project: [INFO] [INFO] Building ApacheDS All 2.0.0-M15-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ apacheds-all --- [INFO] Deleting /Users/pajbam/Development/Apache/trunks/apacheds/all/target [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ apacheds-all --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ apacheds-all --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /Users/pajbam/Development/Apache/trunks/apacheds/all/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ apacheds-all --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ apacheds-all --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /Users/pajbam/Development/Apache/trunks/apacheds/all/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ apacheds-all --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.15:test (default-test) @ apacheds-all --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ apacheds-all --- [INFO] Building jar: /Users/pajbam/Development/Apache/trunks/apacheds/all/target/apacheds-all-2.0.0-M15-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ apacheds-all --- [INFO] [INFO] --- maven-shade-plugin:2.1:shade (default) @ apacheds-all --- [INFO] Including org.apache.directory.server:apacheds-core:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-i18n:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-core-shared:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-admin:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-authn:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-authz:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-changelog:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-collective:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-event:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-exception:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-journal:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-normalization:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-operational:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-referral:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-schema:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-subtree:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.server:apacheds-interceptors-trigger:jar:2.0.0-M15-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-extras-trigger:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including commons-lang:commons-lang:jar:2.6 in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-codec-core:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-extras-util:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-model:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including antlr:antlr:jar:2.7.7 in the shaded jar. [INFO] Including org.apache.directory.api:api-ldap-schema-data:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including org.apache.directory.api:api-util:jar:1.0.0-M20-SNAPSHOT in the shaded jar. [INFO] Including bouncycastle:bcprov-jdk15:jar:140 in the shaded jar. [INFO] Including
[jira] [Commented] (DIRSERVER-1878) Bad warning from 'maven-shade-plugin' when creating the 'apacheds-service' jar
[ https://issues.apache.org/jira/browse/DIRSERVER-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722528#comment-13722528 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1878: --- After some time debugging the issue in the Maven build, here's what I found so far. The KerberosDecoder and KerberosEncoder classes are defined in the 'apacheds-kerberos-codec' project, package 'org.apache.directory.server.kerberos.protocol.codec'. The problem seem to be located in the 'apacheds-protocol-kerberos' project. This project does not contain any source for KerberosDecoder or KerberosEncoder classes and we can't find any trace of those compiled classes in the 'target/classes' directory. However, the generated jar includes those classes. It may related to the fact that this project depends on 'apacheds-kerberos-codec' and also defines a package of the name 'org.apache.directory.server.kerberos.protocol.codec'. In the pom.xml, the build definition for the 'maven-bundle-plugin' indicates to export all local packages and I believe this is why the 2 classes are present in the resulting jar. The fact that both project share the same package name is probably misleading. I was able to verify most of that by removing the manifest generation (done by the 'maven-bundle-plugin'). When the manifest generation isn't present in the pom.xml, the two classes are not there in the resulting jar. The best thing we could probably do to solve this issue is to avoid colliding package names. Bad warning from 'maven-shade-plugin' when creating the 'apacheds-service' jar -- Key: DIRSERVER-1878 URL: https://issues.apache.org/jira/browse/DIRSERVER-1878 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Reporter: Pierre-Arnaud Marcelot Fix For: 2.0.0-RC1 The 'maven-shade-plugin' reports a bad warning when creating the 'apacheds-service' jar: [WARNING] apacheds-protocol-kerberos-2.0.0-M15-SNAPSHOT.jar, apacheds-kerberos-codec-2.0.0-M15-SNAPSHOT.jar define 2 overlappping classes: [WARNING] - org.apache.directory.server.kerberos.protocol.codec.KerberosDecoder [WARNING] - org.apache.directory.server.kerberos.protocol.codec.KerberosEncoder [WARNING] maven-shade-plugin has detected that some .class files [WARNING] are present in two or more JARs. When this happens, only [WARNING] one single version of the class is copied in the uberjar. [WARNING] Usually this is not harmful and you can skeep these [WARNING] warnings, otherwise try to manually exclude artifacts [WARNING] based on mvn dependency:tree -Ddetail=true and the above [WARNING] output [WARNING] See http://docs.codehaus.org/display/MAVENUSER/Shade+Plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSERVER-1871) Logging Not Working in M14
[ https://issues.apache.org/jira/browse/DIRSERVER-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSERVER-1871. --- Resolution: Fixed Fix Version/s: 2.0.0-M14 Assignee: Pierre-Arnaud Marcelot Fixed at revision 1507063. http://svn.apache.org/r1507063 Logging Not Working in M14 -- Key: DIRSERVER-1871 URL: https://issues.apache.org/jira/browse/DIRSERVER-1871 Project: Directory ApacheDS Issue Type: Bug Components: core Affects Versions: 2.0.0-M14 Environment: Linux Reporter: Jonathan Rosenberg Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-M14 Changing logging priortiy of root logger does not cause logging. Here is log4j.priorities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSERVER-1871) Logging Not Working in M14
[ https://issues.apache.org/jira/browse/DIRSERVER-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSERVER-1871: -- Fix Version/s: (was: 2.0.0-M14) 2.0.0-RC1 Logging Not Working in M14 -- Key: DIRSERVER-1871 URL: https://issues.apache.org/jira/browse/DIRSERVER-1871 Project: Directory ApacheDS Issue Type: Bug Components: core Affects Versions: 2.0.0-M14 Environment: Linux Reporter: Jonathan Rosenberg Assignee: Pierre-Arnaud Marcelot Priority: Critical Fix For: 2.0.0-RC1 Changing logging priortiy of root logger does not cause logging. Here is log4j.priorities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1871) Logging Not Working in M14
[ https://issues.apache.org/jira/browse/DIRSERVER-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718059#comment-13718059 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1871: --- Hi Jonathan, I checked most of the ApacheDS installers (Binary, Debian, OS X, Archive zip and tar.gz) and logging works for all them. Now, changing the root logger level is not enough to have logs showing, you also need to change the log level on the particular logs you're interested in and we have more than 10 different depending on which part of the server you'd like to log (LDAP protocol, database, ACI, etc.). Those are located at the end of the log4j.properties file: | log4j.logger.jdbm.recman.BaseRecordManager=FATAL | log4j.logger.org.apache.directory.server.OPERATIONS_LOG=FATAL | log4j.logger.org.apache.directory.server.OPERATION_TIME=FATAL | log4j.logger.org.apache.directory.api.CODEC_LOG=FATAL | log4j.logger.org.apache.directory.server.ACI_LOG=FATAL | log4j.logger.org.apache.directory.server.PROVIDER_LOG=FATAL | log4j.logger.org.apache.directory.server.CONSUMER_LOG=FATAL | log4j.logger.org.apache.directory.CURSOR_LOG=FATAL | log4j.logger.org.apache.directory.api=FATAL | log4j.logger.org.apache.directory.server=DEBUG | log4j.logger.net.sf.ehcache=FATAL | log4j.logger.org.apache.mina=FATAL I'll create/update a page in the ApacheDS documentation to make it easier to understand and have a real reference on how to enable logging for ApacheDS. Logging Not Working in M14 -- Key: DIRSERVER-1871 URL: https://issues.apache.org/jira/browse/DIRSERVER-1871 Project: Directory ApacheDS Issue Type: Bug Components: core Affects Versions: 2.0.0-M14 Environment: Linux Reporter: Jonathan Rosenberg Priority: Critical Changing logging priortiy of root logger does not cause logging. Here is log4j.priorities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[ApacheDS] Review and modified version of the 'log4j.properties' file bundled in the distributions
Hi,
A recent discussion on IRC and the mailing list, followed by the creation of
DIRSERVER-1871 [1] made me look at the way logs could be activated and
specifically the 'log4j.properties' file we bundle in the distributions.
Here's the content of the current version of this file:
#
#Licensed to the Apache Software Foundation (ASF) under one or more
#contributor license agreements. See the NOTICE file distributed with
#this work for additional information regarding copyright ownership.
#The ASF licenses this file to You under the Apache License, Version 2.0
#(the License); you may not use this file except in compliance with
#the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
#Unless required by applicable law or agreed to in writing, software
#distributed under the License is distributed on an AS IS BASIS,
#WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#See the License for the specific language governing permissions and
#limitations under the License.
#
log4j.rootCategory=WARN, R, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=${apacheds.log.dir}/apacheds.log
log4j.appender.R.MaxFileSize=1024KB
# Keep some backup files
log4j.appender.R.MaxBackupIndex=5
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
log4j.appender.stdout.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
# with these we'll not get innundated when switching to DEBUG
log4j.logger.jdbm.recman.BaseRecordManager=FATAL
log4j.logger.org.apache.directory.server.OPERATION_LOG=FATAL
log4j.logger.org.apache.directory.server.OPERATION_TIME=FATAL
log4j.logger.org.apache.directory.api.CODEC_LOG=FATAL
log4j.logger.org.apache.directory.server.ACI_LOG=FATAL
log4j.logger.org.apache.directory.server.PROVIDER_LOG=FATAL
log4j.logger.org.apache.directory.server.CONSUMER_LOG=FATAL
log4j.logger.org.apache.directory.CURSOR_LOG=FATAL
log4j.logger.org.apache.directory.api=FATAL
log4j.logger.org.apache.directory.server=FATAL
log4j.logger.net.sf.ehcache=FATAL
log4j.logger.org.apache.mina=FATAL
A few comments on it.
First, we have two appenders ('R' 'stdout').
I don't really see the utility of having these two. The RollingFileAppender
should be enough.
What happens now with the ConsoleAppender is that any log we can find in the
'apacheds.log' is then duplicated in the 'wrapper.log' file, mandatory log file
for the Tanuki wrapper whichs logs succesful or failed launched and termination
attempts of the server.
Personally, I would get rid of the ConsoleAppender (unfortunately, we will have
two different log files but there's not that can be done about that).
I also took the liberty to modify the RollingFileAppender settings to something
more useful than the current values.
I increased 'MaxFileSize' to '100MB' and decreased 'MaxBackupIndex' to '3'.
So, at most that would be 300 MB dedicated to logs.
It looks enough for me.
Last but not least, I fixed what was causing most of our log issues.
At the end of the file, there are a lot of specific loggers all set to FATAL.
Two are especially interesting, 'org.apache.directory.api'
'org.apache.directory.server'. Setting these ones to 'FATAL' means that we will
only log severe errors for all classes of the LDAP API and ApacheDS.
But it also means that the setting of the root logger at the beginning of the
file has absolutely no effect, hence the problems we've been having with log
activations.
I propose that we keep these definitions, which are very useful when we need to
debug things in the server, but that they should be set with a 'DEBUG' log
level and be deactivated by default.
In the end, an updated version of the file looks like this:
#
#Licensed to the Apache Software Foundation (ASF) under one or more
#contributor license agreements. See the NOTICE file distributed with
#this work for additional information regarding copyright ownership.
#The ASF licenses this file to You under the Apache License, Version 2.0
#(the License); you may not use this file except in compliance with
#the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
#Unless required by applicable law or agreed to in writing, software
#distributed under the License is distributed on an AS IS BASIS,
#WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#See the License for
Re: [ApacheDS] Review and modified version of the 'log4j.properties' file bundled in the distributions
On 24 juil. 2013, at 15:50, Kiran Ayyagari kayyag...@apache.org wrote: no objection as long as this change is part of the installer specific files, I want the console appender to be retained in service module which is used for most of the testing during development Exactly. It won't change the development config in the build. This is only intended to be used with the distributions. Regards, Pierre-Arnaud
Re: [ApacheDS] Review and modified version of the 'log4j.properties' file bundled in the distributions
On 24 juil. 2013, at 15:54, Pierre-Arnaud Marcelot p...@marcelot.net wrote: On 24 juil. 2013, at 15:50, Kiran Ayyagari kayyag...@apache.org wrote: no objection as long as this change is part of the installer specific files, I want the console appender to be retained in service module which is used for most of the testing during development Exactly. It won't change the development config in the build. This is only intended to be used with the distributions. Just a small addition. There is a kind of distribution that will still require the console appender, it's the Archive (zip tar.gz) distribution. In this distrib, ApacheDS is run from the command line in an interactive mode (meaning that CTL+C kills the process) So I think it makes sense to still keep the log directed to the console (in addition to the file). Regards, Pierre-Arnaud
[jira] [Commented] (DIRSERVER-1871) Logging Not Working in M14
[
https://issues.apache.org/jira/browse/DIRSERVER-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718593#comment-13718593
]
Pierre-Arnaud Marcelot commented on DIRSERVER-1871:
---
Jonathan,
Could you try with this new 'log4j.properties' file?
#
#Licensed to the Apache Software Foundation (ASF) under one or more
#contributor license agreements. See the NOTICE file distributed with
#this work for additional information regarding copyright ownership.
#The ASF licenses this file to You under the Apache License, Version 2.0
#(the License); you may not use this file except in compliance with
#the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
#Unless required by applicable law or agreed to in writing, software
#distributed under the License is distributed on an AS IS BASIS,
#WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#See the License for the specific language governing permissions and
#limitations under the License.
#
log4j.rootCategory=WARN, F
log4j.appender.F=org.apache.log4j.RollingFileAppender
log4j.appender.F.File=${apacheds.log.dir}/apacheds.log
log4j.appender.F.MaxFileSize=100MB
log4j.appender.F.MaxBackupIndex=3
log4j.appender.F.layout=org.apache.log4j.PatternLayout
log4j.appender.F.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
# Specific loggers (useful for debugging)
#log4j.logger.jdbm.recman.BaseRecordManager=DEBUG
#log4j.logger.org.apache.directory.server.OPERATION_LOG=DEBUG
#log4j.logger.org.apache.directory.server.OPERATION_TIME=DEBUG
#log4j.logger.org.apache.directory.api.CODEC_LOG=DEBUG
#log4j.logger.org.apache.directory.server.ACI_LOG=DEBUG
#log4j.logger.org.apache.directory.server.PROVIDER_LOG=DEBUG
#log4j.logger.org.apache.directory.server.CONSUMER_LOG=DEBUG
#log4j.logger.org.apache.directory.CURSOR_LOG=DEBUG
#log4j.logger.org.apache.directory.api=DEBUG
#log4j.logger.org.apache.directory.server=DEBUG
#log4j.logger.net.sf.ehcache=DEBUG
#log4j.logger.org.apache.mina=DEBUG
I also wrote a documentation about logs which is currently awaiting validation
on our staging website:
http://directory.staging.apache.org/apacheds/advanced-ug/5.3-logs.html
Is logging working properly with this?
Any comment on the documentation is very welcomed.
Thanks!
Logging Not Working in M14
--
Key: DIRSERVER-1871
URL: https://issues.apache.org/jira/browse/DIRSERVER-1871
Project: Directory ApacheDS
Issue Type: Bug
Components: core
Affects Versions: 2.0.0-M14
Environment: Linux
Reporter: Jonathan Rosenberg
Priority: Critical
Changing logging priortiy of root logger does not cause logging. Here is
log4j.priorities
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Failure when creating a new entity using a custom object class that includes a SUP attribute
: Pierre-Arnaud Marcelot [mailto:paj...@gmail.com] De la part de
Pierre-Arnaud Marcelot
Envoyé : Monday, July 22, 2013 7:26 PM
À : Apache Directory Developers List
Cc : Emmanuel GUITON
Objet : Re: Failure when creating a new entity using a custom object class
that includes a SUP attribute
Hi Emmanuel,
I don't know if it's your mail client but your mail got to us in a pretty bad
shape :(
Could you try to re-send it again with proper formatting? Thanks!
Regards,
Pierre-Arnaud
On 22 juil. 2013, at 19:17, Emmanuel GUITON emmanuel.gui...@intrinsec.com
wrote:
Hello,In an embbeded Apache DS instance, I am trying to add an entity using
a custom object class but it fails. Here is the scenario :First, I set up a
default Apache DS instance, with the schema defined in (maven) :
dependency
groupIdorg.apache.directory.api/groupId
artifactIdapi-ldap-schema-data/artifactId
version1.0.0-M19/version/dependencyThen, I add
(programatically) my custom type using the JNDI. This type extends the
'organization' object class. Browsing the schema with a GUI tool (JXplorer),
I ensure my custom object class was successfully added.After that, I add a
new entity (using the JNDI once again or using the GUI tool) and the
following exception is thrown
:javax.naming.directory.SchemaViolationException: [LDAP: error code 65 -
OBJECT_CLASS_VIOLATION: failed for MessageType : ADD_REQUESTMessage ID : 5
Add Request :Entrydn[n]: o=Test,dc=company,dc=comobjectClass:
orgExtendedo: TestOpaqueControl ControlType OID:
'2.16.840.1.113730.3.4.2'Criticality : 'false'': ERR_277 Attribute o
not declared in objectClasses of entry o=Test,dc=company,dc=com]; remaining
name 'o=Test,dc=company,dc=com'However, I did specify the value of the 'o'
attribute, which is defined in the parent object class (organization).I
stress that the object class definition includes a SUP attribute. I have
other custom object classes without SUP attribute. I can successfully create
new entities using these other object classes.Is this a bug or am I missing
something ?Hereafter, you can find a complete (client side) code snippet to
repeat this behaviour.Thanks for any help, - emmanuelpackage
com.company.directory.client;import java.util.Hashtable;import
javax.naming.Context;import javax.naming.Name;import
javax.naming.NamingException;import javax.naming.directory.Attributes;import
javax.naming.directory.BasicAttributes;import
javax.naming.directory.DirContext;import
javax.naming.directory.InitialDirContext;import
javax.naming.ldap.LdapName;public class ApacheDsTest{ public static
void main(final String[] args){ try {
// Init connection to the LDAP server final
HashtableString, String env = new HashtableString, String();
env.put(Context.INITIAL_CONTEXT_FACTORY,
com.sun.jndi.ldap.LdapCtxFactory);
env.put(Context.PROVIDER_URL, TestUtils.PROVIDER_URL);
env.put(Context.SECURITY_AUTHENTICATION, simple);
env.put(java.naming.ldap.derefAliases, always);
env.put(Context.SECURITY_PRINCIPAL, uid=admin,ou=system);
env.put(Context.SECURITY_CREDENTIALS, secret);
final DirContext context = new InitialDirContext(env);
// Add new objectClass, extends organization
final Attributes attrs = new BasicAttributes();
attrs.put(NUMERICOID, 1.3.6.1.4.1.8654.4.1);
attrs.put(NAME, orgExtended); attrs.put(DESC,
Extension of the organization object class);
attrs.put(SUP, organization);
attrs.put(STRUCTURAL, TRUE);final DirContext
schemaContext = context.getSchema();
schemaContext.createSubcontext(ClassDefinition/orgExtended, attrs);
// dn: o=Test,dc=company,dc=com,
objectClass: orgExtended, o: Testfinal Name name
= new LdapName(o=Test,dc=company,dc=com); final
Attributes attributes=new BasicAttributes();
attributes.put(objectClass, orgExtended);
attributes.put(o, Test);
context.createSubcontext(name, attributes); }
catch (final NamingException exception) {
System.err.println(exception); } }}
Emmanuel GUITON
Ingénieur Développement
Fixe : +33 1 70 92 84 16 l Standard : +33 1 41 91 77 77
215, Avenue Georges Clemenceau l 92024 Nanterre
http://www.intrinsec.com/ http://www.intrinsec.com/
Re: After adding new m-may attribute to a custom class in a schema, can't then add the attribute to an entry
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 the fly as well.
On the Studio side, if you've modified the schema without closing/reopening the
connection or manually reloading the schema (in the connection's properties or
in the Schema view), the modification won't be reflected, hence the message you
got.
A simple close/reopen of the connection should fix that.
Regards
Pierre-Arnaud
On 23 juil. 2013, at 16:39, Matthew Goudge matthew.gou...@qxlva.com wrote:
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
objectclass: metaObjectClass
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.26156.30.0.0.1.12
m-name: adapterMailbox
m-supObjectClass: top
m-must: email
m-must: smtpHost
m-must: smtpPort
m-must: userPassword
Further changes then required the addition of an optional enabled/disabled
flag, so the following update ldif was created:
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.0.1, ou=attributeTypes, cn=conneqt-config,
ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.26156.30.0.0.0.1
m-name: isActiveFlag
m-description: A boolean flag to indicate if an entry is active or not
m-equality: caseIgnoreMatch
m-ordering: booleanMatch
m-syntax: 1.3.6.1.4.1.1466.115.121.1.7
m-length: 1
m-singleValue: TRUE
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.1.12, ou=objectClasses, cn=conneqt-config,
ou=schema
changetype: modify
add: m-may
m-may: isActiveFlag
Now the problems I have are two-fold: firstly, when I try to add the
isActiveFlag attribute to an entry through Apache Directory Studio, it gives
a warning saying the attribute type is not allowed. Whilst I can click
through this, the second problem is that when I try to add entries
programmatically:
var name = string.Format(email={0}, emailAddress);
var entry = container.Children.Add(name, adapterMailbox);
entry.Properties[userPassword].Value = password;
entry.Properties[smtpHost].Value = smtpHost;
entry.Properties[smtpPort].Value = smtpPort;
entry.Properties[isActiveFlag].Value = isActiveFlag;
entry.CommitChanges();
It is throwing a DirectoryServicesCOMException with message “The requested
operation did not satisfy one or more constraints associated with the class
of the object.”
Anyone able to shed any light on what might be going on?
Cheers
Matthew Goudge
Developer
image001.gif
Quicksilva Systems Integration Solutions | www.qxlva.com
Tel: 01249 751 000 | matthew.gou...@qxlva.com
image002.gifimage003.gifimage004.gif
__
The Company gives no warranty as to the accuracy or completeness of
electronic mail messages sent over the Internet and accepts no responsibility
for changes made after it was sent. Any opinion expressed in this email may
be personal to the author, may not necessarily reflect the opinions of the
Company or its affiliates and may be subject to change without notice.
The information contained in this communication is confidential and/or
proprietary business or technical data. If you are not the intended
recipient, you are hereby notified that any dissemination, copying or
distribution of this communication, or the taking of any action in reliance
on the contents of this communication, is strictly prohibited. If you have
received this communication in error, please immediately notify us
electronically by return message, and delete or destroy all copies of this
communication.
Quicksilva Limited, Reg No 3860799, Incorporated at Companies House, Cardiff.
Registered Office: Langley Gate, Swindon Road, Chippenham, Wiltshire, SN15
5SE. Vat Reg No 762 8082 16.
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
[jira] [Commented] (DIRSTUDIO-938) LDAP Browser shows non ascii symbols as escaped
[ https://issues.apache.org/jira/browse/DIRSTUDIO-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714962#comment-13714962 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-938: -- I've debugged this a bit. We actually render the DN exactly how it is retrieved from the directory server (at least on ApacheDS). So, we do display the DN correctly if the entry was created with a non-escaped DN, and _not_ if if was created with an escaped DN. I will dig a bit more into that. LDAP Browser shows non ascii symbols as escaped --- Key: DIRSTUDIO-938 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-938 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Adamansky Anton LDAP Browser shows non ascii symbols as escaped. For example: ou=Подразделение,dc=structure (in Russian) shown as ou=\D0\9F\D0\BE\D0\B4\D1\80\D0\B0\D0\B7\D0\B4\D0\B5\D0\BB\D0\B5\D0\BD\D0\B8\D0\B5,dc=structure It's very difficult and inconvenient to navigate LDAP tree with escaped names. Please fix it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-938) LDAP Browser shows non ascii symbols as escaped
[ https://issues.apache.org/jira/browse/DIRSTUDIO-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-938: - Attachment: Screen Shot 2013-07-22 at 09.05.30.png Screen Shot 2013-07-22 at 09.04.55.png Here are two screenshots demonstrating what I've found so far. LDAP Browser shows non ascii symbols as escaped --- Key: DIRSTUDIO-938 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-938 Project: Directory Studio Issue Type: Bug Components: studio-ldapbrowser Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Adamansky Anton Attachments: Screen Shot 2013-07-22 at 09.04.55.png, Screen Shot 2013-07-22 at 09.05.30.png LDAP Browser shows non ascii symbols as escaped. For example: ou=Подразделение,dc=structure (in Russian) shown as ou=\D0\9F\D0\BE\D0\B4\D1\80\D0\B0\D0\B7\D0\B4\D0\B5\D0\BB\D0\B5\D0\BD\D0\B8\D0\B5,dc=structure It's very difficult and inconvenient to navigate LDAP tree with escaped names. Please fix it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Failure when creating a new entity using a custom object class that includes a SUP attribute
Hi Emmanuel,
I don't know if it's your mail client but your mail got to us in a pretty bad
shape :(
Could you try to re-send it again with proper formatting? Thanks!
Regards,
Pierre-Arnaud
On 22 juil. 2013, at 19:17, Emmanuel GUITON emmanuel.gui...@intrinsec.com
wrote:
Hello,In an embbeded Apache DS instance, I am trying to add an entity using a
custom object class but it fails. Here is the scenario :First, I set up a
default Apache DS instance, with the schema defined in (maven) :
dependencygroupIdorg.apache.directory.api/groupId
artifactIdapi-ldap-schema-data/artifactId
version1.0.0-M19/version/dependencyThen, I add
(programatically) my custom type using the JNDI. This type extends the
'organization' object class. Browsing the schema with a GUI tool (JXplorer),
I ensure my custom object class was successfully added.After that, I add a
new entity (using the JNDI once again or using the GUI tool) and the
following exception is thrown
:javax.naming.directory.SchemaViolationException: [LDAP: error code 65 -
OBJECT_CLASS_VIOLATION: failed for MessageType : ADD_REQUESTMessage ID : 5
Add Request :Entrydn[n]: o=Test,dc=company,dc=comobjectClass:
orgExtendedo: TestOpaqueControl ControlType OID:
'2.16.840.1.113730.3.4.2'Criticality : 'false'': ERR_277 Attribute o
not declared in objectClasses of entry o=Test,dc=company,dc=com]; remaining
name 'o=Test,dc=company,dc=com'However, I did specify the value of the 'o'
attribute, which is defined in the parent object class (organization).I
stress that the object class definition includes a SUP attribute. I have
other custom object classes without SUP attribute. I can successfully create
new entities using these other object classes.Is this a bug or am I missing
something ?Hereafter, you can find a complete (client side) code snippet to
repeat this behaviour.Thanks for any help, - emmanuelpackage
com.company.directory.client;import java.util.Hashtable;import
javax.naming.Context;import javax.naming.Name;import
javax.naming.NamingException;import javax.naming.directory.Attributes;import
javax.naming.directory.BasicAttributes;import
javax.naming.directory.DirContext;import
javax.naming.directory.InitialDirContext;import
javax.naming.ldap.LdapName;public class ApacheDsTest{ public static
void main(final String[] args){ try {
// Init connection to the LDAP server final
HashtableString, String env = new HashtableString, String();
env.put(Context.INITIAL_CONTEXT_FACTORY,
com.sun.jndi.ldap.LdapCtxFactory);
env.put(Context.PROVIDER_URL, TestUtils.PROVIDER_URL);
env.put(Context.SECURITY_AUTHENTICATION, simple);
env.put(java.naming.ldap.derefAliases, always);
env.put(Context.SECURITY_PRINCIPAL, uid=admin,ou=system);
env.put(Context.SECURITY_CREDENTIALS, secret);
final DirContext context = new InitialDirContext(env);
// Add new objectClass, extends organization
final Attributes attrs = new BasicAttributes();
attrs.put(NUMERICOID, 1.3.6.1.4.1.8654.4.1);
attrs.put(NAME, orgExtended); attrs.put(DESC,
Extension of the organization object class);
attrs.put(SUP, organization);
attrs.put(STRUCTURAL, TRUE);final DirContext
schemaContext = context.getSchema();
schemaContext.createSubcontext(ClassDefinition/orgExtended, attrs);
// dn: o=Test,dc=company,dc=com,
objectClass: orgExtended, o: Testfinal Name name
= new LdapName(o=Test,dc=company,dc=com); final
Attributes attributes=new BasicAttributes();
attributes.put(objectClass, orgExtended);
attributes.put(o, Test);
context.createSubcontext(name, attributes); } catch
(final NamingException exception) {
System.err.println(exception); } }}
Emmanuel GUITON
Ingénieur Développement
Fixe : +33 1 70 92 84 16 l Standard : +33 1 41 91 77 77
215, Avenue Georges Clemenceau l 92024 Nanterre
http://www.intrinsec.com/
http://www.intrinsec.com/
[jira] [Updated] (DIRSTUDIO-937) No password confirmation while changing it
[ https://issues.apache.org/jira/browse/DIRSTUDIO-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-937: - Fix Version/s: 2.0.0-M9 Assignee: Pierre-Arnaud Marcelot No password confirmation while changing it -- Key: DIRSTUDIO-937 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-937 Project: Directory Studio Issue Type: Improvement Environment: Apache Directory Studio plugin 2.0.0 in Eclipse Kepler Reporter: Askat Asanaliev Assignee: Pierre-Arnaud Marcelot Priority: Minor Fix For: 2.0.0-M9 When I change my password there is only one field new password. There is no any confirmation field. If I enter a new password with a typo I will not be able to log in next time. I have to ask an administrator to change my password again. With the confirmation field such case can be eliminated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-937) No password confirmation while changing it
[ https://issues.apache.org/jira/browse/DIRSTUDIO-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713854#comment-13713854 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-937: -- Indeed. We can try to add a second verification password field. No password confirmation while changing it -- Key: DIRSTUDIO-937 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-937 Project: Directory Studio Issue Type: Improvement Environment: Apache Directory Studio plugin 2.0.0 in Eclipse Kepler Reporter: Askat Asanaliev Priority: Minor When I change my password there is only one field new password. There is no any confirmation field. If I enter a new password with a typo I will not be able to log in next time. I have to ask an administrator to change my password again. With the confirmation field such case can be eliminated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
