directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Assigned: (DIRSEDA-14) Why bother with AbstractSubscriber.inform when we enqueue anyway?
Date Sat, 23 Oct 2004 19:53:37 GMT
Message:

   The following issue has been re-assigned.

   Assignee: Trustin Lee (mailto:trustin@gmail.com)
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSEDA-14

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSEDA-14
    Summary: Why bother with AbstractSubscriber.inform when we enqueue anyway?
       Type: Task

     Status: Open
   Priority: Major

    Project: Seda Framework

   Assignee: Trustin Lee
   Reporter: Alex Karasulu

    Created: Sat, 20 Mar 2004 9:54 AM
    Updated: Sat, 23 Oct 2004 12:52 PM

Description:
Do we really need to do this since we enqueue no matter what?

    public void inform( EventObject event )
    {
        try
        {
            AbstractSubscriber.inform( this, event ) ;
        }
        catch( Throwable t )
        {
            monitor.failedOnInform( this, event, t ) ;
        }
    }
    
    
    public void inform( OutputEvent event )
    {
        enqueue( event ) ;
    }
    



---------------------------------------------------------------------
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


Mime
View raw message