This bug seems to be a much more fundamental regression. It seems any
page that specifies its own namespace fails - regardless of whether it
has an enclosure or not.
JIRA issue raised and QuickStart provided here:
https://issues.apache.org/jira/browse/WICKET-4829
Regards,
Chris
>-----Original Message-----
>From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
>Sent: Sunday, 21 October 2012 2:38 AM
>To: users@wicket.apache.org
>Subject: Regression when using <wicket:enclosure> with non wicket
namespace
>in 6.0
>
>We have a panel with an enclosure that worked fine in 1.5 but now fails
>in 6.0
>
>The page uses a non wicket namespace: i.e. instead of using <wicket:
...
>> everywhere it uses, for example <mynamespace: ... >
>and adds xmlns:mynamespace to the html tag to declare the non standard
>namespace.
>
>If we remove the namespace declaration from the html tag and rename all
>the mynamespace: tags to wicket: then the enclosure works fine.
>
>I remember a similar problem happened earlier in 1.5 that was caused by
>some Wicket code hardcoding the namespace to be 'wicket' instead of
>checking the namespace declared for each individual markup file. This
>problem was eventually fixed in 1.5. Here is a link to that issue:
>
>https://issues.apache.org/jira/browse/WICKET-4330
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
