You're right it would be module level information. My thought is that while not read or used by strutsaWhile messing with the struts-config_1_1.dtd, I was surprised not to find
way to name and describe the whole application.
As you can have multiple config files for each module, display-name and description could really only describe the contents of each file rather than describing the application or module. (web.xml already has this info at application level).
it keeps a useful summary description with the struts-config.xml that could then be digested/processed by
some other tool like maven when generating documentation.
I was assuming display-name was the same as saying 'a short 1 to 5' word descriptive phrase.
Would this still be meaningful? I think description probably would but I'm not sure about display-name.
It certainly couldn't/shouldn't be the module name.
-Rob
Steve
-----Original Message----- From: Rob Leland [mailto:[EMAIL PROTECTED] Sent: August 4, 2003 6:26 PM To: Struts Developers List Subject: Re: struts-config and xslt
Jonas Björnerstedt wrote:
Hello,others can do it
Having to evaluate an xml editor (I won't say which), I decided to use struts-config.xml as an example. After some hours wrestling with the program, this is the result I got:
http://bjornerstedt.org/struts-config.html
It is the config file from the struts-example application. It was created using:
http://bjornerstedt.org/struts-config_1_1.xslt
It's not that pretty (especially not in Mozilla). I am sure
better, but given that it is rather easy to create an xslt, Ithink it would
be a good idea to include one in Struts. Not only does it makethe file more
not to find areadable for large applications, it can also be used to make the xml - editor a decent Struts editor.
While messing with the struts-config_1_1.dtd, I was surprised
way to name and describe the whole application. Specifically, Iwould like
to see display-name and description added to the struts-config element in the dtd:
<!ELEMENT struts-config (display-name?, description?, data-sources?, form-beans?, global-exceptions?, global-forwards?, action-mappings?, controller?, message-resources*, plug-in*)>
This seems reasonable, if no others object I'll change the dtd to add this info. However, I see no reason for struts itself to read in this information. If you want this info in your application you can use the resource files.
instead of:
<!ELEMENT struts-config (data-sources?, form-beans?, global-exceptions?, global-forwards?, action-mappings?, controller?, message-resources*, plug-in*)>
Descriptions should be available at all levels.
Jonas
----- Rob Leland (703-525-3580)
Choose a job you love, and you will never have to work a day of your life. -Confucius.