Doh. Time for a forward from gmail to the work account for any svn
commits with the branch name in the subject :)

I don't think you missed anything, thanks for the info.

Hen

On 3/1/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> I removed the "cancellable" attribute and replaced them with <set-property>
> in the exercise module of the examples webapp in the Struts 1.2.x branch
> recently:
>
> http://svn.apache.org/viewcvs.cgi?rev=379693&view=rev
>
> Was there somewhere else I missed?
>
> We are not planning to add "cancellable" to the 1.2 dtd - so using
> <set-property> for this attribute is the way to go.
>
> Niall
>
> ----- Original Message -----
> From: "Henri Yandell" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 01, 2006 12:57 AM
>
>
> The recent CANCEL bugfix saw a change to the struts-config.xml: a
> cancellable property was added. When this is used as <action
> cancellable="true"... >, you get errors (though they're really
> warnings) from the DTD verification in Digester:
>
> ***********
> Feb 28, 2006 4:27:59 PM org.apache.commons.digester.Digester error
> SEVERE: Parse Error at line 35 column 39: Attribute "cancellable" must
> be declared for element type "action".
> org.xml.sax.SAXParseException: Attribute "cancellable" must be
> declared for element type "action".
> ***********
>
> This is because the dtd of the exercise/struts-config.xml document is:
>
> "http://struts.apache.org/dtds/struts-config_1_2.dtd";
>
> (The validator/struts-config.xml is fine as it uses set-property).
>
> As part of my job to support legacy versions of Struts,  I'm preparing
> a 1.2.7-2 release for our customers, so a) wanted to mention that this
> will be a problem with the forthcoming 1.2.9 Struts release and b)
> wanted to ask if anyone has any thoughts on how that is typically
> solved.
>
> Does the 1_2 dtd just get updated with the new bit? Is it something
> that users should just ignore until they get to 1.3?
>
> Currently I'll just be recommending the set-property approach :)
>
> Hen
>
>
>
> ---------------------------------------------------------------------
> 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