struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Barrows" <jbarr...@sssc.com>
Subject RE: message resources in db
Date Wed, 29 Dec 2004 19:21:28 GMT


> -----Original Message-----
> From: James Mitchell [mailto:jmitchell@apache.org]
> Sent: Wednesday, December 29, 2004 11:18 AM
> To: Struts Users Mailing List
> Subject: Re: message resources in db
> 
> 
> My reasoning for what I've done is:
> a) it scratches my own itch
> b) it scratches many other peoples itch
> 
> My work did not stop with OJBMessageResources.  I have several 
> Database-based Impls of commons-resources sitting on sf.net 
> that are ready 
> for release as soon as common-resources goes 1.0.
> 
> When you use a Hibernate backed impl, you get many added benfits (see 
> Hibernate docs for details).
> 
> Besides all that.....if this doesn't scratch an itch for you, 
> don't knock 
> it.

I wasn't trying to knock it... I'm just trying to see the benefit of doing this.



> 
> 
> --
> James Mitchell
> Software Engineer / Open Source Evangelist
> EdgeTech, Inc.
> 678.910.8017
> AIM: jmitchtx
> 
> ----- Original Message ----- 
> From: "Jim Barrows" <jbarrows@sssc.com>
> To: "Struts Users Mailing List" <user@struts.apache.org>
> Sent: Wednesday, December 29, 2004 11:15 AM
> Subject: RE: message resources in db
> 
> 
> > -----Original Message-----
> > From: Nathan Coast [mailto:nathan@codeczar.com]
> > Sent: Wednesday, December 29, 2004 4:17 AM
> > To: Struts Users Mailing List
> > Subject: message resources in db
> >
> >
> > Hi,
> >
> > Has anyone developed message resources that pulls messages
> > from a db? I
> > have followed a few links that discuss this but can't find any code:
> >
> > http://wiki.apache.org/struts/StrutsMessageResourcesFromDatabase
> 
> This notion keeps popping up, and I keep wondering why.  On 
> the surface it 
> seems okay, keep everything where it's easy to maintain... 
> but in reality, 
> you really don't buy anything with it.
> If you do it so you can dynamically change the values, then 
> you slow down 
> your page throughput quite painfully.  So, of course you 
> cache the data... 
> which means it's not dynamic and you either provide a way to 
> flush the cache 
> (which you could do for a flat file as well, as Spring has 
> apparently done).
> Then you have the apparent fact that by doing so you are now 
> outside the 
> Java provided i18n stuff, so you might be in a position of trying to 
> maintain this code to keep up with what Java provides for you 
> autmatically.
> So, you gain what?  it's in a database?
> I'm curios as to what you're reasoning is to put these into a 
> database, coz 
> I'm looking for a good excuse to do it myself :)
> 
> 
> >
> > these docs mention
> > org.apache.struts.util.OJBMessageResourcesFactory but
> > I can't find this class anywhere.
> >
> > If there is a db implementation for message resources? I guess the
> > natural progression is a web-app gui for managing those
> > resources.  Does
> > such a thing exist?
> >
> > cheers
> > Nathan
> > -- 
> > Nathan Coast
> > Managing Director
> > Codeczar Ltd
> > mob : (852) 9049 5581
> > tel : (852) 2834 8733
> > fax : (852) 2834 8755
> > web : http://www.codeczar.com
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Mime
View raw message