Thank your reply! I only want more choices.I think wildcard style would be more easier in developing stage, and the current style would be more suitable in deploying stage.
On 3/20/07, Harring Figueiredo <[EMAIL PROTECTED]> wrote:
Even though I would like to have something like this for CLASSPATH in say, ant scripts, I would not want something like this in configuration file for 2 reasons: - Sercuty issues - When it comes to error messages, struts does not really provide good messages (I take that this is because the XML parser errors is not filtered and interpreted ). I would hate to have a member of the development team drop a .xml file in the config dir and break the deployment for "no" aparent reason. Harring On 3/20/07, joey <[EMAIL PROTECTED]> wrote: > > I think if struts.xml 's element 'include' support wildcard,it will be > better. > For example I have ten file to be included in struts.xml,now I have to > write > <include file="/config/struts-xxx.xml " /> ten times.But if it has > supported > wildcard, > I would only need write once like this <include file="/config/*.xml" />. > is it possible to support wildcard next version?I think I can deploy my > struts application > easier if so. > -- Sincerely, Harring Figueiredo Sr. Software Engineer Email: [EMAIL PROTECTED] Telephone: 941-256-0600 "We never become truly spiritual by sitting down and wishing to become so. You must undertake something so great that you cannot accomplish it unaided."
