tapestry-commits mailing list archives

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

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

Lance commented on TAP5-2192:
-----------------------------

FYI, If you wanted to remove the hashCode() and equals() you could do it as follows:

{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
   private List<ServiceConfigurationListener> delegates;
   private List<Runnable> queue = CollectionFactory.newMap();

   public void onOrderedConfiguration(ServiceDef serviceDef, List configuration) {
      if (delegates == null) {
         queue.add(new Runnable() { public void run() { this.onOrderedConfiguration(serviceDef,
configuration); } });
      } else {
         for (ServiceConfigurationListener delegate : delegates) {
            delegate.onOrderedConfiguration(serviceDef, configuration);
         }
      }
   }

   public void setDelegates(List<ServiceConfigurationListener> delegates) {
      this.delegates = delegates;
      for (Runnable runnable : queued) {
         queued.run();
      }
      queued.clear();
      queued = null;
  }
  
  ...
}
{code}
         


> 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