tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
Date Mon, 21 Jul 2014 08:08:38 GMT

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

Lance edited comment on TAP5-2192 at 7/21/14 8:08 AM:
------------------------------------------------------

Thiago, I like the solution. Much better than storing the lists and having to consider garbage
collection.

I'm not sure the chicken and egg problem has been solved.

For instance, in RegistrySpec.groovy, what would be the contents of:
{code}listener.getOrderedConfigurations().get("ServiceConfigurationListenerHub"){code}

I'm guessing it would be null / empty? This is what I was trying to solve with InternalContributionListener.

*EDIT*

Actually, it looks like I'm wrong. You do the flushing behaviour in {code}DelegatingServiceConfigurationListener.setDelegates{code}

Thus solving the chicken-and-egg problem.

Thanks for the fix!!


was (Author: uklance):
Thiago, I like the solution. Much better than storing the lists and having to consider garbage
collection.

I'm not sure the chicken and egg problem has been solved.

For instance, in RegistrySpec.groovy, what would be the contents of:
{code}listener.getOrderedConfigurations().get("ServiceConfigurationListenerHub"){code}

I'm guessing it would be null / empty? This is what I was trying to solve with InternalContributionListener.

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

Mime
View raw message