On Tue, Oct 20, 2009 at 6:16 AM, Wes Wannemacher <[email protected]> wrote:
> Yes, you can copy the file... The files in 2.x might be overwritten,
> but I don't know if there is any pointers to 'dtds' anywhere.

I don't know what the situation is for S2, but that URL is *the*
definitive reference to the DTDs for S1. It is used when parsing the
XML. When everything is set up properly, the DTD should not be
downloaded from that URL, but a local copy (in the jar) should be
referenced by means of that URL. If something is trying to access the
file at the URL directly, then there may be a configuration problem.
(Regardless, the DTDs should still exist at that URL, so if they
don't, that's another problem.)

--
Martin Cooper


> -Wes
>
> On Tue, Oct 20, 2009 at 1:58 AM, Lukasz Lenart
> <[email protected]> wrote:
>> Can I copy the file? As I recall, Wes mentioned that all files will be
>> erased during a new release from that location.
>>
>> https://issues.apache.org/struts/browse/WW-3279
>>
>>
>> Regards
>> --
>> Lukasz
>>
>> 2009/10/1 Lukasz Lenart <[email protected]>:
>>> 2009/10/1 E Au <[email protected]>:
>>>> I just migrated my struts 2.1.6 webapp to 2.1.8. My webapp failed to load 
>>>> because
>>>> it couldn't read struts-default.xml which is using 
>>>> http://struts.apache.org/dtds/struts-2.1.7.dtd.
>>>> The dtd is not currently available in that url.
>>>
>>> Please fill Jira ticket for that, I will upload it than!
>>> https://issues.apache.org/struts/browse/WW
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
>
> --
> Wes Wannemacher
>
> Head Engineer, WanTii, Inc.
> Need Training? Struts, Spring, Maven, Tomcat...
> Ask me for a quote!
>
> ---------------------------------------------------------------------
> 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