synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <>
Subject [jira] Resolved: (SYNAPSE-516) Deprecation of AbstractMediatorFactory.processTraceState() instead of removing it
Date Mon, 09 Mar 2009 17:14:50 GMT


Asankha C. Perera resolved SYNAPSE-516.

    Resolution: Fixed
      Assignee: Asankha C. Perera

Committed the patch.. Thanks Eric

> Deprecation of AbstractMediatorFactory.processTraceState() instead of removing it
> ---------------------------------------------------------------------------------
>                 Key: SYNAPSE-516
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: FUTURE
>            Reporter: Eric Hubert
>            Assignee: Asankha C. Perera
>            Priority: Minor
>             Fix For: 1.3
>         Attachments:
> while developing and testing the fault detection in the HessianMessageBuilder I'll noticed
that I had to change our custom developed code. 
> The question is whether the code we use is considered part of the API of Synapse or not.

> AbstractmediatorFactory once exposed a protected method called processTraceState() which
had been renamed to processAuditStatus().
> This method is not called inside any other method. So each concrete Factory has to call
it directly. Thus I would consider it to be part of the API as the user may need to write
a factory to process custom config snippets and call it in the create method.

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message