You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2010/09/15 00:14:33 UTC

[jira] Created: (EXTCDI-53) eval producers for all config entries

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.

[jira] Commented: (EXTCDI-53) eval producers for all config entries

Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909484#action_12909484 ] 

Gerhard Petracek commented on EXTCDI-53:
----------------------------------------

if there are no objections, i move the existing producer methods to an external codi add-on

> 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.

[jira] Issue Comment Edited: (EXTCDI-53) eval producers for all config entries

Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
    [ 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.

[jira] Resolved: (EXTCDI-53) eval producers for all config entries

Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek resolved EXTCDI-53.
------------------------------------

    Fix Version/s: 1.0.0-SNAPSHOT
       Resolution: Fixed

> 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
>             Fix For: 1.0.0-SNAPSHOT
>
>
> 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.

[jira] Commented: (EXTCDI-53) eval producers for all config entries

Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/EXTCDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909481#action_12909481 ] 

Gerhard Petracek commented on EXTCDI-53:
----------------------------------------

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.