[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054435#comment-14054435
]
Lance edited comment on TAP5-2192 at 7/8/14 9:07 AM:
-----------------------------------------------------
Barry, for point 2. of this jira (accessing configuration info) you can't have
a map by class since there can be multiple services for a service interface.
I'd say a listener approach might be better
{code}
public interface ContributionListener {
void onConfigureList(ServiceIdentifier id, List l);
void onConfigureMap(ServiceIdentifier id, Map m);
void onConfigureCollection(ServiceIdentifier id, Collection c);
}
public interface ServiceIdentifier {
Class getServiceInterface();
String getServiceId();
Set<Class> getMarkers();
}
{code}
I guess that ServiceDef should extend this new ServiceIdentifier interface too:
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/def/ServiceDef.html
was (Author: uklance):
Barry, for point 2. of this jira (accessing configuration info) you can't have
a map by class since there can be multiple services for a service interface.
I'd say a listener approach might be better
{code}
public interface ContributionListener {
void onConfigureList(ServiceDescriptor d, List l);
void onConfigureMap(ServiceDescriptor d, Map m);
void onConfigureCollection(ServiceDescriptor d, Collection c);
}
public interface ServiceDescriptor {
Class getServiceInterface();
String getServiceId();
Set<Class> getMarkers();
}
{code}
I guess that ServiceDef should extend this new ServiceDescriptor interface too:
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/def/ServiceDef.html
> 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)
