[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059211#comment-14059211
]
Lance commented on TAP5-2192:
-----------------------------
Thiago, I'm suggesting that tapestry ioc internally has a hard coded
InternalContributionListener. This is not a service, it is a hard coded
instantiation.
Every time tapestry-ioc does a contribution, it fires the
InternalContributionListener.
There is also a public ContributionListener service. By default this does
nothing but can be overridden by Barry.
To solve the chicken or egg scenario, the InternalContributionListener saves
any contribution events to a List until the ContributionListener service
exists. Once it exists, it flushes it's events to the ContributionListener. All
future contribution events pass straight through to the ContributionListener.
> Add support for distributed documentation
> -----------------------------------------
>
> Key: TAP5-2192
> URL: https://issues.apache.org/jira/browse/TAP5-2192
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.4
> Reporter: Barry Books
> Assignee: Thiago H. de Paula Figueiredo
> Labels: documentation, month-of-tapestry
>
> Please add support for a distributed documentation system. The basic
> requirements are:
> 1. Access to a list of Pages/Compoents/Mixins. (ComponentClassResolver
> supports pages)
> 2. Access to a Map of all Configurations. The map would have the
> configuration class as the Key and contain an object such a list or map that
> contains the configuration.
> 3. Access to a list of configured services.
> From this it should be possible to build documentation of a running system.
> Thanks
> Barry
--
This message was sent by Atlassian JIRA
(v6.2#6252)
