newton.dave wrote: > > --- On Mon, 12/15/08, Marsman <mars....@gmx.de> wrote: >> How can I solve this problem? Do I really have to code a >> second file like AddCustomerForm.properties with the same >> properties as in AddCustomer.property? > > There are several solutions; the easiest is to create a > "package.properties" file in the appropriate package and put common > message resources there. You can also create an action class hierarchy and > create properties files for the superclasses, but it doesn't make much > sense to do that unless you really need an action class hierarchy. >
Using the package.properties or a super class is that what I've thought about before posting here. But in package.properties I store localizations for all actions in the corresponding package. Not only for AddCustomer. And using a super class seems to me only like a workaround for the specified problem. Any other ideas? Titus -- View this message in context: http://www.nabble.com/Message-properties-on-actions-level-tp21012612p21020185.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
