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/30 15:24:29 UTC

[jira] Resolved: (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:all-tabpanel ]

Juergen Donnerstag resolved WICKET-2655.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-M1
                   1.4.6
         Assignee: Juergen Donnerstag

javadoc updated

> 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
>            Assignee: Juergen Donnerstag
>             Fix For: 1.4.6, 1.5-M1
>
>
> 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.