Dmitri:
I've just completed a project that had a rather large Object model in which
there were numerous String collections. My solution was to create a
StringArray object to manage them. This turned out to be the simplest way to
implement a List based solution, since all the management code moved into
the StringArray class. Adding a StringArray to class became a three - liner.
ex)
private StringArray _someList;
public void setSomeList(StringArray values) { _someList = values; }
public StringArray getSomeList() { return _someList; }
----- Original Message -----
From: "Dmitri Colebatch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 14, 2001 6:55 PM
Subject: Re: [castor-dev] vector, String[] or String...
| I would _definately_ go for option (1). a lot cleaner.
|
| my 2c
|
| cheesr
| dim
|
| On Mon, 15 Oct 2001, Keith Chew wrote:
|
| > Hi
| >
| > Simple question. If I have a an object and one of it's attributes is a
list
| > of string, should I:
| > (1) create a Vector of string objects
| > (2) create a String and comma delimit the items
| >
| > In terms of programming, (1) would be the easiest, but in terms of JDO,
I
| > suppose (2) is the easiet (just an extra column in the table). In (1),
we
| > need to create a new table and class.
| >
| > Which approach would you take? Or any other ideas would be welcome.
| >
| > Thanks
| > Keith C
| >
| > -----------------------------------------------------------
| > If you wish to unsubscribe from this mailing, send mail to
| > [EMAIL PROTECTED] with a subject of:
| > unsubscribe castor-dev
| >
| >
|
| -----------------------------------------------------------
| If you wish to unsubscribe from this mailing, send mail to
| [EMAIL PROTECTED] with a subject of:
| unsubscribe castor-dev
|
|
|
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
