in the view.
-john
-Original Message-
From: Arron Bates [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 04, 2002 11:17 PM
To: Struts Users Mailing List
Subject: Re: Nesting Extension and persistance strategy
Well, yeah. That'd do the trick too. Probably in a fashion that would be
manageable
Well, yeah. That'd do the trick too. Probably in a fashion that would be
manageable, clean, and garner the respect of OO gurus, developers and
peers alike. Very apt solution.
You can notify the observer from inside your setters rather than query
the submit button. Mainly because you will have
I like beans managing dirty state becuause I could possibly have one method
that can handle several different structures if it's designed right.
Maybe this:
Have all DataBeans implement an interface lets day DirtyInterface that
defines
2 methods:
public String getDirtyAttribute() and
public
John Menke wrote:
I am planning to use the Nesting Extension...
sweet :)
The MonkeyStruts example uses one ActionForm bean on the outermost level
that links to other beans recursively in a parent child heirarchy. It looks
like each child bean in the hierarchy is instantiated from methods
I don't see any reason as to why the nested tags wouldn't work with
simper.
Then I will try to get them working together (simper -- NeXt), Having a
problem downloading
the simper-src.jar from SourceForge download always fininshes but winzip
complains
that archive is missing bytes...
At the
- Original Message -
From: Arron Bates [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Monday, March 04, 2002 11:16 PM
Subject: Re: Nesting Extension and persistance strategy
I like beans managing dirty state becuause I could possibly have one
method
Mailing List
Subject: Re: Nesting Extension and persistance strategy--castor any one?
Hi All,
I am not the expert in the field of designing OO persistence mechanisms.
I am a fan of nested beans and also i have been playing with castor lately.
So am thinking if we can map our monkey object
I am planning to use the Nesting Extension in my application and would like
to field comments on how to best implement a database persistance mechanism
in this framework.
The MonkeyStruts example uses one ActionForm bean on the outermost level
that links to other beans recursively in a parent
John Menke wrote:
I am planning to use the Nesting Extension...
sweet :)
The MonkeyStruts example uses one ActionForm bean on the outermost level
that links to other beans recursively in a parent child heirarchy. It
looks
like each child bean in the hierarchy is instantiated from
you could drive it exactly as you've described having the beans manage
their dirty state and have a one-to-one level mapping from the
persistence mechanism to nested bean (ie: have each nested bean know how
it's to be stored). There are various ways to take this back to the MVC
paradigm keeping
Aaron,
what do you think of implementing the Observable interface with the
DataBeans? This could help with detecting updates. (Inserts and Deletes
are easier because you can determine the action via querying the submit
button).
-john
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For
Well, yeah. That'd do the trick too. Probably in a fashion that would be
manageable, clean, and garner the respect of OO gurus, developers and
peers alike. Very apt solution.
You can notify the observer from inside your setters rather than query
the submit button. Mainly because you will have
I like beans managing dirty state becuause I could possibly have one
method
that can handle several different structures if it's designed right.
Maybe this:
Have all DataBeans implement an interface lets day DirtyInterface that
defines
2 methods:
public String getDirtyAttribute()
I don't think what you guys are discussing, is too far off from the
Simper framework I've developed:
http://www.netmeme.org/simper/
It doesn't have anything to do with the current Nesting library, but, it
does many of the things you've discussed in this thread, including
automatic change
the dynamic beans
work with Nesting.
-john
-Original Message-
From: Bryan Field-Elliot [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 04, 2002 11:36 PM
To: Struts Users Mailing List
Subject: Re: Nesting Extension and persistance strategy
I don't think what you guys are discussing, is too far off
]]
Sent: Monday, March 04, 2002 11:17 PM
To: Struts Users Mailing List
Subject: Re: Nesting Extension and persistance strategy
Well, yeah. That'd do the trick too. Probably in a fashion that would be
manageable, clean, and garner the respect of OO gurus, developers and
peers alike. Very apt
. Dynamic persistance and great flexibility in the view.
-john
-Original Message-
From: Arron Bates [ mailto:[EMAIL PROTECTED] ]
Sent: Monday, March 04, 2002 11:17 PM
To: Struts Users Mailing List
Subject: Re: Nesting Extension and persistance strategy
Well, yeah. That'd do
17 matches
Mail list logo
