Yes, that pretty much describes it. A key point is that the number of
languages is variable.

After reading through the pattern that Stuart recommended i look at, i'm
thinking about using a Facade or Manager, passing in a list of active
languages, have the manager function as a factory to instantiate the primary
and secondary objects needed and the DAO's, and take it from there.

I think i just need to stand in front of a white board and walk through it
conceptually a few times and see what i come up with. I remember looking at
an example that Hal posted somewhere, i think it involved a car and an
engine or something like that, :) but i have no idea where it might be, or
if it would be relevant in a case where you don't know in advance how many
secondary objects are needed. (I'm avoiding using the terms parent and child
to not confuse composition and inheritance in the terminology, but not too
skillfully, i'm afraid).

The other option would be to pass the list of active languages into the
primary object, and perhaps let the primary object function as the factory
that instantiates the secondary objects, but then the cohesiveness of the
primary object begins to break down. Maybe the secondary objects could be
instantiated outside the primary and passed in, maybe within an array? Then
what? Pass that all into a DAO, into both DAO's? Sounds like a dead end, but
who knows.

I'm a little lost, but wandering around, seeing if i can find a way out.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Patrick McElhaney
Sent: Thursday, January 20, 2005 2:39 PM
To: [email protected]
Subject: Re: [CFCDev] Multiple BO / DAO scenario


On Thu, 20 Jan 2005 10:24:10 +0100, Nando <[EMAIL PROTECTED]> wrote:

> Speaking of interesting ... i have just such a scenario i'm looking for
> options on. Design-wise what is clear at this point is that i have a
primary
> BO that handles some properties, and a variable number of secondary BO's
> that handle language specific properties, depending on what languages are
> enabled in the app. Editing / updating is handled via a single form, so it
> all needs to hang together.

Can you share some more specifics? I'm imagining something like a
product with a name description and price. The name and description
need to be stored in a few different languages, but the price
obvioulsy doesn't. Is that the basic idea?

Patrick


--
Patrick McElhaney
704.560.9117
http://pmcelhaney.blogspot.com
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).

An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]



----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' 
in the message of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]

Reply via email to