[jira] Commented: (DIR-36) Mock decoder returns 'busy' ldap resp result

[ji...@apache.org]

The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Thu, 4 Mar 2004 8:47 PM
       Body:
I'm a bit stupid.  It's upto the output manage to report the result message generated by the encoder.  The decoder just produces a message.  I need to get my arms around this jmock stuff and start rocking away with it because I'm going to have to assemble a bogus message in the decoder for this peice.

Perhaps its also a good time to start working on this provider framework thingy again.  We definately need to revisit this concept again because its not upto par now with NIO.

---------------------------------------------------------------------
View this comment:
  http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=DIR-36&page=comments#action_20978

---------------------------------------------------------------------
View the issue:
  http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=DIR-36

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIR-36
    Summary: Mock decoder returns 'busy' ldap resp result
       Type: Task

     Status: Open
   Priority: Major

    Project: Directory
 Components: 
             Eve

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Thu, 4 Mar 2004 8:39 PM
    Updated: Thu, 4 Mar 2004 8:47 PM

Description:
Step III:

Make mock decoder return a preconfigured response 'busy' ldap result for any request.  For now it should just be a bindresponse because no other ops should occur.  

Eventually as snickers comes along we might be able to respond by actually detecting the message type and id.



Step IV:
Setup decoder to read content in one shot using the existing
snacc decoder to generate a Message.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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