You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/09/28 16:41:44 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12635226#action_12635226 ]
Andreas Veithen commented on SYNAPSE-441:
-----------------------------------------
Maybe we should move the classes that compose the public API to a different module? That way, people can easily check that their extensions don't use internal APIs (simply by depending only on the API module).
> 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: 1.3
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org