Actually, I'm not completely convinced yet.
Reason against: We might want to add parameters to the annotations. We
can't add them to the JSR-330 ones.
Counterargument: But on the other hand, we could place these additional
parameters, when and if we invent them, on a new annotation without
creating overlap with JSR-330
Tom.
Op 21-12-2010 9:20, Igor Drobiazko schreef:
Now that 5.2 is out, we can start working on 5.3. I'm going to add support
for JSR-330: Dependency Injection for Java in the next days, weeks.
I believe now it is time to think about whether we still need our own
annotations for injection. I think that support of standard annotations
would improve the adoption of Tapestry. Here are the overlappings of JSR-330
and Tapestry IoC:
org.apache.tapestry5.ioc.annotations.Inject = javax.inject.Inject
org.apache.tapestry5.ioc.annotations.InjectService = javax.inject.Inject and
javax.inject.Named
org.apache.tapestry5.ioc.annotations.Scope = javax.inject.Scope
Probably it makes sence to add a new depenendency for Tapestry IoC and not
to provide a new library. I'd rather deprecate our own annotations and
encourage people to move to standard annotations.
What do you think?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
