You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2008/07/23 16:59:31 UTC

[jira] Assigned: (DIRSERVER-1205) Remove Referral interceptor from core

     [ https://issues.apache.org/jira/browse/DIRSERVER-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu reassigned DIRSERVER-1205:
----------------------------------------

    Assignee: Alex Karasulu

> Remove Referral interceptor from core
> -------------------------------------
>
>                 Key: DIRSERVER-1205
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1205
>             Project: Directory ApacheDS
>          Issue Type: Task
>          Components: core, core-integ
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>            Priority: Critical
>             Fix For: 1.5.4
>
>
> The referral interceptor is responsible for raising exceptions based on a referral handling parameters associated with a session or an individual request.  This is a remnant from the days when the core and the JNDI provider code were tightly coupled.  It no longer needs to be the case and the server's core can handle both referrals and entries in the same way leaving it up to higher layers to decide upon policy for dealing with referrals.
> The protocol-ldap provider can send back search response entry or referral PDU's based on the ManageDSAIT control settings.  The JNDI provider wrapping the core will determine whether an exception will be thrown or the referral will be chased etc.  Either way it's the job of higher layers to determine which action to take.  
> This is why this interceptor will be stripped out of the core.  Some core integ tests will be moved out probably into the core-jndi module and other tests will be altered.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.