[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)
[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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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)
[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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}
[...]
org.apache.felix
maven-bundle-plugin
true
true
[...]
{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 :
>
> org.apache.directory.server
> apacheds-server-jndi
> 2.0.0-M6
>
> It should transitively depend on a "jar" type, not a bundle.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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] [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] [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] [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] [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
[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] [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
[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] [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] [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] [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-tabpanel&focusedCommentId=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] [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] [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] [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: - 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] [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] [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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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-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-tabpanel&focusedCommentId=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
[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-tabpanel&focusedCommentId=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-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-tabpanel&focusedCommentId=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.(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-tabpanel&focusedCommentId=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.(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] (DIRSERVER-1880) ApacheDS failed to start on boot
[ https://issues.apache.org/jira/browse/DIRSERVER-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[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-tabpanel&focusedCommentId=13729436#comment-13729436 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1880: --- Hi Frank, So, ApacheDS does start, but only manually, right? Could you use the log4.properties from this jira issue, DIRSERVER-1871? https://issues.apache.org/jira/browse/DIRSERVER-1871?focusedCommentId=13718593&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13718593 In the meantime, I'll experiment on a Ubuntu VM to see if I can reproduce the issue. Thanks. > 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-1880) ApacheDS failed to start on boot
[ https://issues.apache.org/jira/browse/DIRSERVER-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [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] [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] [Resolved] (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 resolved DIRSTUDIO-942. -- Resolution: Fixed Fix Version/s: 2.0.0-M9 Assignee: Pierre-Arnaud Marcelot Fixed at revision 1509275. http://svn.apache.org/r1509275 Thanks for the report! > 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 >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-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-tabpanel&focusedCommentId=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] [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
[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] [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] [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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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 org.apache.dir
[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] [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] [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] [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] [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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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] (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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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-jn
[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-tabpanel&focusedCommentId=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] | | +- org.apache
[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] [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] [Commented] (DIRSERVER-1871) Logging Not Working in M14
[
https://issues.apache.org/jira/browse/DIRSERVER-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[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-tabpanel&focusedCommentId=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
[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
[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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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
[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-935) Reading root DSE
[ https://issues.apache.org/jira/browse/DIRSTUDIO-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705843#comment-13705843 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-935: -- The class you're looking for is probably "InitializeRootDSERunnable". /ldapbrowser.core/src/main/java/org/apache/directory/studio/ldapbrowser/core/jobs/InitializeRootDSERunnable.java Hope this helps. > Reading root DSE > > > Key: DIRSTUDIO-935 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-935 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M8 (2.0.0.v20130628) > Environment: Windows 8 64-bit, Java 7 >Reporter: Aleks M > > Hello > How can I troubleshoot this issue. > When connected to an older version of eDirectory and when clicking on the > Root DSE I can see all the attributes available on the Root DSE. > When I connect to a newer version, in my case 887, Studio displays just the > following: > namingContexts, subschemaEntry, supportedControl, supportedExtension, > supportedFeatures, supportedLDAPVersion, supportedSASLMechanisms, vendorName, > vendorVersion. > Reading the root DSE using another others LDAP tools works fine. > Which Java class performs the reading of the root DSE? -- 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-883) No search selected
[ https://issues.apache.org/jira/browse/DIRSTUDIO-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705727#comment-13705727 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-883: -- Thanks Aleks. I'll give it a try and debug on Windows then. > No search selected > -- > > Key: DIRSTUDIO-883 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-883 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M5 (2.0.0.v20130131) > Environment: Windows 8, Java 7u15 >Reporter: Aleks M > > I have multiple connections that I switch between and I have at least one > search opened in each connection. > Sometimes when switching between connections Studio switches to a tab named > No search selected. > If you then click on a search it will be displayed in that tab. > If you click on a search result in the LDAP Browser view (the tree view) > Studio won't switch to the entry editor tab. Instead it will just display "No > search selected" in the current tab. > You can also replicate this issue by having two connections, in connection > one select an object in the LDAP browser view so that the entry editor is > displayed. > Swith to connection two and perform a search. Switch back to connection one, > instead of showing you the entry editor where you were it displays the No > search selected tab. -- 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-934) Exporting the configuration from the ApacheDS 2.0 Configuration Editor should not change the input
[ https://issues.apache.org/jira/browse/DIRSTUDIO-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-934. -- Resolution: Fixed Fixed with revision 1502156. http://svn.apache.org/r1502156 > Exporting the configuration from the ApacheDS 2.0 Configuration Editor should > not change the input > -- > > Key: DIRSTUDIO-934 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-934 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M8 (2.0.0.v20130628) >Reporter: Pierre-Arnaud Marcelot >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M9, 2.0.0 > > > Exporting the configuration from the ApacheDS 2.0 Configuration Editor should > not change the input. > At the moment, the input is changed, as if we did a "Save As…" action. > The original input should be the same and not be modified. -- 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] (DIRSTUDIO-934) Exporting the configuration from the ApacheDS 2.0 Configuration Editor should not change the input
Pierre-Arnaud Marcelot created DIRSTUDIO-934: Summary: Exporting the configuration from the ApacheDS 2.0 Configuration Editor should not change the input Key: DIRSTUDIO-934 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-934 Project: Directory Studio Issue Type: Bug Components: studio-apacheds-configuration Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M9, 2.0.0 Exporting the configuration from the ApacheDS 2.0 Configuration Editor should not change the input. At the moment, the input is changed, as if we did a "Save As…" action. The original input should be the same and not be modified. -- 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-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:comment-tabpanel&focusedCommentId=13705608#comment-13705608 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-903: -- Hi Guillermo, You subscribe to our 'users' or 'dev' mailing lists if you like: http://directory.apache.org/mailing-lists-and-irc.html Or you can also subscribe to the Apache 'announce' list where all Apache projects announce their new release: http://www.apache.org/foundation/mailinglists.html#foundation-announce Hope this helps. > 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 >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: - Fix Version/s: (was: 2.0.0-M7 (2.0.0.v20130517)) 2.0.0-M9 > 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 >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] [Commented] (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:comment-tabpanel&focusedCommentId=13700730#comment-13700730 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-903: -- Finally fixed with this last commit: 1500017. http://svn.apache.org/r1500017 > 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 >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] [Commented] (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:comment-tabpanel&focusedCommentId=13700705#comment-13700705 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-903: -- My bad! That was in fact a bug in the code… :D The test on the empty string was not properly working in the case where "Plaintext" was used. I only tested with others encryption mechanisms. > 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 >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-M7 (2.0.0.v20130517), 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] [Commented] (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:comment-tabpanel&focusedCommentId=13700636#comment-13700636 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-903: -- I can confirm that on Windows, the fix for the empty field doesn't work. "Write once, run anywhere" they say… :( Investigating now... > 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 >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-M7 (2.0.0.v20130517), 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] [Commented] (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:comment-tabpanel&focusedCommentId=13700613#comment-13700613 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-903: -- Actually, in "New Password" mode, if the field is empty the button should be disabled. Let me verify this on a Windows VM. BTW, we released a new version yesterday: Apache Directory Studio 2.0.0-M8. > 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 >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-M7 (2.0.0.v20130517), 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] [Resolved] (DIRSTUDIO-932) NPE while importing an ApacheDS 2.0 configuration from within the editor
[ https://issues.apache.org/jira/browse/DIRSTUDIO-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-932. -- Resolution: Fixed Fix Version/s: 2.0.0-M9 Fixed at revision 1499028. http://svn.apache.org/r1499028 > NPE while importing an ApacheDS 2.0 configuration from within the editor > > > Key: DIRSTUDIO-932 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-932 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Ubuntu 13.04 >Reporter: Łukasz Adamczyk >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M9 > > Attachments: apache-ds-200m14-conf.ldif > > > Import of Apache DS 2.0 configuration fails even when you import just > exported, default ldif with configuration. > http://imageshack.us/photo/my-images/594/kpej.png/ -- 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-932) NPE while importing an ApacheDS 2.0 configuration from within the editor
[ https://issues.apache.org/jira/browse/DIRSTUDIO-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-932: - Assignee: Pierre-Arnaud Marcelot Summary: NPE while importing an ApacheDS 2.0 configuration from within the editor (was: Import Apache DS 2.0 configuration fails) > NPE while importing an ApacheDS 2.0 configuration from within the editor > > > Key: DIRSTUDIO-932 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-932 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Ubuntu 13.04 >Reporter: Łukasz Adamczyk >Assignee: Pierre-Arnaud Marcelot > Attachments: apache-ds-200m14-conf.ldif > > > Import of Apache DS 2.0 configuration fails even when you import just > exported, default ldif with configuration. > http://imageshack.us/photo/my-images/594/kpej.png/ -- 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-932) Import Apache DS 2.0 configuration fails
[ https://issues.apache.org/jira/browse/DIRSTUDIO-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697960#comment-13697960 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-932: -- Oh, right. I thought you were opening it via "File" > "Open…". Indeed, I get the error when I try import it using the editor button. > Import Apache DS 2.0 configuration fails > > > Key: DIRSTUDIO-932 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-932 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Ubuntu 13.04 >Reporter: Łukasz Adamczyk > Attachments: apache-ds-200m14-conf.ldif > > > Import of Apache DS 2.0 configuration fails even when you import just > exported, default ldif with configuration. > http://imageshack.us/photo/my-images/594/kpej.png/ -- 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-932) Import Apache DS 2.0 configuration fails
[ https://issues.apache.org/jira/browse/DIRSTUDIO-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697874#comment-13697874 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-932: -- This file loads fine with the latest 2.0.0-M8 (2.0.0.v20130628) version (being currently mirrored) as far as I can tell. > Import Apache DS 2.0 configuration fails > > > Key: DIRSTUDIO-932 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-932 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Ubuntu 13.04 >Reporter: Łukasz Adamczyk > Attachments: apache-ds-200m14-conf.ldif > > > Import of Apache DS 2.0 configuration fails even when you import just > exported, default ldif with configuration. > http://imageshack.us/photo/my-images/594/kpej.png/ -- 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-932) Import Apache DS 2.0 configuration fails
[ https://issues.apache.org/jira/browse/DIRSTUDIO-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697846#comment-13697846 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-932: -- Ok, in that case, that's another issue. Could you share your config.ldif file please? Thanks! > Import Apache DS 2.0 configuration fails > > > Key: DIRSTUDIO-932 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-932 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Ubuntu 13.04 >Reporter: Łukasz Adamczyk > > Import of Apache DS 2.0 configuration fails even when you import just > exported, default ldif with configuration. > http://imageshack.us/photo/my-images/594/kpej.png/ -- 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-932) Import Apache DS 2.0 configuration fails
[ https://issues.apache.org/jira/browse/DIRSTUDIO-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697830#comment-13697830 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-932: -- What the version of the ApacheDS? If it's 2.0.0-M13 or 2.0.0-M14, note that Apache Directory Studio 2.0.0-M7 (2.0.0.v20130517) is compatible with them, since they include a new attribute type for the configuration. Version 2.0.0-M8 has been voted to fix this issue (and more) and is currently being replicated to the Apache mirrors before being announce tomorrow. In the meantime, you can download it here: http://people.apache.org/~pamarcelot/ApacheDirectoryStudio-2.0.0.v20130628/ Could you try and tell us if it fixes your issue (it probably will)? Thanks! > Import Apache DS 2.0 configuration fails > > > Key: DIRSTUDIO-932 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-932 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Ubuntu 13.04 >Reporter: Łukasz Adamczyk > > Import of Apache DS 2.0 configuration fails even when you import just > exported, default ldif with configuration. > http://imageshack.us/photo/my-images/594/kpej.png/ -- 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] [Comment Edited] (DIRSTUDIO-932) Import Apache DS 2.0 configuration fails
[ https://issues.apache.org/jira/browse/DIRSTUDIO-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697830#comment-13697830 ] Pierre-Arnaud Marcelot edited comment on DIRSTUDIO-932 at 7/2/13 2:32 PM: -- What the version of the ApacheDS? If it's 2.0.0-M13 or 2.0.0-M14, note that Apache Directory Studio 2.0.0-M7 (2.0.0.v20130517) is *NOT* compatible with them, since they include a new attribute type for the configuration. Version 2.0.0-M8 has been voted to fix this issue (and more) and is currently being replicated to the Apache mirrors before being announce tomorrow. In the meantime, you can download it here: http://people.apache.org/~pamarcelot/ApacheDirectoryStudio-2.0.0.v20130628/ Could you try and tell us if it fixes your issue (it probably will)? Thanks! was (Author: pamarcelot): What the version of the ApacheDS? If it's 2.0.0-M13 or 2.0.0-M14, note that Apache Directory Studio 2.0.0-M7 (2.0.0.v20130517) is compatible with them, since they include a new attribute type for the configuration. Version 2.0.0-M8 has been voted to fix this issue (and more) and is currently being replicated to the Apache mirrors before being announce tomorrow. In the meantime, you can download it here: http://people.apache.org/~pamarcelot/ApacheDirectoryStudio-2.0.0.v20130628/ Could you try and tell us if it fixes your issue (it probably will)? Thanks! > Import Apache DS 2.0 configuration fails > > > Key: DIRSTUDIO-932 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-932 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Ubuntu 13.04 >Reporter: Łukasz Adamczyk > > Import of Apache DS 2.0 configuration fails even when you import just > exported, default ldif with configuration. > http://imageshack.us/photo/my-images/594/kpej.png/ -- 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-931) ERR_04269 ATTRIBUTE_TYPE for OID ads-pwdvalidator does not exist!
[ https://issues.apache.org/jira/browse/DIRSTUDIO-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-931. -- Resolution: Fixed Fix Version/s: 2.0.0-M8 Assignee: Pierre-Arnaud Marcelot This new attribute was added in the latest version of ApacheDS. Apache Directory Studio 2.0.0-M8 s currently being voted and supports the latest version of ApacheDS. It should be out in two days or so. In the meantime, you can grab it here: http://people.apache.org/~pamarcelot/ApacheDirectoryStudio-2.0.0.v20130628/ > ERR_04269 ATTRIBUTE_TYPE for OID ads-pwdvalidator does not exist! > - > > Key: DIRSTUDIO-931 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-931 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) >Reporter: Marc Ende >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M8 > > > Due to the following error I couldn't load the server configuration. > (I've tried to try it with the current SNAPSHOT but the latest is not > starting.) > Die Konfiguration konnte nicht geladen werden. > - ERR_04269 ATTRIBUTE_TYPE for OID ads-pwdvalidator does not exist! > org.apache.directory.api.ldap.model.exception.LdapNoSuchAttributeException: > ERR_04269 ATTRIBUTE_TYPE for OID ads-pwdvalidator does not exist! > at > org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:317) > at > org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:47) > at > org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.lookupAttributeTypeRegistry(DefaultSchemaManager.java:1623) > at > org.apache.directory.api.ldap.model.entry.DefaultEntry.(DefaultEntry.java:311) > at > org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.readConfiguration(LoadConfigurationRunnable.java:359) > at > org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.getConfiguration(LoadConfigurationRunnable.java:182) > at > org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.run(LoadConfigurationRunnable.java:127) > at > org.apache.directory.studio.common.core.jobs.StudioJob.run(StudioJob.java:83) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: org.apache.directory.api.ldap.model.exception.LdapException: > ERR_04269 ATTRIBUTE_TYPE for OID ads-pwdvalidator does not exist! > at > org.apache.directory.api.ldap.model.schema.registries.DefaultSchemaObjectRegistry.lookup(DefaultSchemaObjectRegistry.java:176) > at > org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:313) > ... 8 more > ERR_04269 ATTRIBUTE_TYPE for OID ads-pwdvalidator does not exist! -- 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-930) ERR_04269 ads_pwdvalidator does not exist
[ https://issues.apache.org/jira/browse/DIRSTUDIO-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696628#comment-13696628 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-930: -- BTW, you can find distributions for version 2.0.0-M8 of Apache Directory Studio, currently being voted, at this address: http://people.apache.org/~pamarcelot/ApacheDirectoryStudio-2.0.0.v20130628/ > ERR_04269 ads_pwdvalidator does not exist > - > > Key: DIRSTUDIO-930 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-930 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: apacheds 2.0.0 M13 >Reporter: Daniel Cheung >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M8, 2.0.0 > > > After fresh install of apacheds 2.0.0 M13 and trying to configure it per the > readme, I'm getting ERR_04269 ATTRIBUTE_TYPE for OID ads_pwdvalidator does > not exist! error. I also tried the nightly build of Directory Studio, but it > won't get pass Loading Workspace. > It's very similar to DIRSTUDIO-916 and DIRSTUDIO-907. -- 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-930) ERR_04269 ads_pwdvalidator does not exist
[ https://issues.apache.org/jira/browse/DIRSTUDIO-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-930. -- Resolution: Fixed Fix Version/s: 2.0.0 2.0.0-M8 Assignee: Pierre-Arnaud Marcelot > ERR_04269 ads_pwdvalidator does not exist > - > > Key: DIRSTUDIO-930 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-930 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: apacheds 2.0.0 M13 >Reporter: Daniel Cheung >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M8, 2.0.0 > > > After fresh install of apacheds 2.0.0 M13 and trying to configure it per the > readme, I'm getting ERR_04269 ATTRIBUTE_TYPE for OID ads_pwdvalidator does > not exist! error. I also tried the nightly build of Directory Studio, but it > won't get pass Loading Workspace. > It's very similar to DIRSTUDIO-916 and DIRSTUDIO-907. -- 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-930) ERR_04269 ads_pwdvalidator does not exist
[ https://issues.apache.org/jira/browse/DIRSTUDIO-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696622#comment-13696622 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-930: -- Indeed this is the same kind of error than these two other issues, this new attribute was added in the latest version of ApacheDS. Apache Directory Studio is currently being voted and supports the latest version of ApacheDS. It should be out in two days or so. The current nightly builds are also broken because of pending Apache Directory LDAP API and ApacheDS releases. > ERR_04269 ads_pwdvalidator does not exist > - > > Key: DIRSTUDIO-930 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-930 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: apacheds 2.0.0 M13 >Reporter: Daniel Cheung > > After fresh install of apacheds 2.0.0 M13 and trying to configure it per the > readme, I'm getting ERR_04269 ATTRIBUTE_TYPE for OID ads_pwdvalidator does > not exist! error. I also tried the nightly build of Directory Studio, but it > won't get pass Loading Workspace. > It's very similar to DIRSTUDIO-916 and DIRSTUDIO-907. -- 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-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:comment-tabpanel&focusedCommentId=13693893#comment-13693893 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-903: -- Hi Guillermo, Thanks for testing and confirming it's fixed. :) The "OK" button is disabled: - when the "Current Password" pane is selected - when the "New Password" pane is selected AND the "Enter New Password:" field is empty, which is the case when the dialog is first opened. So unless the user voluntarily types a new password, there's no way a user can close the dialog using the "OK" button, only the "Cancel" or 'close window' button are enabled. > 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 >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-M7 (2.0.0.v20130517), 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] [Commented] (DIRSERVER-1860) Invalid DN in returned entry
[ https://issues.apache.org/jira/browse/DIRSERVER-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693073#comment-13693073 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1860: --- Unfortunately, this test 'CollectiveAttributeServiceIT.testSearch' randomly fails without us knowing exactly now (for now). You might want to run the tests again (with resume: mvn clean install -rf :apacheds-core-integ). Or you can disable tests by appending "-DskipTests" to the command line. Hope this helps. > Invalid DN in returned entry > > > Key: DIRSERVER-1860 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1860 > Project: Directory ApacheDS > Issue Type: Bug > Components: ldap > Environment: Windows Server 2008 R2 Standard >Reporter: Charlie Barnett >Priority: Minor > Fix For: 2.0.0-M11 > > > I am trying to match entries in two directories and produce an xml file of > differences. ApacheDS is the server for both directories. JXplorer is being > used to modify one of the directories. The modified directory is read using a > SearchResultListener. In one case the dn of the SearchResultEntry passed to > the listener is incorrect. It only contains the rdn of the entry. The > specific case is when a new uniqueMember is added to an existing entry of > type groupOfUniqueNames. This occurs with both JXplorer and also with Apache > Directory Studio. After starting and stopping the server the correct dn is > contained in the entry passed. Waiting aproximately 15 minutes also clears > the problem. Am using unboundid ldap client library > Reported problem initially to unboundid but determined by running a proxy > that the invalid dn was being returned from server. Link to unboundui report > is http://sourceforge.net/p/ldap-sdk/discussion/1001257/thread/ffbae6dd/ > -- 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-1860) Invalid DN in returned entry
[ https://issues.apache.org/jira/browse/DIRSERVER-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692845#comment-13692845 ] Pierre-Arnaud Marcelot commented on DIRSERVER-1860: --- Hi Charlie, What kind of build issues did you have? The proper place for build documentation is here: http://directory.apache.org/apacheds/advanced-ug/0.2-building-trunks.html > Invalid DN in returned entry > > > Key: DIRSERVER-1860 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1860 > Project: Directory ApacheDS > Issue Type: Bug > Components: ldap > Environment: Windows Server 2008 R2 Standard >Reporter: Charlie Barnett >Priority: Minor > Fix For: 2.0.0-M11 > > > I am trying to match entries in two directories and produce an xml file of > differences. ApacheDS is the server for both directories. JXplorer is being > used to modify one of the directories. The modified directory is read using a > SearchResultListener. In one case the dn of the SearchResultEntry passed to > the listener is incorrect. It only contains the rdn of the entry. The > specific case is when a new uniqueMember is added to an existing entry of > type groupOfUniqueNames. This occurs with both JXplorer and also with Apache > Directory Studio. After starting and stopping the server the correct dn is > contained in the entry passed. Waiting aproximately 15 minutes also clears > the problem. Am using unboundid ldap client library > Reported problem initially to unboundid but determined by running a proxy > that the invalid dn was being returned from server. Link to unboundui report > is http://sourceforge.net/p/ldap-sdk/discussion/1001257/thread/ffbae6dd/ > -- 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-929) Improve Hex Value Editor to allow text edition
[ https://issues.apache.org/jira/browse/DIRSTUDIO-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-929. -- Resolution: Fixed Fix at revision 1496058. http://svn.apache.org/r1496058 > Improve Hex Value Editor to allow text edition > -- > > Key: DIRSTUDIO-929 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-929 > Project: Directory Studio > Issue Type: Improvement > Components: studio-ldapbrowser >Reporter: Pierre-Arnaud Marcelot >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M8, 2.0.0 > > > Following DIRSTUDIO-915 (Attribute values of Binary syntax > (1.3.6.1.4.1.1466.115.121.1.5) are displayed inconsistently), it would be > helpful to have an "Edit as Text…" button in the Hex Value Editor to be able > to edit the value (if it is text displayable, typically the case of a string > value stored in a binary attribute). -- 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-929) Improve Hex Value Editor to allow text edition
[ https://issues.apache.org/jira/browse/DIRSTUDIO-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-929: - Summary: Improve Hex Value Editor to allow text edition (was: Improve Hex Value Editor to allow text edition.) > Improve Hex Value Editor to allow text edition > -- > > Key: DIRSTUDIO-929 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-929 > Project: Directory Studio > Issue Type: Improvement > Components: studio-ldapbrowser >Reporter: Pierre-Arnaud Marcelot >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M8, 2.0.0 > > > Following DIRSTUDIO-915 (Attribute values of Binary syntax > (1.3.6.1.4.1.1466.115.121.1.5) are displayed inconsistently), it would be > helpful to have an "Edit as Text…" button in the Hex Value Editor to be able > to edit the value (if it is text displayable, typically the case of a string > value stored in a binary attribute). -- 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-915) Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are displayed inconsistently
[ https://issues.apache.org/jira/browse/DIRSTUDIO-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-915. -- Resolution: Not A Problem Assignee: Pierre-Arnaud Marcelot DIRSTUDIO-929 (Improve Hex Value Editor to allow text edition) has been opened for the improvement on the Hex Value Editor. > Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are > displayed inconsistently > - > > Key: DIRSTUDIO-915 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-915 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M6 (2.0.0.v20130308) > Environment: Apache DS 2.0.0M6 on Win7-64 against Edirectory 8.8.7 >Reporter: Lothar Haeger >Assignee: Pierre-Arnaud Marcelot > Attachments: screenshot-1.jpg > > > Attribute values of binary syntax OID 1.3.6.1.4.1.1466.115.121.1.5 are > displayed inconsistently and partly wrong. Those attributes contain base 64 > encoded text and some of them are displayed as > - editable (inline + dialog) text > - "Binary Data (xxx Bytes)" > - NULL > See attached screenshot for an example of Apache DS vs. Gawor LDAP > Browser/Editor displayoing the same 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] (DIRSTUDIO-929) Improve Hex Value Editor to allow text edition.
Pierre-Arnaud Marcelot created DIRSTUDIO-929: Summary: Improve Hex Value Editor to allow text edition. Key: DIRSTUDIO-929 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-929 Project: Directory Studio Issue Type: Improvement Components: studio-ldapbrowser Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M8, 2.0.0 Following DIRSTUDIO-915 (Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are displayed inconsistently), it would be helpful to have an "Edit as Text…" button in the Hex Value Editor to be able to edit the value (if it is text displayable, typically the case of a string value stored in a binary attribute). -- 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-915) Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are displayed inconsistently
[ https://issues.apache.org/jira/browse/DIRSTUDIO-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691930#comment-13691930 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-915: -- After a TeamViewer session with Lothar last week, we saw that some "wrong" settings in the Value Editors preferences page were primarily the cause of this issue. On the subject of eDirectory storing String values into attributes with a Binary Syntax, we concurred that it would be great to have a new option in the Hex Value Editor to allow text edition (if possible, if the value is displayable). This is going to be tracked in a dedicated JIRA issue. > Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are > displayed inconsistently > - > > Key: DIRSTUDIO-915 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-915 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M6 (2.0.0.v20130308) > Environment: Apache DS 2.0.0M6 on Win7-64 against Edirectory 8.8.7 >Reporter: Lothar Haeger > Attachments: screenshot-1.jpg > > > Attribute values of binary syntax OID 1.3.6.1.4.1.1466.115.121.1.5 are > displayed inconsistently and partly wrong. Those attributes contain base 64 > encoded text and some of them are displayed as > - editable (inline + dialog) text > - "Binary Data (xxx Bytes)" > - NULL > See attached screenshot for an example of Apache DS vs. Gawor LDAP > Browser/Editor displayoing the same 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] (DIRSTUDIO-915) Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are displayed inconsistently
[ https://issues.apache.org/jira/browse/DIRSTUDIO-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-915: - Summary: Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are displayed inconsistently (was: Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (Binary) are displayed inconsistently) > Attribute values of Binary syntax (1.3.6.1.4.1.1466.115.121.1.5) are > displayed inconsistently > - > > Key: DIRSTUDIO-915 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-915 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M6 (2.0.0.v20130308) > Environment: Apache DS 2.0.0M6 on Win7-64 against Edirectory 8.8.7 >Reporter: Lothar Haeger > Attachments: screenshot-1.jpg > > > Attribute values of binary syntax OID 1.3.6.1.4.1.1466.115.121.1.5 are > displayed inconsistently and partly wrong. Those attributes contain base 64 > encoded text and some of them are displayed as > - editable (inline + dialog) text > - "Binary Data (xxx Bytes)" > - NULL > See attached screenshot for an example of Apache DS vs. Gawor LDAP > Browser/Editor displayoing the same 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] (DIRSTUDIO-915) Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (binary) are displayed inconsistently
[ https://issues.apache.org/jira/browse/DIRSTUDIO-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-915: - Summary: Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (binary) are displayed inconsistently (was: Attribute values of syntac 1.3.6.1.4.1.1466.115.121.1.5 (binary) are displayed inconsistently) > Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (binary) are > displayed inconsistently > - > > Key: DIRSTUDIO-915 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-915 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M6 (2.0.0.v20130308) > Environment: Apache DS 2.0.0M6 on Win7-64 against Edirectory 8.8.7 >Reporter: Lothar Haeger > Attachments: screenshot-1.jpg > > > Attribute values of binary syntax OID 1.3.6.1.4.1.1466.115.121.1.5 are > displayed inconsistently and partly wrong. Those attributes contain base 64 > encoded text and some of them are displayed as > - editable (inline + dialog) text > - "Binary Data (xxx Bytes)" > - NULL > See attached screenshot for an example of Apache DS vs. Gawor LDAP > Browser/Editor displayoing the same 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] (DIRSTUDIO-915) Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (Binary) are displayed inconsistently
[ https://issues.apache.org/jira/browse/DIRSTUDIO-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-915: - Summary: Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (Binary) are displayed inconsistently (was: Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (binary) are displayed inconsistently) > Attribute values of syntax 1.3.6.1.4.1.1466.115.121.1.5 (Binary) are > displayed inconsistently > - > > Key: DIRSTUDIO-915 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-915 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M6 (2.0.0.v20130308) > Environment: Apache DS 2.0.0M6 on Win7-64 against Edirectory 8.8.7 >Reporter: Lothar Haeger > Attachments: screenshot-1.jpg > > > Attribute values of binary syntax OID 1.3.6.1.4.1.1466.115.121.1.5 are > displayed inconsistently and partly wrong. Those attributes contain base 64 > encoded text and some of them are displayed as > - editable (inline + dialog) text > - "Binary Data (xxx Bytes)" > - NULL > See attached screenshot for an example of Apache DS vs. Gawor LDAP > Browser/Editor displayoing the same 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] [Resolved] (DIRSTUDIO-927) The "options... Advanced Options Configuration" link on the "Overview" age does not work
[ https://issues.apache.org/jira/browse/DIRSTUDIO-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-927. -- Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Pierre-Arnaud Marcelot Fix at revision 1494652. http://svn.apache.org/r1494652 I removed the link which has always linked to a non-existing page in the editor. > The "options... Advanced Options Configuration" link on the "Overview" age > does not work > > > Key: DIRSTUDIO-927 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-927 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) >Reporter: Emmanuel Lecharny >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M8, 2.0.0 > > > When you open a server configuration, and try to click on the "Advanced > Options Configuration", nothing happens -- 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-862) Unhandled event loop exception in Studio for eclipse
[ https://issues.apache.org/jira/browse/DIRSTUDIO-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687937#comment-13687937 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-862: -- Hi, I'm not able to reproduce the issue with the current version (2.0.0-M7 - 2.0.0.v20130517). Is this still occurring for you? Thanks! Regards, Pierre-Arnaud > Unhandled event loop exception in Studio for eclipse > > > Key: DIRSTUDIO-862 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-862 > Project: Directory Studio > Issue Type: Bug > Environment: Eclipse Java EE IDE for Web Developers. > Version: Indigo Service Release 2 > Build id: 20120216-1857 > OS X >Reporter: Nabil Sayegh > > 1. Follow an administrativeRole attribute > 2. Follow prescriptiveACI > 3. BOOM! (Unhandled event loop exception) -- 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-926) 1.2.840.113556.1.4.319 (Simple Paged Results) Control page size limit
[ https://issues.apache.org/jira/browse/DIRSTUDIO-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686894#comment-13686894 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-926: -- I have to say, I wonder too. If you find it, would you please mind indicating it here, in case someone faces the same issue later ? Thanks! > 1.2.840.113556.1.4.319 (Simple Paged Results) Control page size limit > - > > Key: DIRSTUDIO-926 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-926 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Windows and Microsoft Active Directory > domainControllerFunctionality: 4 > domainFunctionality: 4 >Reporter: Jim Willeke >Priority: Minor > Labels: patch > > Setting the page size to anything less than 101 seems to work. > Any value >=101 fails to return any results beyond 101 when in "Scroll Mode" > Returns all expected results when NOT in "Scroll Mode" > Not sure if this is a feature or a bug. -- 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-926) 1.2.840.113556.1.4.319 (Simple Paged Results) Control page size limit
[ https://issues.apache.org/jira/browse/DIRSTUDIO-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686795#comment-13686795 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-926: -- Hi Jim, I checked both issues. Issue #1: Any value >=101 fails to return any results beyond 101 when in "Scroll Mode" - I tested it against ApacheDS which also supports the Simple Paged Results control and it works as expected. I was able to scroll an entire "OU" 500 entries at a time. So, it might be a limit on Active Directory or the user you're using to browse entries. I'm not sure. Issue #2: Returns all expected results when NOT in "Scroll Mode" - I was able to confirm this behavior and that it's a feature. Taken from the tooltip of the "Scroll Mode" checkbox: "If enabled only one page is fetched from the server at once while browsing, you could 'scroll' through the pages by using the 'next page' and 'top page' items. If disabled _all_ entries are fetched from the server, the paged result control is only used in background to avoid server-side limits." > 1.2.840.113556.1.4.319 (Simple Paged Results) Control page size limit > - > > Key: DIRSTUDIO-926 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-926 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M7 (2.0.0.v20130517) > Environment: Windows and Microsoft Active Directory > domainControllerFunctionality: 4 > domainFunctionality: 4 >Reporter: Jim Willeke >Priority: Minor > Labels: patch > > Setting the page size to anything less than 101 seems to work. > Any value >=101 fails to return any results beyond 101 when in "Scroll Mode" > Returns all expected results when NOT in "Scroll Mode" > Not sure if this is a feature or a bug. -- 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-848) Unable to open LDAP configuration editor when special chars are in ads-certificatePassword attribute
[ https://issues.apache.org/jira/browse/DIRSTUDIO-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot resolved DIRSTUDIO-848. -- Resolution: Fixed Assignee: Pierre-Arnaud Marcelot This was an problem on ApacheDS (the server), which has been fixed now. > Unable to open LDAP configuration editor when special chars are in > ads-certificatePassword attribute > > > Key: DIRSTUDIO-848 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-848 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds-configuration >Affects Versions: 2.0.0-M3 (2.0.0.v20120224) >Reporter: Richard Lowden >Assignee: Pierre-Arnaud Marcelot >Priority: Minor > > Exception thrown when trying to "open configuration" from connections view > when LDAP server is configured for LDAPS and there is a '$' character in the > ads-certificatePassword attribute. > The exception seems to indicate that the ads-certificatePassword attribute > should be a PrintableString, however looking at it's definition through the > schema it is a DirectoryString. > Error stack trace is (actual password has been changed slightly for security): > org.apache.directory.shared.ldap.model.exception.LdapInvalidAttributeValueException: > ERR_04447_CANNOT_NORMALIZE_VALUE Cannot normalize the wrapped value > ERR_04473_NOT_VALID_VALUE Not a valid value 'my$password' for the > AttributeType 'ATTRIBUTE_TYPE ( 1.3.6.1.4.1.18060.0.4.1.2.309 > NAME 'ads-certificatePassword' > DESC The certificate passord > EQUALITY caseExactMatch > ORDERING caseExactOrderingMatch > SUBSTR caseExactSubstringsMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 > SINGLE-VALUE > USAGE userApplications > ) > ' > at > org.apache.directory.shared.ldap.model.entry.AbstractValue.apply(AbstractValue.java:209) > at > org.apache.directory.shared.ldap.model.entry.StringValue.(StringValue.java:102) > at > org.apache.directory.shared.ldap.model.entry.DefaultAttribute.(DefaultAttribute.java:468) > at > org.apache.directory.shared.ldap.model.entry.DefaultEntry.(DefaultEntry.java:314) > at > org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.readConfiguration(LoadConfigurationRunnable.java:358) > at > org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.getConfiguration(LoadConfigurationRunnable.java:182) > at > org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.run(LoadConfigurationRunnable.java:127) > at > org.apache.directory.studio.common.core.jobs.StudioJob.run(StudioJob.java:83) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: > org.apache.directory.shared.ldap.model.exception.LdapInvalidAttributeValueException: > ERR_04473_NOT_VALID_VALUE Not a valid value 'my$password' for the > AttributeType 'ATTRIBUTE_TYPE ( 1.3.6.1.4.1.18060.0.4.1.2.309 > NAME 'ads-certificatePassword' > DESC The certificate passord > EQUALITY caseExactMatch > ORDERING caseExactOrderingMatch > SUBSTR caseExactSubstringsMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 > SINGLE-VALUE > USAGE userApplications > ) > ' > at > org.apache.directory.shared.ldap.model.entry.AbstractValue.apply(AbstractValue.java:201) > ... 8 more -- 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-883) No search selected
[ https://issues.apache.org/jira/browse/DIRSTUDIO-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685659#comment-13685659 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-883: -- I've checked this issue with the current trunk version and it seems to work as expected. The entry editor is shown when I go back to connection one. Could you please verify on your side? Thanks! > No search selected > -- > > Key: DIRSTUDIO-883 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-883 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M5 (2.0.0.v20130131) > Environment: Windows 8, Java 7u15 >Reporter: Aleks M > > I have multiple connections that I switch between and I have at least one > search opened in each connection. > Sometimes when switching between connections Studio switches to a tab named > No search selected. > If you then click on a search it will be displayed in that tab. > If you click on a search result in the LDAP Browser view (the tree view) > Studio won't switch to the entry editor tab. Instead it will just display "No > search selected" in the current tab. > You can also replicate this issue by having two connections, in connection > one select an object in the LDAP browser view so that the entry editor is > displayed. > Swith to connection two and perform a search. Switch back to connection one, > instead of showing you the entry editor where you were it displays the No > search selected tab. -- 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-911) Object classes not visible within Schema View of OS X
[ https://issues.apache.org/jira/browse/DIRSTUDIO-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-911: - Component/s: studio-schemaeditor > Object classes not visible within Schema View of OS X > - > > Key: DIRSTUDIO-911 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-911 > Project: Directory Studio > Issue Type: Bug > Components: studio-schemaeditor >Affects Versions: 2.0.0-M6 (2.0.0.v20130308) > Environment: Mac OS X 10.8.3 (Java 7) >Reporter: Konrad Windszus >Assignee: Pierre-Arnaud Marcelot > Fix For: 2.0.0-M8, 2.0.0 > > > Object classes are not visible within the Schema view. To reproduce > - Create a new schema project (offline) > - Create a new schema > - Create a new ObjectClass > Although there is no error message, the newly created object class is not > shown in the schema view. -- 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
