--- On Mon, 12/15/08, Marsman <[email protected]> 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. (Does it really work with a file named *.property? I wouldn't have guessed that.) Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
