PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 24, 2003 3:05 PM
Subject: Re: [JBoss-user] OT: Data Internationalisation Best Practice
> Maybe you could do something like this:
>
> ++
> | product|
> +-
(Sending this again as my first reply somehow didn't appear to make it...)
Maybe you could do something like this:
++
| product|
++
| product_key number pk |
| name_i18n_id number|
| desc_i18n_id number
ey" <[EMAIL PROTECTED]>
Sent: Monday, March 24, 2003 3:17 PM
Subject: Re: [JBoss-user] OT: Data Internationalisation Best Practice
> I don't mind, please, I don't feel there's anything really proprietary
> in there. The trick is to ensure that the many-to-many relatio
hi,
At 13:30 24.03.2003 +, Brian McSweeney wrote:
Hi all,
Strategy 2)
Remove all the locale specific information from database and try
to hold it in resource bundles.
Advantage - can add new language with same database structure,
no new code.
Disadvantage - coupling the primary keys of databa
Maybe you could do something like this:
++
| product|
++
| product_key number pk |
| name_i18n_id number|
| desc_i18n_id number|
++
| sequence: product_key |
+-
Hi all,
This is way off JBoss as a topic, but because of
the expertise in
developing J2EE apps and because the xpetstore
applicaiton shows
off using JBoss as a J2EE server I thought I'd ask
this design
question here anyway. Hope that's okay.
we are looking at internationalising the
x
