You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ma...@McAfee.com on 2014/02/20 08:46:04 UTC
Can jasper2's "validateXml" be added back, at least for the
lifetime of Tomcat 7?
Hi everyone,
My project recently tried upgrading to Tomcat 7.0.52 and has become bit by the renaming of jasper2’s “validateXml” to “validateTld”, as described on the thread below. This change has made it more difficult pick up the latest Tomcat 7’s security fixes since the change breaks build scripts for quite a few projects maintained by different teams.
Would it be possible to add back support for “validateXml” as part of the next minor release of Tomcat 7, as more or less described by Mark Thomas on that thread?
http://mail-archives.apache.org/mod_mbox/tomcat-users/201401.mbox/%3Ccd84922d-b159-49bd-9c11-6aaa5cb973da@email.android.com%3E
This would save us a lot of effort, and we would then plan on switching to the new attribute name as part of adopting Tomcat 8.
Thank you for any assistance on this!
Sincerely,
Mark DeSpain
Re: Can jasper2's "validateXml" be added back, at least for the
lifetime of Tomcat 7?
Posted by Ma...@McAfee.com.
Got it. Much appreciated!
On 2/21/14, 1:11 AM, "Mark Thomas" <ma...@apache.org> wrote:
>On 21/02/2014 01:44, Mark_DeSpain@McAfee.com wrote:
>> Thank you for the quick reply, Mark. Would it be possible to get a
>>sense
>> of which release the validateXml attribute might get added back? E.g.
>> 7.0.53?
>
>It will be 7.0.53. See:
>http://svn.us.apache.org/repos/asf/tomcat/tc7.0.x/trunk/webapps/docs/chang
>elog.xml
>
>> I did a quick search through the bugs, but it does not seem to be
>>tracked.
>> Would it be worth submitting something?
>
>To be perfectly honest, no. The problem is already fixed. The Tomcat
>developers don't create a bug report for every issue. We tend to use
>Bugzilla as a list of things still to fix so if someone reports a bug we
>know we aren't going to fix straight away, we'll ask them to create a
>Bugzilla entry for it so it doesn't get lost. In this case all that
>would happen is that you'd create it and I'd immediately close it as
>fixed.
>
>Mark
>
>
>>
>> Thanks!
>>
>> Mark D.
>>
>>
>>
>>
>> On 2/20/14, 12:21 AM, "Mark Thomas" <ma...@apache.org> wrote:
>>
>>> On 20/02/2014 07:46, Mark_DeSpain@McAfee.com wrote:
>>>> Hi everyone,
>>>>
>>>> My project recently tried upgrading to Tomcat 7.0.52 and has become
>>>> bit by the renaming of jasper2¹s ³validateXml² to ³validateTld², as
>>>> described on the thread below. This change has made it more
>>>> difficult pick up the latest Tomcat 7¹s security fixes since the
>>>> change breaks build scripts for quite a few projects maintained by
>>>> different teams.
>>>>
>>>> Would it be possible to add back support for ³validateXml² as part of
>>>> the next minor release of Tomcat 7, as more or less described by Mark
>>>> Thomas on that thread?
>>>>
>>>>
>>>>
>>>>http://mail-archives.apache.org/mod_mbox/tomcat-users/201401.mbox/%3Ccd
>>>>84
>>>> 922d-b159-49bd-9c11-6aaa5cb973da@email.android.com%3E
>>>>
>>>> This would save us a lot of effort, and we would then plan on
>>>> switching to the new attribute name as part of adopting Tomcat 8.
>>>>
>>>> Thank you for any assistance on this!
>>>
>>> It looks like that attribute was going to get added back already as,
>>> digging into another issue reported on the dev list, Jasper in 7.0.x
>>> still parses web.xml in full so it needs to have separate control over
>>> validateXml.
>>>
>>> Mark
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: Can jasper2's "validateXml" be added back, at least for the lifetime
of Tomcat 7?
Posted by Mark Thomas <ma...@apache.org>.
On 21/02/2014 01:44, Mark_DeSpain@McAfee.com wrote:
> Thank you for the quick reply, Mark. Would it be possible to get a sense
> of which release the validateXml attribute might get added back? E.g.
> 7.0.53?
It will be 7.0.53. See:
http://svn.us.apache.org/repos/asf/tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
> I did a quick search through the bugs, but it does not seem to be tracked.
> Would it be worth submitting something?
To be perfectly honest, no. The problem is already fixed. The Tomcat
developers don't create a bug report for every issue. We tend to use
Bugzilla as a list of things still to fix so if someone reports a bug we
know we aren't going to fix straight away, we'll ask them to create a
Bugzilla entry for it so it doesn't get lost. In this case all that
would happen is that you'd create it and I'd immediately close it as fixed.
Mark
>
> Thanks!
>
> Mark D.
>
>
>
>
> On 2/20/14, 12:21 AM, "Mark Thomas" <ma...@apache.org> wrote:
>
>> On 20/02/2014 07:46, Mark_DeSpain@McAfee.com wrote:
>>> Hi everyone,
>>>
>>> My project recently tried upgrading to Tomcat 7.0.52 and has become
>>> bit by the renaming of jasper2¹s ³validateXml² to ³validateTld², as
>>> described on the thread below. This change has made it more
>>> difficult pick up the latest Tomcat 7¹s security fixes since the
>>> change breaks build scripts for quite a few projects maintained by
>>> different teams.
>>>
>>> Would it be possible to add back support for ³validateXml² as part of
>>> the next minor release of Tomcat 7, as more or less described by Mark
>>> Thomas on that thread?
>>>
>>>
>>> http://mail-archives.apache.org/mod_mbox/tomcat-users/201401.mbox/%3Ccd84
>>> 922d-b159-49bd-9c11-6aaa5cb973da@email.android.com%3E
>>>
>>> This would save us a lot of effort, and we would then plan on
>>> switching to the new attribute name as part of adopting Tomcat 8.
>>>
>>> Thank you for any assistance on this!
>>
>> It looks like that attribute was going to get added back already as,
>> digging into another issue reported on the dev list, Jasper in 7.0.x
>> still parses web.xml in full so it needs to have separate control over
>> validateXml.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Can jasper2's "validateXml" be added back, at least for the
lifetime of Tomcat 7?
Posted by Ma...@McAfee.com.
Thank you for the quick reply, Mark. Would it be possible to get a sense
of which release the validateXml attribute might get added back? E.g.
7.0.53?
I did a quick search through the bugs, but it does not seem to be tracked.
Would it be worth submitting something?
Thanks!
Mark D.
On 2/20/14, 12:21 AM, "Mark Thomas" <ma...@apache.org> wrote:
>On 20/02/2014 07:46, Mark_DeSpain@McAfee.com wrote:
>> Hi everyone,
>>
>> My project recently tried upgrading to Tomcat 7.0.52 and has become
>> bit by the renaming of jasper2¹s ³validateXml² to ³validateTld², as
>> described on the thread below. This change has made it more
>> difficult pick up the latest Tomcat 7¹s security fixes since the
>> change breaks build scripts for quite a few projects maintained by
>> different teams.
>>
>> Would it be possible to add back support for ³validateXml² as part of
>> the next minor release of Tomcat 7, as more or less described by Mark
>> Thomas on that thread?
>>
>>
>>http://mail-archives.apache.org/mod_mbox/tomcat-users/201401.mbox/%3Ccd84
>>922d-b159-49bd-9c11-6aaa5cb973da@email.android.com%3E
>>
>> This would save us a lot of effort, and we would then plan on
>> switching to the new attribute name as part of adopting Tomcat 8.
>>
>> Thank you for any assistance on this!
>
>It looks like that attribute was going to get added back already as,
>digging into another issue reported on the dev list, Jasper in 7.0.x
>still parses web.xml in full so it needs to have separate control over
>validateXml.
>
>Mark
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Can jasper2's "validateXml" be added back, at least for the lifetime
of Tomcat 7?
Posted by Mark Thomas <ma...@apache.org>.
On 20/02/2014 07:46, Mark_DeSpain@McAfee.com wrote:
> Hi everyone,
>
> My project recently tried upgrading to Tomcat 7.0.52 and has become
> bit by the renaming of jasper2’s “validateXml” to “validateTld”, as
> described on the thread below. This change has made it more
> difficult pick up the latest Tomcat 7’s security fixes since the
> change breaks build scripts for quite a few projects maintained by
> different teams.
>
> Would it be possible to add back support for “validateXml” as part of
> the next minor release of Tomcat 7, as more or less described by Mark
> Thomas on that thread?
>
> http://mail-archives.apache.org/mod_mbox/tomcat-users/201401.mbox/%3Ccd84922d-b159-49bd-9c11-6aaa5cb973da@email.android.com%3E
>
> This would save us a lot of effort, and we would then plan on
> switching to the new attribute name as part of adopting Tomcat 8.
>
> Thank you for any assistance on this!
It looks like that attribute was going to get added back already as,
digging into another issue reported on the dev list, Jasper in 7.0.x
still parses web.xml in full so it needs to have separate control over
validateXml.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org