[ https://issues.apache.org/jira/browse/WICKET-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Colman updated WICKET-4829: --------------------------------- Summary: ComponentResolvers created in app init ignore non standard namespace (was: Page fails if non default namespace is specified and href has relative path) > ComponentResolvers created in app init ignore non standard 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 tag. This works fine in 1.4.x and 1.5.x > > 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: > > 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