[ 
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058819#comment-14058819
 ] 

Lance edited comment on TAP5-2192 at 7/11/14 2:06 PM:
------------------------------------------------------

Hi Thiago, did you see my ContributionListener suggestion? The default 
implementation could do nothing. But Barry could override the listener with one 
that stored lists of the contributions which he can look up. This way, the core 
implementation doesn't have to deal with garbage collection at all. 


was (Author: uklance):
Hi Thiago, did you see my ContributionListener suggestion? The default 
implementation could do nothing. But Barry could override the listener with one 
that sorted lists of the contributions. This way, the core implementation 
doesn't have to deal with garbage collection at all. 

> 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)

Reply via email to