Hi Sebastian,
Back on this topic...
I strongly guess you are talking about dialog's button... You are right,
their ids are automatically generated. The reason why the ids are generated
is because DialogButton(s) are actually *not* wicket components, there are
really related to the jquery ui's dialog, and I need these ids for
enabling/disabling/showing/hiding them using ajax. This is the only case
like this in wicket-jquery-ui (except also in datatable buttons, but you
don't want to use kendo ui! ;) )
So, you cannot test the dialog's button as there were wicket's component,
but - if it can helps - you can retrieve the buttons (and then their ids)
using AbstractDialog#getButtons() and perform an ajax click like this:
target.appendJavaScript(String.format("$('#%s').click();",
myButton.getMarkupId())); // (just an idea)
Hope this help a little,
Best regards,
Sebastien
On Sat, Sep 14, 2013 at 4:59 PM, Sebastien Briquet <seb...@gmail.com> wrote:
> Hi Sebastian, i am currently on vacation. I am coming back to you end of
> next week!..
>
> Thanks & best regards,
> Sebastien
>
>
>
> On 13 sept. 2013, at 22:04, "seba.wag...@gmail.com" <seba.wag...@gmail.com>
> wrote:
>
> Hallo Sebastien,
>
> I run into a couple of issues when tryting to use WicketTester to write
> tests on classes and forms the are created using Wicket jQuery UI.
>
> WicketTester actually expects you to know the component id of an element.
>
> Some of the Buttons will generate those automatically. It does not seem to
> be that easy to integration WicketTester with Wicket jQuery UI.
>
> Do you have some pointers or ideas that would help us?
>
> Thanks,
> Sebastian
>
> --
> Sebastian Wagner
> <https://twitter.com/#%21/dead_lock>https://twitter.com/#!/dead_lock
> <http://www.webbase-design.de>http://www.webbase-design.de
> <http://www.wagner-sebastian.com>http://www.wagner-sebastian.com
> <seba.wag...@gmail.com>seba.wag...@gmail.com
>
>
