You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2011/05/25 18:19:47 UTC
[jira] [Created] (DIRSHARED-126) Make the connection schema aware,
so that the returned entry are schema aware
Make the connection schema aware, so that the returned entry are schema aware
-----------------------------------------------------------------------------
Key: DIRSHARED-126
URL: https://issues.apache.org/jira/browse/DIRSHARED-126
Project: Directory Shared
Issue Type: New Feature
Affects Versions: 1.0.0-M3
Reporter: Emmanuel Lecharny
Priority: Blocker
Fix For: 1.0.0-M5
When we fetch entries (lookup or search), we get back non-schema aware results.
We should have those entries schema aware by default, unless the remote server cannot provide a schema.
We also have to provide a way to inject a schema to a connection, in case we can't get back a schema frm the remote server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSHARED-126) Make the connection schema aware,
so that the returned entry are schema aware
Posted by "Emmanuel Lecharny (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSHARED-126.
-----------------------------------------
Resolution: Fixed
It's enough to load the schema this way :
connection.loadDefaultSchema()
The connection is now schema aware.
> Make the connection schema aware, so that the returned entry are schema aware
> -----------------------------------------------------------------------------
>
> Key: DIRSHARED-126
> URL: https://issues.apache.org/jira/browse/DIRSHARED-126
> Project: Directory Shared
> Issue Type: New Feature
> Affects Versions: 1.0.0-M3
> Reporter: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 1.0.0-M10
>
>
> When we fetch entries (lookup or search), we get back non-schema aware results.
> We should have those entries schema aware by default, unless the remote server cannot provide a schema.
> We also have to provide a way to inject a schema to a connection, in case we can't get back a schema frm the remote server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira