[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 3:11 PM: -- Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do all of this from my IDE which is up and available the whole day, unlike my jetty instance. was (Author: uklance): Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc It sounds like a maintenance nightmare and I don't really see the value. I do all of this from my IDE which is up and available the whole day, unlike my jetty instance. 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 3:10 PM: -- Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc It sounds like a maintenance nightmare and I don't really see the value. I do all of this from my IDE which is up and available the whole day, unlike my jetty instance. was (Author: uklance): Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. From what I can see there is - code to integrate with maven - code to append .java to the end of class names (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc It sounds like a maintenance nightmare and I don't really see the value. I do all of this from my IDE which is up and available the whole day, unlike my jetty instance. 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 3:13 PM: -- Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. was (Author: uklance): Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 3:16 PM: -- Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. Have you seen the gradle plugin portal? http://plugins.gradle.org/ This is driven by tags in bintray http://plugins.gradle.org/submit Perhaps tapestry needs something similar? was (Author: uklance): Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 3:12 PM: -- Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. was (Author: uklance): Hi Thiago, as I've said before. I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. At least if it's optional I could exclude it. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do all of this from my IDE which is up and available the whole day, unlike my jetty instance. 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 3:28 PM: -- Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. Have you seen the gradle plugin portal? http://plugins.gradle.org/ This is driven by tags in bintray http://plugins.gradle.org/submit Perhaps a third party could provide something similar for tapestry? was (Author: uklance): Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. Have you seen the gradle plugin portal? http://plugins.gradle.org/ This is driven by tags in bintray http://plugins.gradle.org/submit Perhaps tapestry needs something similar? 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 4:35 PM: -- Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven (reading a maven pom) - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. Have you seen the gradle plugin portal? http://plugins.gradle.org/ This is driven by tags in bintray http://plugins.gradle.org/submit Perhaps a third party could provide something similar for tapestry? was (Author: uklance): Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. Have you seen the gradle plugin portal? http://plugins.gradle.org/ This is driven by tags in bintray http://plugins.gradle.org/submit Perhaps a third party could provide something similar for tapestry? 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109275#comment-14109275 ] Lance edited comment on TAP5-2192 at 8/25/14 4:34 PM: -- Hi Thiago, reading from pom.xml IS integrating with maven IMO. I was using http://plugins.gradle.org/ as an example of a plugin repository with links to source and documentation and other information about each plugin... please ignore the Gradle reference. I used this example because I like the way that it's driven from bintray tags. I think we'll have to agree to disagree about this. was (Author: uklance): Hi Thiago, reading from pom.xml IS integrating with maven IMO. I was using http://plugins.gradle.org/ as an example of a plugin repository with links to source and documentation and other information about each plugin... please ignore the Gradle reference. I used this example because I like the way that it's driven from bintray tags. 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109180#comment-14109180 ] Lance edited comment on TAP5-2192 at 8/25/14 4:36 PM: -- Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven (reading a maven pom) - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface (should we integrate with subversion, perforce, etc) - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. Have you seen the gradle plugin portal? http://plugins.gradle.org/ This is driven by tags in bintray http://plugins.gradle.org/submit Perhaps a third party could provide something similar for tapestry? was (Author: uklance): Hi Thiago, as I've said before, I really don't think tapestry should be doing this task at all. In my opinion it's outside of tapestry's scope. If the functionality was optional I could exclude it from my projects. From what I can see there is - code to integrate with maven (reading a maven pom) - code to append .java to the end of class names for source lookups (what about groovy and scala?) - code to integrate with git's web interface - code to integrate with javadoc (append html to class name etc) It sounds like a maintenance nightmare and I don't really see the value. I do most of this from my IDE which is up and available the whole day, unlike my jetty instance. Have you seen the gradle plugin portal? http://plugins.gradle.org/ This is driven by tags in bintray http://plugins.gradle.org/submit Perhaps a third party could provide something similar for tapestry? 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 Fix For: 5.4 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:20 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{code}
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queued.clear();
queued = null;
}
// same for other events
}
{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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:20 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queued.clear();
queued = null;
}
// same for other events
}
{code}
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable runnable : queued) {
queued.run();
}
queued.clear();
queued = null;
}
// same for other events
}
{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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:19 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable runnable : queued) {
queued.run();
}
queued.clear();
queued = null;
}
// same for other events
}
{code}
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:21 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:50 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable queue = CollectionFactory.newList();
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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable 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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:54 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable queue = CollectionFactory.newList();
public void onOrderedConfiguration(ServiceDef serviceDef, List
configuration) {
if (delegates == null) {
queue.add(new Runnable() { public void run() {
onOrderedConfiguration(serviceDef, configuration); } });
} else {
for (ServiceConfigurationListener delegate : delegates) {
delegate.onOrderedConfiguration(serviceDef, configuration);
}
}
}
public void setDelegates(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable queue = CollectionFactory.newList();
public void onOrderedConfiguration(ServiceDef serviceDef, List
configuration) {
if (delegates == null) {
queue.add(new Runnable() { public void run() {
onOrderedConfiguration(serviceDef, configuration); } });
} else {
for (ServiceConfigurationListener delegate : delegates) {
delegate.onOrderedConfiguration(serviceDef, configuration);
}
}
}
public void setDelegates(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:53 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable queue = CollectionFactory.newList();
public void onOrderedConfiguration(ServiceDef serviceDef, List
configuration) {
if (delegates == null) {
queue.add(new Runnable() { public void run() {
onOrderedConfiguration(serviceDef, configuration); } });
} else {
for (ServiceConfigurationListener delegate : delegates) {
delegate.onOrderedConfiguration(serviceDef, configuration);
}
}
}
public void setDelegates(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable queue = CollectionFactory.newList();
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(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
queue= null;
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068313#comment-14068313
]
Lance edited comment on TAP5-2192 at 7/21/14 8:56 AM:
--
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private class DelegatingServiceConfigurationListener implements
ServiceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable queue = CollectionFactory.newList();
public void onOrderedConfiguration(ServiceDef serviceDef, List
configuration) {
if (delegates == null) {
queue.add(new Runnable() { public void run() {
onOrderedConfiguration(serviceDef, configuration); } });
} else {
for (ServiceConfigurationListener delegate : delegates) {
delegate.onOrderedConfiguration(serviceDef, configuration);
}
}
}
public void setDelegates(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
was (Author: uklance):
FYI, If you wanted to remove the hashCode() and equals() you could do it as
follows:
{code}
private DelegatingServiceConfigurationListener serviceConfigurationListener {
private ListServiceConfigurationListener delegates;
private ListRunnable queue = CollectionFactory.newList();
public void onOrderedConfiguration(ServiceDef serviceDef, List
configuration) {
if (delegates == null) {
queue.add(new Runnable() { public void run() {
onOrderedConfiguration(serviceDef, configuration); } });
} else {
for (ServiceConfigurationListener delegate : delegates) {
delegate.onOrderedConfiguration(serviceDef, configuration);
}
}
}
public void setDelegates(ListServiceConfigurationListener delegates) {
this.delegates = delegates;
for (Runnable queued : queue) {
queued.run();
}
queue.clear();
}
// same for other events
}
{code}
This would also retain the ordering of the configurations.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055368#comment-14055368 ] Lance edited comment on TAP5-2192 at 7/9/14 7:32 AM: - Hi Thiago, I've just fired up the t5dashboard/componentlibraries page. I think a page listing the components is generally a good idea (better if it can be disabled). But I really hate the idea of configuring homepage URL's, artifact id's, group codes, javadoc and source locations inside tapestry. Since maven / gradle know this info, I'd be far less concerned with an option which made use of this. ie write the version / artifact id / javadoc url etc to the jar's manifest at build time (or an XML / JSON file) and look it up at runtime. Please see my ComponentLibraryInfoSource suggestion above. I doubt I'd use a feature like this since I can easily view source code / javadoc from my IDE. was (Author: uklance): Hi Thiago, I've just fired up the t5dashboard/componentlibraries page. I think a page listing the components is generally a good idea (better if it can be disabled). But I really hate the idea of configuring homepage URL's, artifact id's, group codes, javadoc and source locations inside tapestry. Since maven / gradle know this info, I'd be far less concerned with an option which made use of this. ie write the version / artifact id / javadoc url etc to the jar's manifest at build time (or an XML / JSON file) and look it up at runtime. Please see my ComponentLibraryInfoSource suggestion above. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054435#comment-14054435
]
Lance edited comment on TAP5-2192 at 7/8/14 9:05 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(ServiceDescriptor d, List l);
void onConfigureMap(ServiceDescriptor d, Map m);
void onConfigureCollection(ServiceDescriptor d, Collection c);
}
public interface ServiceDescriptor {
Class getServiceInterface();
String getServiceId();
SetClass 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
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();
T extends Annotation ListClassT getMarkers();
}
{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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1405#comment-1405 ] Lance edited comment on TAP5-2192 at 7/8/14 9:08 AM: - You are correct that there's only 1 configuration (List, Map, Collection) per service. But 2 services can have the same service interface. The ServiceIdentifier would be the combination of service interface, service id and any marker annotations. All these combined uniquely identify a service. was (Author: uklance): You are correct that there's only 1 configuration (List, Map, Collection) per service. But 2 services can have the same service interface. The ServiceDescriptor would be the combination of service interface, service id and any marker annotations. All these combined uniquely identify a service. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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();
SetClass 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();
SetClass 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055368#comment-14055368 ] Lance edited comment on TAP5-2192 at 7/8/14 7:47 PM: - Hi Thiago, I've just fired up the t5dashboard/componentlibraries page. I think a page listing the components is generally a good idea (better if it can be disabled). But I really hate the idea of configuring homepage URL's, artifact id's, group codes, javadoc and source locations inside tapestry. Since maven / gradle know this info, I'd be far less concerned with an option which made use of this. ie write the version / artifact id / javadoc url etc to the jar's manifest at build time (or an XML / JSON file) and look it up at runtime. Please see my ComponentLibraryInfoSource suggestion above. was (Author: uklance): Hi Thiago, I've just fired up the t5dashboard/componentlibraries page. I think a page listing the components is generally a good idea (better if it can be disabled). But I really hate the idea of configuring homepage URL's, artifact id's, group codes, javadoc and source locations inside tapestry. If I want javadoc and source code, it's only a few keystrokes away in my IDE... No config required. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14053728#comment-14053728 ] Lance edited comment on TAP5-2192 at 7/7/14 3:03 PM: - I'm looking at ComponentLibraryInfo and I think that these details are outside of tapestry's scope. Homepage url for a library? Source root for a library? I really don't think that tapestry should be concerning itself with such information. Perhaps a maven plugin or gradle plugin could generate a service to provide this but I really don't feel it's tapestry's job. was (Author: uklance): I'm looking at ComponentLibraryInfo and I think that these details are outside of tapestry's scope. Homepage url for a library? Source root for a library? I really don't think that tapestry should be concerning itself with such information. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14053728#comment-14053728 ] Lance edited comment on TAP5-2192 at 7/7/14 3:28 PM: - I'm looking at ComponentLibraryInfo and I think that these details are outside of tapestry's scope. Homepage url for a library? Source root for a library? I really don't think that tapestry should be concerning itself with such information. Perhaps a maven plugin or gradle plugin could generate a service to provide this but I really don't feel it's tapestry's job. Since these attributes are already available in maven/gradle I feel this breaks the DRY principle too. was (Author: uklance): I'm looking at ComponentLibraryInfo and I think that these details are outside of tapestry's scope. Homepage url for a library? Source root for a library? I really don't think that tapestry should be concerning itself with such information. Perhaps a maven plugin or gradle plugin could generate a service to provide this but I really don't feel it's tapestry's job. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054080#comment-14054080 ] Lance edited comment on TAP5-2192 at 7/7/14 7:32 PM: - If this was a gradle plugin, you would have direct access to the javadoc html (through the javadoc artifact) and the source code (through the sources artifact). This would eliminate the need for a sources root and a javadoc root. You'd also have access to the dependency version numbers which is much better than forcing library authors to maintain the version number in two places. This would be a great gradle plugin. You could auto-generate a service that could be used in many more places than just tapestry webapps. After thinking about this more... I am even more convinced this should be handled at build time (in gradle) and NOT by tapestry. was (Author: uklance): If this was a gradle plugin, you would have direct access to the javadoc html (through the javadoc artifact) and the source code (through the sources artifact). This would eliminate the need for a sources root and a javadoc root. You'd also have access to the dependency version numbers which is much better than forcing library authors to maintain the version number in two places. This would be a great gradle plugin. You could auto-generate a service that could be used in many more places than just tapestry webapps. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054080#comment-14054080 ] Lance edited comment on TAP5-2192 at 7/7/14 7:32 PM: - If this was a gradle plugin, you would have direct access to the javadoc html (through the javadoc artifact) and the source code (through the sources artifact). This would eliminate the need for a sources root and a javadoc root. You'd also have access to the dependency version numbers which is much better than forcing library authors to maintain the version number in two places (lets consider CI builds where it changes every checkin). This would be a great gradle plugin. You could auto-generate a service that could be used in many more places than just tapestry webapps. After thinking about this more... I am even more convinced this should be handled at build time (in gradle) and NOT by tapestry. was (Author: uklance): If this was a gradle plugin, you would have direct access to the javadoc html (through the javadoc artifact) and the source code (through the sources artifact). This would eliminate the need for a sources root and a javadoc root. You'd also have access to the dependency version numbers which is much better than forcing library authors to maintain the version number in two places. This would be a great gradle plugin. You could auto-generate a service that could be used in many more places than just tapestry webapps. After thinking about this more... I am even more convinced this should be handled at build time (in gradle) and NOT by tapestry. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054122#comment-14054122 ] Lance edited comment on TAP5-2192 at 7/7/14 8:01 PM: - Yes, my big complaint is asking library authors to reliably give us this information and keep it up to date. I also feel that this getting out of scope for what tapestry is (an ioc container and a web framework). By asking for a javadoc / sources URL I can only assume that you are also wanting component authors to publish their javadoc / sources to a public URL. IMHO it's better to add the sources / javadoc artifacts to the classpath and access from there. was (Author: uklance): Yes, my big complaint is asking library authors to reliably give us this information and keep it up to date. By asking for a javadoc / sources URL I can only assume that you are also wanting component authors to publish their javadoc / sources to a public URL. IMHO it's better to add the sources / javadoc artifacts to the classpath and access from there. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054271#comment-14054271
]
Lance edited comment on TAP5-2192 at 7/7/14 11:11 PM:
--
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be implemented / overrided. Perhaps
driven by an XML file generated at build time etc. Using Resource also allows
javadoc to be sourced from classpath or a URL etc.
was (Author: uklance):
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be implemented / overrided. Perhaps
driven by an XML file generated at build time etc.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054271#comment-14054271
]
Lance edited comment on TAP5-2192 at 7/7/14 11:12 PM:
--
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be contributed to and overridden.
Perhaps driven by an XML file generated at build time etc. Using Resource also
allows javadoc to be sourced from classpath or a URL etc.
was (Author: uklance):
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be implemented / overrided. Perhaps
driven by an XML file generated at build time etc. Using Resource also allows
javadoc to be sourced from classpath or a URL etc.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054271#comment-14054271
]
Lance edited comment on TAP5-2192 at 7/7/14 11:13 PM:
--
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String URL's. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be contributed to and overridden.
Perhaps driven by an XML file generated at build time etc. Using Resource also
allows javadoc to be sourced from classpath or a URL etc.
was (Author: uklance):
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be contributed to and overridden.
Perhaps driven by an XML file generated at build time etc. Using Resource also
allows javadoc to be sourced from classpath or a URL etc.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054271#comment-14054271
]
Lance edited comment on TAP5-2192 at 7/7/14 11:14 PM:
--
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String URL's. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be contributed to and overridden.
Perhaps driven by an XML file generated at build time etc. Using Resource also
allows javadoc to be sourced from classpath or a URL etc.
This feels much more like 'the tapestry way' of doing things.
was (Author: uklance):
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String URL's. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be contributed to and overridden.
Perhaps driven by an XML file generated at build time etc. Using Resource also
allows javadoc to be sourced from classpath or a URL etc.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054271#comment-14054271
]
Lance edited comment on TAP5-2192 at 7/8/14 12:09 AM:
--
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String URL's. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be contributed to and overridden.
Perhaps driven by an XML file generated at build time etc. Or better yet,
library authors could add the maven version / artifact to the jar manifest and
the service could look it up.
Using Resource also allows javadoc and sources to be sourced from classpath or
a URL etc.
This feels much more like 'the tapestry way' of doing things.
was (Author: uklance):
How's this for a compromise... my main problem is requiring the configuration
inside tapestry. I don't necessarily mind that it's modelled inside tapestry.
1. Remove getComponentLibraryInfo() from LibraryMapping
2. Add ComponentLibraryInfoSource
{code}
public interface ComponentLibraryInfoSource {
ComponentLibraryInfo getComponentLibraryInfo(String libraryName);
}
{code}
3. Change ComponentLibraryInfo to use Resource instead of String URL's. eg
{code}
public interface ComponentLibraryInfo {
Resource getHomePageRoot();
Resource getSourceRoot();
Resource getJavadocRoot();
// etc
}
{code}
This way, ComponentLibraryInfoSource could be contributed to and overridden.
Perhaps driven by an XML file generated at build time etc. Using Resource also
allows javadoc to be sourced from classpath or a URL etc.
This feels much more like 'the tapestry way' of doing things.
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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054435#comment-14054435
]
Lance edited comment on TAP5-2192 at 7/8/14 2:41 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(ServiceDescriptor d, List l);
void onConfigureMap(ServiceDescriptor d, Map m);
void onConfigureCollection(ServiceDescriptor d, Collection c);
}
{code}
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 ConfigurationListener {
void onConfigureList(ServiceDescriptor d, List l);
void onConfigureMap(ServiceDescriptor d, Map m);
void onConfigureCollection(ServiceDescriptor d, Collection c);
}
{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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[ https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1405#comment-1405 ] Lance edited comment on TAP5-2192 at 7/8/14 2:55 AM: - You are correct that there's only 1 configuration (List, Map, Collection) per service. But 2 services can have the same service interface. The ServiceDescriptor would be the combination of service interface, service id and any marker annotations. All these combined uniquely identify a service. was (Author: uklance): Yes, the ServiceDescriptor would be the combination of service interface, service id and any marker annotations. 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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054435#comment-14054435
]
Lance edited comment on TAP5-2192 at 7/8/14 3:03 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(ServiceDescriptor d, List l);
void onConfigureMap(ServiceDescriptor d, Map m);
void onConfigureCollection(ServiceDescriptor d, Collection c);
}
public interface ServiceDescriptor {
Class getInterface();
String getId();
T extends Annotation ListT getMarkers();
}
{code}
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);
}
{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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054435#comment-14054435
]
Lance edited comment on TAP5-2192 at 7/8/14 3:05 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(ServiceDescriptor d, List l);
void onConfigureMap(ServiceDescriptor d, Map m);
void onConfigureCollection(ServiceDescriptor d, Collection c);
}
public interface ServiceDescriptor {
Class getInterface();
String getId();
T extends Annotation ListClassT getMarkers();
}
{code}
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 getInterface();
String getId();
T extends Annotation ListT getMarkers();
}
{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)
[jira] [Comment Edited] (TAP5-2192) Add support for distributed documentation
[
https://issues.apache.org/jira/browse/TAP5-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054435#comment-14054435
]
Lance edited comment on TAP5-2192 at 7/8/14 3:13 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(ServiceDescriptor d, List l);
void onConfigureMap(ServiceDescriptor d, Map m);
void onConfigureCollection(ServiceDescriptor d, Collection c);
}
public interface ServiceDescriptor {
Class getServiceInterface();
String getServiceId();
T extends Annotation ListClassT getMarkers();
}
{code}
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 getInterface();
String getId();
T extends Annotation ListClassT getMarkers();
}
{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)
