Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::'  doesn't means 1.4 is in action. Just take
a look at event listener implementation.

About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...


If someone wonder how to determine why his page is stateful here is
the solution:
if (!isPageStateless()) {
            visitChildren(Component.class, new IVisitor<Component,
Component>() {
                @Override
                public void component(Component component,
IVisit<Component> iVisit) {
                    if (!component.isStateless()) {
                        LOGGER.info("Stateful component found [ "
                                + component.getClass().getName() + " : "
                                + component.getMarkupId() + " ]");

                        // iVisit.stop(component);
                    }
                }
            });
        }

If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.


On 21 August 2012 15:47, Martin Grigorov <mgrigo...@apache.org> wrote:
> Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
> url means that this is Wicket pre-1.5 ;-)
>
> I guess Sven will join this conversation later today and explain in
> more details.
>
> On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert <alex.shub...@gmail.com> wrote:
>> Martin
>> with all my respect but their build script uses
>>
>>                 <dependency>
>>                         <groupId>org.apache.wicket</groupId>
>>                         <artifactId>wicket-core</artifactId>
>>                         <version>${wicket.version}</version>
>>                 </dependency>
>>
>> ${wicket.version} derived from parent pom where
>> <wicket.version>1.5.0</wicket.version>
>>
>> So,
>> 1. no stateless form
>> 2. it is 1.5
>> 3. it's pretty easy to ensure yourself just by looking into code
>> http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
>> can't be compiled under 1.4
>>
>> Anyway: what does your answer has to do with my question? One more
>> time: how that example manage not to increase page version shown in
>> url on every tree node selection?
>> thanks
>>
>>
>> On 21 August 2012 14:39, Martin Grigorov <mgrigo...@apache.org> wrote:
>>> The deployed examples use Wicket 1.4.
>>>
>>> http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
>>>
>>> On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert <alex.shub...@gmail.com> 
>>> wrote:
>>>> They are using
>>>> Form<Void> form = new Form<Void>("form");
>>>>
>>>> and still no version in url on round-trips. Also, FilterForm from
>>>> Wicket API doesn't extends StatelessForm while your answer states that
>>>> must be the case.
>>>>
>>>>
>>>> On 21 August 2012 14:20, Martin Grigorov <mgrigo...@apache.org> wrote:
>>>>> Use StatelessForm instead.
>>>>>
>>>>> On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert <alex.shub...@gmail.com> 
>>>>> wrote:
>>>>>> Hello
>>>>>>
>>>>>> Recently I found wicket tree control
>>>>>>
>>>>>> http://wicket-tree.appspot.com/nested
>>>>>>
>>>>>>  and one there is a thing I can't understand: while the page contains
>>>>>> Form it looks like not versioned. I mean there are no version number
>>>>>> in a url.
>>>>>> How does it work then? Is there any clear way to build pages
>>>>>> containing Form without explicit version number in url except some
>>>>>> black magic involved ( modified MountedMapper )
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best regards
>>>>>> Alexandr
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Martin Grigorov
>>>>> jWeekend
>>>>> Training, Consulting, Development
>>>>> http://jWeekend.com
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best regards
>>>> Alexandr
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>
>>
>>
>> --
>> Best regards
>> Alexandr
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>



-- 
Best regards
Alexandr

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to