[
https://issues.apache.org/jira/browse/DIRSTUDIO-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474192#comment-13474192
]
Aaron J Angel commented on DIRSTUDIO-834:
-----------------------------------------
I believe that is the version I installed. I cannot tell for certain as the
Help/About screen lists a different version: 2.0.0.v20120224. I installed and
tested the snapshot and can confirm that both are now working. Thanks so much
for fixing this! It has made my day.
> Unable to edit subtreeSpecification
> -----------------------------------
>
> Key: DIRSTUDIO-834
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-834
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-acieditor
> Environment: Fresh installation of Apache Studio 2.x via the Eclipse
> update site, connected to a new instance of ApacheDS 2.0.0 created within
> Eclipse. Added a new partition whose context entry has administrativeRole
> accessControlSpecificArea.
> Reporter: Aaron J Angel
> Assignee: Pierre-Arnaud Marcelot
> Fix For: 2.0.0-M4, 2.0.0
>
>
> Creating a new accessControlSubentry fails due to inability to edit the value
> of the subtreeSpecification attribute. Steps to reproduce:
> Right-click on an object in the DIT, choosing New, New Entry.
> Create entry from scratch and click next.
> Add accessControlSubentry and subentry classes and click next.
> Name the object.
> At this point, behavior is inconsistent. Sometimes, an error message
> displays:
> An error has occurred. See error log for more details.
> java.lang.NullPointerException
> Other times, the value editor for prescriptiveACI attribute is launched. In
> either case, attempting to edit the value for the subtreeSpecification
> attribute is unsuccessful. Double clicking on the attribute or its value
> does nothing. Right-clicking and choosing a value editor (any, actually,
> included in-place and text editor) also do nothing.
--
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
