[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068057#comment-14068057
]
Thiago H. de Paula Figueiredo commented on TAP5-2192:
-----------------------------------------------------
Hello, Lance!
I've followed your suggestion almost to the letter, except for service names,
and it worked very well. Thanks for the hint, as always. ;-)
ServiceConfigurationListener is the listener interface, with methods void
onOrderedConfiguration(ServiceDef serviceDef, List configuration), void
onUnorderedConfiguration(ServiceDef serviceDef, Collection configuration) and
void onMappedConfiguration(ServiceDef serviceDef, Map configuration).
ServiceConfigurationListenerHub is the service to which
ServiceConfigurationListeners are contributed. At first, I tried without the
hub service, with contributions going to a ServiceConfigurationListener, but
then its implementations tend to be services as well, causing exceptions due to
two services matching the same interface.
Lance, interesting facts: I implemented the event storing and replaying in the
end of the RegistryImpl constructor, but then I noticed no service distributed
configuration is calculated until after the constructor ends, so maybe the
event storing and replaying isn't actually needed. I kept it because it's
already implemented, uses almost no resources and I'm not 100% sure this will
be true for all cases.
I'm going to tackle ComponentLibraryInfoSource now.
> 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)
