[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-dev
Subject:    [jira] Closed: (TAPESTRY-1368) The @ApplicationState annotation
From:       "Howard M. Lewis Ship (JIRA)" <dev () tapestry ! apache ! org>
Date:       2007-03-30 15:27:25
Message-ID: 4707456.1175268445204.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/TAPESTRY-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Howard M. Lewis Ship closed TAPESTRY-1368.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.4
         Assignee: Howard M. Lewis Ship

> The @ApplicationState annotation should be capable of enhancing a boolean field to \
>                 indicate whether the state object already exists
> -----------------------------------------------------------------------------------------------------------------------------------
>  
> Key: TAPESTRY-1368
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1368
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Fix For: 5.0.4
> 
> 
> Currently, you can use @ApplicationState to identify a field that can be used to \
> access an Application State Object: @ApplicationState
> private MyState _myState;
> However, there's no way to determine if the state object already exists; checking \
> it  (_myState != null) will force the object (and, perhaps, the session) into \
> existence.  A  kind of "heisenbug". What could be done is to look for a related \
> field of type boolean, with "Exists" appended (i.e., "_myStateExists").  This \
> boolean flag could be enhanced to check to see if the related ASO exists or not, \
> without creating it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]