Multiple config files is one good reason to have the display-name and
description. Just like Javadoc comments there is no reason for Struts to
care about them. For Struts, the change amounts to nothing more than the
modification of the dtd. Currently it seems like the description field is
rather forgotten. It is not used in the examples I have seen, and Struts
Console doesn't support it. It is better if descriptions are handled this
way rather than being inserted as comments.

Jonas

> -----Original Message-----
> From: Steve Raeburn [mailto:[EMAIL PROTECTED]
> Sent: den 5 augusti 2003 03:47
> To: Struts Developers List
> Subject: RE: struts-config and xslt
>
>
> >>While messing with the struts-config_1_1.dtd, I was surprised
> not to find
> a
> >>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).
>
> Would this still be meaningful? I think description probably would but I'm
> not sure about display-name.
>
> 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,
> > >
> > >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
> > others can do it
> > >better, but given that it is rather easy to create an xslt, I
> > think it would
> > >be a good idea to include one in Struts. Not only does it make
> > the file more
> > >readable 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
> > not to find a
> > >way to name and describe the whole application. Specifically, I
> > would 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
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > -----
> > Rob Leland (703-525-3580)
> >
> >
> > Choose a job you love, and you will never have to work a day of
> your life.
> >
> >                     -Confucius.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to