You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Wendy Smoak <ja...@wendysmoak.com> on 2005/09/21 07:50:12 UTC
DTDs on the website
Currently we have several DTDs available online:
http://struts.apache.org/dtds/
It looks like they are uploaded as needed, but not stored as part of the
site. The corresponding directory, site/xdocs/dtds has some files that are
(according to README.txt) left over from the Ant build:
http://svn.apache.org/viewcvs.cgi/struts/site/trunk/xdocs/dtds/?rev=290621
I'll remove those files in a day or so (unless someone objects). The
question I have is whether to check in the current set of DTDs and maintain
them as part of the website, or just leave it as-is.
Craig, can the dialog and clay DTDs be put on the website?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: DTDs on the website
Posted by Martin Cooper <mf...@gmail.com>.
On 9/21/05, Joe Germuska <Jo...@germuska.com> wrote:
>
> >(On the other hand, infra@ has been griping about the number of requests
> for
> >DTDs that hit the ASF servers. I don't know how we can debug where those
> are
> >coming from, though.)
>
> I bet they're coming from people using XML editing tools which do
> validation. I wonder what they leave in the logs as the user agent?
> Can the number really be great enough to be causing problems?
We're talking about well over 300,000 requests a day for Struts-related
files. About 13% of the requests coming in to the main web server are from
nameless Java clients, and much of that is for Struts-related files.
>IIRC, when Struts was in Jakarta-land, the DTD location wasn't underneath
> >the Struts web site, which is why the DTDs became dislocated from the
> site
> >itself. Now that we're our own bosses ;-) I think it would be fine to
> treat
> >the DTDs as part of the site.
>
> That could produce a maintenance headache, if we want to both publish
> the DTDs in "site" and include them in JARs. Perhaps some SVN
> trickery will help here? We want the URLs to be simple and stable,
> which may be at odds with some of the parameters of our automated
> build processes.
Good point. Instead of resorting to trickery here, then, perhaps we should
just leave things the way they are. I don't think there's a pressing reason
to include them in the site.
--
Martin Cooper
Joe
>
> --
> Joe Germuska
> Joe@Germuska.com
> http://blog.germuska.com
> "Narrow minds are weapons made for mass destruction" -The Ex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: DTDs on the website
Posted by Wendy Smoak <ja...@wendysmoak.com>.
From: "Joe Germuska" <Jo...@Germuska.com>
> I bet they're coming from people using XML editing tools which do
> validation.
Exactly. That's why I was working on the Shale DTDs last weekend-- JEdit
had been complaining about every single tag in any dialog or clay config
file I opened.
While I can write an XML catalog to tell it where to find the files locally,
I have a feeling most people rely on them being available at the public URL.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: DTDs on the website
Posted by Joe Germuska <Jo...@Germuska.com>.
>(On the other hand, infra@ has been griping about the number of requests for
>DTDs that hit the ASF servers. I don't know how we can debug where those are
>coming from, though.)
I bet they're coming from people using XML editing tools which do
validation. I wonder what they leave in the logs as the user agent?
Can the number really be great enough to be causing problems?
>IIRC, when Struts was in Jakarta-land, the DTD location wasn't underneath
>the Struts web site, which is why the DTDs became dislocated from the site
>itself. Now that we're our own bosses ;-) I think it would be fine to treat
>the DTDs as part of the site.
That could produce a maintenance headache, if we want to both publish
the DTDs in "site" and include them in JARs. Perhaps some SVN
trickery will help here? We want the URLs to be simple and stable,
which may be at odds with some of the parameters of our automated
build processes.
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: DTDs on the website
Posted by Martin Cooper <mf...@gmail.com>.
On 9/21/05, Craig McClanahan <cr...@apache.org> wrote:
>
> On 9/21/05, Martin Cooper <mf...@gmail.com> wrote:
> >
> > [snip]
> > (On the other hand, infra@ has been griping about the number of requests
> > for
> > DTDs that hit the ASF servers. I don't know how we can debug where those
> > are
> > coming from, though.)
>
>
> I'm wondering if some portion of those are coming from IDEs that are
> trying to parse config files? As you stated, Struts itself should always be
> finding its internal copies, presuming that the public ID has no typos in
> it.
>
Ah, yes, that's possible. In which case, I guess, there's nothing we can do
about it. ;-(
--
Martin Cooper
Craig
>
>
Re: DTDs on the website
Posted by Craig McClanahan <cr...@apache.org>.
On 9/21/05, Martin Cooper <mf...@gmail.com> wrote:
>
> [snip]
> (On the other hand, infra@ has been griping about the number of requests
> for
> DTDs that hit the ASF servers. I don't know how we can debug where those
> are
> coming from, though.)
I'm wondering if some portion of those are coming from IDEs that are trying
to parse config files? As you stated, Struts itself should always be finding
its internal copies, presuming that the public ID has no typos in it.
Craig
Re: DTDs on the website
Posted by Martin Cooper <mf...@gmail.com>.
On 9/20/05, Wendy Smoak <ja...@wendysmoak.com> wrote:
>
> Currently we have several DTDs available online:
> http://struts.apache.org/dtds/
Yes. The URLs to those are used in struts-config.xml, and used to download
the DTD if a local one is not found. With Struts, the local one should
*always* be found (or we have a bug!), but we should still have the DTDs
available there, just in case.
(On the other hand, infra@ has been griping about the number of requests for
DTDs that hit the ASF servers. I don't know how we can debug where those are
coming from, though.)
It looks like they are uploaded as needed, but not stored as part of the
> site. The corresponding directory, site/xdocs/dtds has some files that are
> (according to README.txt) left over from the Ant build:
> http://svn.apache.org/viewcvs.cgi/struts/site/trunk/xdocs/dtds/?rev=290621
>
> I'll remove those files in a day or so (unless someone objects). The
> question I have is whether to check in the current set of DTDs and
> maintain
> them as part of the website, or just leave it as-is.
IIRC, when Struts was in Jakarta-land, the DTD location wasn't underneath
the Struts web site, which is why the DTDs became dislocated from the site
itself. Now that we're our own bosses ;-) I think it would be fine to treat
the DTDs as part of the site.
--
Martin Cooper
Craig, can the dialog and clay DTDs be put on the website?
>
> --
> Wendy
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: DTDs on the website
Posted by Craig McClanahan <cr...@apache.org>.
On 9/20/05, Wendy Smoak <ja...@wendysmoak.com> wrote:
>
>
> Craig, can the dialog and clay DTDs be put on the website?
Done.
--
> Wendy
Craig