You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2009/12/29 18:06:29 UTC
[jira] Commented: (WICKET-2655) WicketTester javadocs are referring
in many places to a component's path but it's not documented anywhere
[ https://issues.apache.org/jira/browse/WICKET-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795084#action_12795084 ]
Juergen Donnerstag commented on WICKET-2655:
--------------------------------------------
1) with Wicket each Component has an ID and that ID must be unique within its scope.
2) You can add Component into a Container
3) Via its path you can get(path) / access to a component any time without keeping its reference. The concept is similar to Java packages except that ":" is the separator
4) see getPageRelativePath, getRelativePath
I'll add a few @see to WicketTester's javadoc
> WicketTester javadocs are referring in many places to a component's path but it's not documented anywhere
> ---------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2655
> URL: https://issues.apache.org/jira/browse/WICKET-2655
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.4.5
> Reporter: Roberto Fasciolo
>
> In many places in the WicketTester javadoc there are references to a path parameter explained in the following way:
> path - path to Component
> But it's not explained anywhere what a path is, what does it contains, which separator is used there, what's the root of it and so on.
> Practically, it's impossible understanding how to use WicketTester from its javadoc because of that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.