You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/05/29 07:22:01 UTC
[jira] Closed: (DIRSNICKERS-43) Write a ReferralRule
Message:
The following issue has been closed.
Resolver: Alex Karasulu
Date: Fri, 28 May 2004 10:20 PM
Was written a while back.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRSNICKERS-43
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRSNICKERS-43
Summary: Write a ReferralRule
Type: Task
Status: Closed
Priority: Major
Resolution: FIXED
Project: Directory Snickers
Components:
LDAP Provider
Assignee: Alex Karasulu
Reporter: Alex Karasulu
Created: Sun, 18 Apr 2004 2:15 PM
Updated: Fri, 28 May 2004 10:20 PM
Description:
Need to write a rule that builds a Referral object that is to be part of a LdapResult. The rule simply creates an empty ReferralImpl object and pushes it onto the stack. Another OCTET STRING rule extending rule keeps generating ByteBuffers for the LDAPURLs and adding them to the Referral object on the top of the object stack.
If we extend the PrimitiveOctetStringRule and override the finish() method of the rule but call the super method at the top then we can just pop the objectStack for the ByteBuffer since the super call pushes the ByteBuffer of the OCTET STRING onto the objectStack.
So we need two rules to do this right:
1. ReferralUrlRule extends PrimitiveOctetStringRule
2. ReferralRule extends AbstractRule
We could use reflection and have a special form of PrimitiveOctetStringRule that calls a method to add the content it generates but this would slow things down. Plus I'd probably use BeanUtils and that would mean an extra dependency. As a general rule we want to stay far away from reflection in this very low level decoder.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira