Michael Westbay wrote: > Vaala-san wrote: > > > I would like to further propose on this idea - create a > > MessageResourcesInterface that various implementations can be created for. Four > > standard implementations could ship with struts: XML, Properties, and database. > > I could see that some people may find it easier, or more practical to store > > their messages in a database. > > This is the best idea I've heard so far. And I believe I read that the > factory pattern was one of McClanahan-san's favorites? > Yep :-). Its a good idea. Craig > > -- > Michael Westbay > Work: Beacon-IT http://www.beacon-it.co.jp/ > Home: http://www.seaple.icc.ne.jp/~westbay > Commentary: http://www.japanesebaseball.com/
- Re: Proposed Solution to Non-Serializable Message... Laird Nelson
- Re: Proposed Solution to Non-Serializable MessageResou... Rousseau, John
- Re: Proposed Solution to Non-Serializable MessageResou... Louis Tribble
- Re: Proposed Solution to Non-Serializable MessageResou... Pierre M�tras
- Re: Proposed Solution to Non-Serializable Message... Craig R. McClanahan
- Re: Proposed Solution to Non-Serializable Mes... Greg Murray
- Re: Proposed Solution to Non-Serializable Mes... Pierre M�tras
- Re: Proposed Solution to Non-Serializable... Michael Westbay
- Re: Proposed Solution to Non-Serializable Mes... Evan Vaala
- Re: Proposed Solution to Non-Serializable... Michael Westbay
- Re[2]: Proposed Solution to Non-Seria... Craig R. McClanahan
- Re[2]: Proposed Solution to Non-Serializa... Oleg V Alexeev
- Re: Proposed Solution to Non-Serializable MessageResou... Pierre M�tras
- Re: Proposed Solution to Non-Serializable Message... Laird Nelson
- Re: Proposed Solution to Non-Serializable MessageResou... Wong Kok Wai

