Ok, let me provide more details. We have two implementations of the DataTypeAnalyzer service in the registry. The primary implementation is a chain of AnnotationDataTypeAnalyzer and DefaultDataTypeAnalyzer. The user do not contribute to the primary implementation but to the DefaultDataTypeAnalyzer. Currently there is no way to contribute to DefaultDataTypeAnalyzer using @Contribute annotation. There only way to contribute to DefaultDataTypeAnalyzer is to use its id. And that sucks. I want to change it and need a good name for the marker annotation.
On Tue, Jul 12, 2011 at 3:59 AM, Thiago H. de Paula Figueiredo < [email protected]> wrote: > On Mon, 11 Jul 2011 19:34:16 -0300, Igor Drobiazko < > [email protected]> wrote: > > of a marker annotation similar to @Primary. For example, >> DefaultDataTypeAnalyzer is contributed to DataTypeAnalyzer which is >> @Primary. The users never >> contribute to the @Primary DataTypeAnalyzer, but to >> DefaultDataTypeAnalyzer. >> > > I did make contributions for DataTypeAnalyzer directly, defining the data > type based on annotations or even on an specific field. > > > public static void >> contributeDefaultDataTypeAnaly**zer(MappedConfiguration<Class, String> >> configuration) { ... } >> >> So, I'm looking for a good marker name. Any ideas? Maybe @Main or >> @Default? >> > > I didn't really understand the scenario here, maybe because I very > unfortunately haven't had a chance to work with even T5.2, not even 5.3 yet. > :'( > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > -- Best regards, Igor Drobiazko http://tapestry5.de
