I see it as simplification rather than a restriction.
I guess I don't normally store application state in a bunch of
separate strings; rather, I always store state in one or more POJO's,
exactly analogous to the Pricing object. So, for me, less mess,
because I don't have to have a bunch of extra string properties in my
page, and less mess because I don't have to constantly refer to what
I called some variable on some other page.
Robert
On Mar 20, 2007, at 3/203:35 PM , Anjana Gopinath wrote:
Thanks Robert for responding.
I can do that, but was wondering why there is a restriction like this?
Anjana Gopinath
True North Technology
11465 John's Creek Parkway, Suite 300
Duluth, GA 30079
[EMAIL PROTECTED]
On Mar 20, 2007, at 4:29 PM, Robert Zeigler wrote:
Correct.
Why not create, say, a "Pricing" object with "enterprisePrice" and
"clientPrice" properties?
Then you could do:
@ApplicationState
private Pricing _pricing;
Then you have one less injection to do/page that requires pricing
information. :)
Robert
On Mar 20, 2007, at 3/203:26 PM , Anjana Gopinath wrote:
Hi
I am trying to use few ASO's so share data across the pages. I
have declared the following, but looks like if one gets a value,
the second varaible also gets the same value. Is it not possible
to define different ASO's of same type?
@ApplicationState
private String enterprisePrice;
@ApplicationState
private String clientPrice;
i saw this in the T5 website
"Any other component or page that declares a field of the same
type, regardless of name, and marks it with the ApplicationState
annotation will share the same value. " . So is it not possible
to have two different ASO's os same type?
Thanks!
Anjana Gopinath
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
