If you dont want to use an original object why not just clone/create a
copy of the original end use that and then copy the values over again?
(i think beanutils or something van do that for you)
On 11/18/08, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Hi
Im trying todo a
True, this is also what I am thinking about doing...
Johan Compagner wrote:
If you dont want to use an original object why not just clone/create a
copy of the original end use that and then copy the values over again?
(i think beanutils or something van do that for you)
On 11/18/08, Nino
Ok great.. Seems like SerializationHelper.clone and just a normal
compound model could work..
Francisco Diaz Trepat - gmail wrote:
Don't know, but LOL.
This might be an instancing issue in which special handling is good for this
scenario but seems to be fine for most cases. And in a lazy TDD
why?
simple is good. doesn't need to be complex.
what part you dislike the most?
f(t)
On Thu, Nov 20, 2008 at 2:29 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
BTW this is a flawed approch.. We need something a little more
intelligent.. I'll return on the subject..
I love simple and simple is good. But this approach has issues with
hibernate if your hibernate sessions are per request and your
shadowmodel lives in multiple requests and your entities has references
to other entities for example 1..* etc ... In simple use cases, and
possibly also when not
Don't know, but LOL.
This might be an instancing issue in which special handling is good for this
scenario but seems to be fine for most cases. And in a lazy TDD programming
way it might be good enough.
Although I know from blog and other threads that you look for greatness :-)
and not just code
BTW this is a flawed approch.. We need something a little more
intelligent.. I'll return on the subject..
Nino Saturnino Martinez Vazquez Wael wrote:
heres the raw and completely untested version of it. probably with a
whole bunch of issues...:
package zeuzgroup.web.model;
import
Hi
Im trying todo a compoundpropertymodel which does not change original
values in the original model. I need this since I am updating some
stuff in a wizard but I first want to commit when the user confirms in
the end of the wizard, and if the model are changed directly the
transaction are
Nice, I was up to something similar.
On Tue, Nov 18, 2008 at 9:43 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Hi
Im trying todo a compoundpropertymodel which does not change original
values in the original model. I need this since I am updating some stuff
in a wizard
I do.. But if I use it with a detachable model the idea goes a bit
away.. Plus I'd like it to be a bit more transparent... Could be me that
just not know enough
James Carman wrote:
You didn't like the ProxyModelManager?
heres the raw and completely untested version of it. probably with a
whole bunch of issues...:
package zeuzgroup.web.model;
import java.lang.reflect.Field;
import java.util.HashMap;
import java.util.Map;
import java.util.Map.Entry;
import org.apache.wicket.Component;
You could adapt the proxy model thing (I kind of like the name
shadow and I might change mine) to do what you want. You'd need to
keep a flag that tells whether or not you've retrieved the value from
the destination model.
On Tue, Nov 18, 2008 at 9:33 AM, Nino Saturnino Martinez Vazquez Wael
Shadows sounds good... :-)f(t)
On Tue, Nov 18, 2008 at 11:37 AM, James Carman
[EMAIL PROTECTED]wrote:
You could adapt the proxy model thing (I kind of like the name
shadow and I might change mine) to do what you want. You'd need to
keep a flag that tells whether or not you've retrieved the
[+] on proposition shadow
On Tue, Nov 18, 2008 at 4:16 PM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
And heres the result in all its glory, should I create jira issue and
attach the code?.. :
package zeuzgroup.web.model;
import java.lang.reflect.Field;
import
14 matches
Mail list logo
