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/10/23 21:53:37 UTC
[jira] Assigned: (DIRSEDA-14) Why bother with AbstractSubscriber.inform when we enqueue anyway?
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