I'm with thiago here,
module is not something we change all the time
like pages and components, it gets written bit by bit.
Naming conventions here don't speed-up development in scope
of the whole project.
@Contribute(FooBar.class)
I would even say it's faster because you can use autocomplete.
Em Sun, 14 Oct 2007 12:40:38 -0300, Howard Lewis Ship [EMAIL PROTECTED]
escreveu:
This is heading a bit backwards from my initial goals, of naming
conventions over annotations, and raises the question of the convention
for naming such methods,
I think that to rely just on naming
在 Sun, 14 Oct 2007 23:40:38 +0800，Howard Lewis Ship [EMAIL PROTECTED] 写
道:
Where I dropped the ball here, in a minor way, is that it should be
contributeTo as a prefix, or perhaps configure. It's a prefix on the
*service* being configured or contributed to. So I would choose option
#2
or
Where I dropped the ball here, in a minor way, is that it should be
contributeTo as a prefix, or perhaps configure. It's a prefix on the
*service* being configured or contributed to. So I would choose option #2
or #3.
I wonder if there's some value in something like:
@Contribute(FooBar.class)
Howard,
Just in case that was an invitation for proposals :), how about:
contributeSomethingToSomeService(), where 'Something' is optional?
Allows for a little more specificity while still being an easily
parsed convention. And for those that don't care - its only two more
characters :)
In any
Tapestry-ioc already calls the something a configuration:
http://tapestry.apache.org/tapestry5/tapestry-ioc/configuration.html
so Howard's configure naming suggestion looks even better.
(This has been discussed previously in this list.)
Cheers,
Nick.
lasitha wrote:
Howard,
Just in case that
Thanks Nick - you're right, i should have looked over list and jira first:
http://thread.gmane.org/gmane.comp.java.tapestry.user/51015
https://issues.apache.org/jira/browse/TAPESTRY-1679
I agree that 'configure' is a step forward -
configureRequestHandler() is better than
Let's say you have a service that allows multiple contributions. One of
the contributions is simply a list of other objects (say an ordered
configuration). What is the naming convention for the configuration
point for that list of objects? For instance, lets say you want to have
a list of FooBars
