Bug 124356 (DEFECT000295402) - read the extended definition of a class as well as the rules defined on the class
Summary: read the extended definition of a class as well as the rules defined on the c...
Status: NEW
Alias: DEFECT000295402
Product: NDS SDK
Classification: Novell Products
Component: LDAP Java SDK (show other bugs)
Version: Future
Hardware: Other Other
: P5 - None : Minor
Target Milestone: ---
Assignee: Palaniappan N
QA Contact: Anilkumar S
URL:
Whiteboard:
Keywords: English
Depends on:
Blocks:
 
Reported: 2002-03-14 18:17 UTC by Alan Clark
Modified: 2008-05-10 07:01 UTC (History)
1 user (show)

See Also:
Found By: Integration Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rajkumar V 2005-10-10 22:54:39 UTC 


------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 -------

This bug previously known as bug DEFECT000295402 at remedy/
remedy/show_bug.cgi?id=DEFECT000295402
Originally filed under the NDS SDK product and LDAP Java SDK component.

---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> 
The eDirectory NCP library allows reading the extended (or expanded) definition
of a class as well as the rules explicitly defined on the class.  Each of
these is a single call to eDirectory.  It would be convenient if JLDAP had
similar functionality.  In the NCP library, the same function call is used,
along with a flag denoting explicit rules or extended rules.
 </remedy_details>
---------
<remedy_notes> vtag (  7/31/2002 1:59:29 PM  Fixing - New )
Translation: Reading the schema of a class gives attribute definitions
for only the class, and not of its superiors.  What is wanted here is
a way to get all of the attribute definitions.

One possibility is to write a sample that demonstrates this.
Another possibility is to set a property in LDAPConstraints to enable
this behavior  - probably very difficult.

We consider this to be an enhancement request.


 </remedy_notes>