Bug 124399 (DEFECT000322507)

Summary:	Request for schema helper methods
Product:	[Novell Products] NDS SDK	Reporter:	Steve Sonntag <vtag>
Component:	LDAP Java SDK	Assignee:	Jeff Vincent <jvincent>
Status:	VERIFIED FIXED	QA Contact:	Sundar Swamy <ssundar>
Severity:	Minor
Priority:	P5 - None	CC:	aclark
Version:	OCT 2006 NDK	Keywords:	English
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Rajkumar V 2005-10-10 22:54:53 UTC



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

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

---------
<remedy_version_found_in> BLANK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> From: Jim Willeke <jim@willeke.com>

When working with an attribute or an objectclass it would be nice to be
able to easily determine the schema of the attribute or objectclass.

One I was working on lately was wanting to print the attributes of a
user. Since some of these are non-printable, it became necessary to
query the RootDSE, then the subSchemaEntry to determine the syntax of
the attributte.

Some helper methods that allow retrieveing the Schema when using an
instance of attribute or objectclass would save a lot of lines of code.

like LDAPAttributte.schema.syntax should be easy to implement.

Another one on Objectclasses. You want to add a new entry and would like
a list of "possible" attributes. LDAPEntry.schema.attributes as an
enumeration would be helpful.

Or am I missing something that already exist?
-jim
 </remedy_details>