Hmm, I really can't remember everything. Now one problem was that if
you save the objects to XML, you can't save all available attributes
for the instance. You have to filter and only save the attributes that
are part of the instance and not those of the coplet data.
An additional problem is removing of attributes etc. What do you do if
the attribute you want to remove is not an attribute of the instance?
Do you delegate it to the data object? And so on.
Now, rethinkink everything, perhaps the simplest solutions is to leave
everything as it is and only add a "get value from all attributes method",
which is just a getter method that first looks in the instance and then
in the coplet data object. But for setting and removing everything could
be left unchanged.
HTH
Carsten
________________________________
From: Ralph Goers [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 26, 2004 8:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Portal - coplet instance data attributes
What problems were you experiencing? I don't want to waste my time
if it won't work.
Ralph
Carsten Ziegeler wrote:
Now, the original idea was exactly to have this behaviour,
but
unfortunately we soon ran into problems with Castor
converting
the objects to XML. But apart from that I see no problems
with it.
(PS: if anyone has a better way for the conversion than
Castor
it would make me very happy).
Carsten
