You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Vanjikumaran Sivajothy (JIRA)" <ji...@apache.org> on 2017/09/24 19:59:00 UTC

[jira] [Updated] (SYNAPSE-441) Declare the public API of Synapse, so that custom Mediator and Task developers know the boundary between the public API and Synapse internals

     [ https://issues.apache.org/jira/browse/SYNAPSE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vanjikumaran Sivajothy updated SYNAPSE-441:
-------------------------------------------
    Fix Version/s:     (was: 2.0)
                   FUTURE

> Declare the public API of Synapse, so that custom Mediator and Task developers know the boundary between the public API and Synapse internals
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-441
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-441
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.2
>            Reporter: Asankha C. Perera
>            Assignee: Asankha C. Perera
>             Fix For: FUTURE
>
>
> Eric and Luca has brought to my attention that there is no clear document for Synapse that shows which classes constitute our public API - safe for Mediator, Task and extension writers to use.
> This JIRA is a placeholder to make sure that we include this valuable information into our standard document on "Extending Synapse"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org