You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kiran Ayyagari (JIRA)" <ji...@apache.org> on 2010/08/23 12:57:17 UTC
[jira] Commented: (DIRAPI-21) Adding a value into an EntryAttribute
does not leverage the schemaManager
[ https://issues.apache.org/jira/browse/DIRAPI-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901348#action_12901348 ]
Kiran Ayyagari commented on DIRAPI-21:
--------------------------------------
IMO it is better to let the user make use of schema manager rather than changing api to make the entries/attributes schema aware.
cause..
1. Users can directly get access to schema manager from LdapConnection
2. It is always slow to convert a given entry to a schema aware entry (this requires creating a new entry by copying all attributes)
3. Entry interface doesn't provide any method to check if the entry already is schema aware so there is no way to avoid step 2 even if the
user creates a schema aware entry
The only place where LdapConnection uses schema manager internally is while returning search results.
> Adding a value into an EntryAttribute does not leverage the schemaManager
> -------------------------------------------------------------------------
>
> Key: DIRAPI-21
> URL: https://issues.apache.org/jira/browse/DIRAPI-21
> Project: Directory client API
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 0.2.0
>
>
> We don't normalize nor check that the added value is valid in the EntryAttribute. As soon as we have a reference to the SchemaManager, every added value should be checkd and normalized.
> The contains( XXX ) method does not leverage the schemaManager either.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.