[
https://issues.apache.org/jira/browse/WICKET-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484545#comment-13484545
]
Chris Colman edited comment on WICKET-4829 at 10/26/12 1:37 AM:
----------------------------------------------------------------
Do you think it would be possible to go ahead with the simple bug fix now and
look at the other idea as an improvement? If you could apply these small, safe
patches into the master then I can switch back to the master branch again and
then maybe we can look at the riskier move of changing the id composition later.
At the moment we want our app to go live soon with a 6.2 snapshot but without
the patches in the master we'd have to make a release based on our own branch
with the fix which isn't ideal.
was (Author: chrisc):
Do you think it would be possible to go ahead with the simple bug fix now
and look at the other idea as an improvement? If you could apply these small,
safe patches into the master then I can switch back to the master branch again
and then maybe we can look at the riskier move of changing the id composition
later.
At the moment we want our app to go live soon with a 6.2 snapshot but without
the patches in the master we'd have to make a release based on our own fixed
branch which is a bit scary ;)
> ComponentResolvers created in app init ignore markup's namespace
> ----------------------------------------------------------------
>
> 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
> Attachments: nonStdNamespaceBugW6.2.zip
>
>
> Initially this problem was occurring in a page with an enclosure and so I
> thought it was specific to enclosures but on minimalizing the quickstart it
> is apparent that it happens on any page where a non default namespace is
> specified AND a href has a relative path.
>
> The attached quickstart has a single page with no components at all. In 6.x
> the page fails if a non default namespace is specified in the <html> tag.
> This works fine in 1.4.x and 1.5.x
> <html xmls:foobar>
> causes:
> Last cause: Unable to find component with id 'foobar_relative_path_prefix_'
> in [HtmlHeaderContainer [Component id = _header_0]]
> Expected: '_header_0.foobar_relative_path_prefix_'.
> Found with similar names: ''
> If we remove the non standard namespace declaration from the html element
> then the page works fine.
> Also, if we remove the line:
> <link rel="stylesheet" href="style.css" type="text/css" media="screen"
> title="Stylesheet"/>
> from the HomePage.html then the problem doesn't occur.
> Problem could possibly be related to how RelativePathPrefixHanlder deals with
> a non default namespace.
--
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
