[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058849#comment-14058849
]
Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------
Hello, Lance!
How would that listener be passed to Tapestry-IoC? I don't think that's
possible to implement using typical Tapestry-IoC, as the ContributionListener
would need to be a built-in service (one which is built before the Registry
itself) and I don't think they can be overriden. Distributed configuration
handling is done too deep inside Tapestry-IoC. I'd be more than happy to be
proven wrong, of course. :)
> 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)
