[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059151#comment-14059151
]
Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------
Lance, my plan so far has been a little bit different: I think the main, and
probably only, use of this listener will be for manual checks of contributions,
so only one listener will be used. This way, there would be a default listener
implementation that just logs the contributions at debug level, but it could be
overriden by using a system property contaning the fully qualified class name
of the new listener.
In your suggestion, I didn't understand how to implement what you call the
initial contributions. Built-in services cannot have distributed configuration,
because they're instantiated before the registry itself, and it (the registry)
is the one that handles configuration. I see a chicken-and-egg problem there.
> 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)
