[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-271) null Seam components OR default scope for non-Seam components

[Pete Muir (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-271?page=all ]

Pete Muir closed JBSEAM-271.
----------------------------

    Resolution: Won't Fix

I don't see how this is useful. There is a default, the scope of the outjecting component. Alternatively, you can use the manager pattern to specify a default scope.

I've also never seen a single request for this functionality on the forum.

> null Seam components OR default scope for non-Seam components
> -------------------------------------------------------------
>
>                 Key: JBSEAM-271
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-271
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>            Reporter: Raul Piaggio
>            Priority: Minor
>
> Seam-managed components have a default Seam scope and are always created upon reference by a view.
> User-managed variables can be created and destroyed ad-hoc, but they don't have a default scope (it has to be specified in every outjection, leading to more costly code maintenance).
> The request is for a feature to allow creating and destroying variables in the Seam-controlled space but specify their scope in a unique location. (See forum reference for an example).
> Suggestions:
> 1) Allow null Seam components. This could be achieved with a "create" or "required" property in the @Role annotation (and in @Scope). Defaults to "true", but we could specify "create=false" or "required=false".
> 2) Create another annotation, similar to @Role and with the same properties. This would allow to specify a role and default scope for a class, which would not be Seam-managed in that role.
> Note that ideally, we would have role granularity, not class. That is to say, the same class would be Seam-managed in some roles but not in others. (Again, see forum reference).
> Thank you.

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