[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1233) Extend @Scope to work on member variables/properties

Marcell Barbacena (JIRA) jira-events at lists.jboss.org
Sat Mar 22 19:42:39 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBSEAM-1233?page=comments#action_12404192 ] 
Marcell Barbacena commented on JBSEAM-1233:

Isn't it the same to define the get/set in the bean?

Use case B:
<h:outputText value="#{bean.someVariable}" />

Ties to:
private String someVariable;
public String getSomeVariable() {
  return someVariable;

> Extend @Scope to work on member variables/properties
> ----------------------------------------------------
>                 Key: JBSEAM-1233
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1233
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.1.6.GA
>            Reporter: Andrew
> I have a relate bug:
> http://jira.jboss.com/jira/browse/JBSEAM-903
> My purpose for this bug was mostly due to binding issues. There are times that I want to have the scope of a member variable to be different from the scope of the bean. Especially, if the bean is conversational and I want the field/property to have event scope. Instead of the proposed @InOut from the above bug, perhaps just extending @Scope would work:
> @Scope(ScopeType.EVENT)
> private MyVar myVar;
> Unlike @In and @Out, this scope would not put use the contexts to get and set values, but simply control the lifecycle of the variable. In this example, myVar could be set to null when the the variables of the bean are out-jected. As it stands, there is no other easy way that I know of to have a variable set to null at then end of a page request.

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


More information about the seam-issues mailing list