You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2010/07/12 14:11:49 UTC
[jira] Created: (DIRSTUDIO-676)
SchemaUtils.getSpecificStructuralObjectClass() issues
SchemaUtils.getSpecificStructuralObjectClass() issues
-----------------------------------------------------
Key: DIRSTUDIO-676
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-676
Project: Directory Studio
Issue Type: Bug
Components: studio-persistence-tooling
Reporter: Stefan Seelmann
- Method name should just be getStructuralObjectClass(), the term "structural object class" is well defined in RFC 4512, "specific" isn't
- Javadoc is missing
- The method throws an IndexOutOfBoundsException if the passed list is empty or doesn't contain an object class description with kind "structural". Better throw an IllegalArgumentException in that case and note that in the javadoc
- The method throws an NullPointerException if the passed list is null, Better throw an IllegalArgumentException in that case
- If multiple object classes descriptions with kind "structural" are passed and they are not part of the same superclass chain then the first one is picked. Better throw an IllegalArgumentException in that case because that is an illegal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSTUDIO-676)
SchemaUtils.getSpecificStructuralObjectClass() issues
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887355#action_12887355 ]
Stefan Seelmann commented on DIRSTUDIO-676:
-------------------------------------------
Added test, marked with @Ignore("DIRSTUDIO-676"): http://code.google.com/p/dirstudio-ldap-tooling/source/detail?r=57
> SchemaUtils.getSpecificStructuralObjectClass() issues
> -----------------------------------------------------
>
> Key: DIRSTUDIO-676
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-676
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-persistence-tooling
> Reporter: Stefan Seelmann
>
> - Method name should just be getStructuralObjectClass(), the term "structural object class" is well defined in RFC 4512, "specific" isn't
> - Javadoc is missing
> - The method throws an IndexOutOfBoundsException if the passed list is empty or doesn't contain an object class description with kind "structural". Better throw an IllegalArgumentException in that case and note that in the javadoc
> - The method throws an NullPointerException if the passed list is null, Better throw an IllegalArgumentException in that case
> - If multiple object classes descriptions with kind "structural" are passed and they are not part of the same superclass chain then the first one is picked. Better throw an IllegalArgumentException in that case because that is an illegal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSTUDIO-676)
SchemaUtils.getSpecificStructuralObjectClass() issues
Posted by "Kasun Lakpriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kasun Lakpriya resolved DIRSTUDIO-676.
--------------------------------------
Resolution: Fixed
Issue is resolved.
http://code.google.com/p/dirstudio-ldap-tooling/source/detail?r=63
> SchemaUtils.getSpecificStructuralObjectClass() issues
> -----------------------------------------------------
>
> Key: DIRSTUDIO-676
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-676
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-persistence-tooling
> Reporter: Stefan Seelmann
> Assignee: Kasun Lakpriya
>
> - Method name should just be getStructuralObjectClass(), the term "structural object class" is well defined in RFC 4512, "specific" isn't
> - Javadoc is missing
> - The method throws an IndexOutOfBoundsException if the passed list is empty or doesn't contain an object class description with kind "structural". Better throw an IllegalArgumentException in that case and note that in the javadoc
> - The method throws an NullPointerException if the passed list is null, Better throw an IllegalArgumentException in that case
> - If multiple object classes descriptions with kind "structural" are passed and they are not part of the same superclass chain then the first one is picked. Better throw an IllegalArgumentException in that case because that is an illegal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSTUDIO-676)
SchemaUtils.getSpecificStructuralObjectClass() issues
Posted by "Kasun Lakpriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kasun Lakpriya reassigned DIRSTUDIO-676:
----------------------------------------
Assignee: Kasun Lakpriya
> SchemaUtils.getSpecificStructuralObjectClass() issues
> -----------------------------------------------------
>
> Key: DIRSTUDIO-676
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-676
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-persistence-tooling
> Reporter: Stefan Seelmann
> Assignee: Kasun Lakpriya
>
> - Method name should just be getStructuralObjectClass(), the term "structural object class" is well defined in RFC 4512, "specific" isn't
> - Javadoc is missing
> - The method throws an IndexOutOfBoundsException if the passed list is empty or doesn't contain an object class description with kind "structural". Better throw an IllegalArgumentException in that case and note that in the javadoc
> - The method throws an NullPointerException if the passed list is null, Better throw an IllegalArgumentException in that case
> - If multiple object classes descriptions with kind "structural" are passed and they are not part of the same superclass chain then the first one is picked. Better throw an IllegalArgumentException in that case because that is an illegal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.