[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4349) Provide static injection option via @In

Gonzalez Adrian (JIRA) jira-events at lists.jboss.org
Tue Sep 15 17:20:23 EDT 2009


    [ https://jira.jboss.org/jira/browse/JBSEAM-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12485957#action_12485957 ] 

Gonzalez Adrian commented on JBSEAM-4349:
-----------------------------------------

This would forbid injection of non serializable data into a conversation or session or paged scoped component.

Out of topic : 
This remark can be stupid, but perhaps changing injection logic by using a serializable scoped proxy instead could enhance Seam performance ?
Something like this : http://jira.springframework.org/browse/SPR-2121.
The problem with @In is that it's called every time a component action is called, even if we don't need it.
Advantage of serializable scoped proxy is that the proxy is called only when you explicitly call it.


> Provide static injection option via @In
> ---------------------------------------
>
>                 Key: JBSEAM-4349
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4349
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 2.2.0.GA
>         Environment: n/a
>            Reporter: asookazian
>
> Currently injection in Seam via @In is dynamic only.  By dynamic, we mean that the instance variable that is associated with the @In annotation is refreshed with the latest value from the specified context every time a business method is invoked (specifically prior to the invocation).
> Request is to add a facility to allow developer to specify static injection only for that particular @In annotation instance.  Add an optional element named "type" to @In.
> example:
> @In(type=static)
> private String foo;
> The default type or behavior will be dynamic.
> The purpose of this request is to support use case implementations that do not require dynamic injections but merely one-time static injections like Spring DI setter or constructor injections.  This will help with performance as well as there will not be unnecessary "refreshing" of the instance variables via dynamic injection in those cases that are not needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list