[
https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909481#action_12909481
]
Gerhard Petracek edited comment on EXTCDI-53 at 9/14/10 6:15 PM:
-----------------------------------------------------------------
advantages:
- short syntax
- users don't have to know how to use the ConfigResolver
disadvantages:
- it isn't completely typesafe -> more error-prone
- a lot of producer methods
was (Author: gpetracek):
advantage:
- short syntax
- users don't have to know how to use the ConfigResolver
disadvantages:
- it isn't completely typesafe -> more error-prone
- a lot of producer methods
> eval producers for all config entries
> -------------------------------------
>
> Key: EXTCDI-53
> URL: https://issues.apache.org/jira/browse/EXTCDI-53
> Project: MyFaces CODI
> Issue Type: Task
> Components: Core, JEE-BV1-Module, JEE-JSF12-Module,
> JEE-JSF20-Module, JSE-Message, Trinidad Support
> Reporter: Gerhard Petracek
>
> internally we are using the typesafe approach - e.g.:
> @Inject
> private ConfigResolver configResolver;
> //...
> this.configResolver.resolve(WindowContextConfig.class).getWindowContextTimeoutInMinutes();
> we have to eval the support for the following syntax for using it in an
> application:
> example:
> @Inject
> @Config(WindowContextConfig.class)
> private Integer conversationTimeoutInMinutes;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
