Chris Colman created WICKET-4829:
------------------------------------
Summary: Enclosures fail unless standard 'wicket' namespace is used
Key: WICKET-4829
URL: https://issues.apache.org/jira/browse/WICKET-4829
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 6.2.0
Environment: Windows, Java 6.x
Reporter: Chris Colman
We have a panel with an enclosure that worked fine in 1.5 but now fails in 6.0
The page uses a non standard namespace: i.e. instead of using <wicket: ...>
everywhere it uses, for example <mynamespace: ... > and so we add
xmlns:mynamespace to the html element to declare the non standard namespace -
this has worked fine in 1.4.x and 1.5.x for years but after migrating to 6.2.0
it no longer works failing with the following error:
Last cause: Unable to find component with id
'mynamespace_relative_path_prefix_' in [TransparentWebMarkupContainer
[Component id = mynamespace_extend4]]
Expected:
'body:myapp_child3:mynamespace_extend4.mynamespace_relative_path_prefix_'.
Found with similar names: ''
If we remove the non standard namespace declaration from the html element and
rename all the mynamespace: tags to wicket: then the enclosure works fine - in
other words the enclosure mechanism works but only if the 'wicket' namespace is
used everywhere.
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
