i just always overwrite getMarkupId()
but a setter is also fine to have. We store it anyway.
johan
On 7/18/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> On 7/18/07, mperham <[EMAIL PROTECTED]> wrote:
> >
> >
> > We are migrating our existing application from UI framework XXX to
> Wicket
> > a
i dont remember how similar the markup id handling code is between the two
versions, but all i did was add this:
/**
* Sets this component's markup id to a user defined value. It is up to
the
* user to ensure this value is unique.
*
* The recommended way is to let wicket g
Igor, could you please attach a diff of your impl to WICKET-766? I'm going
to need to backport it to our private fork of 1.2.6.
mike
igor.vaynberg wrote:
>
>>
>> Now the actual ID of the select should be "selBusinessService" and that's
>> the wicket:id of the component in Java but Wicket prep
On 7/18/07, mperham <[EMAIL PROTECTED]> wrote:
>
>
> We are migrating our existing application from UI framework XXX to Wicket
> and
> we have a boatload of UI automated tests which depend on the ID attribute
> of
> our form inputs to drive the tests. I'm trying to figure out how to get
> Wicket t
We are migrating our existing application from UI framework XXX to Wicket and
we have a boatload of UI automated tests which depend on the ID attribute of
our form inputs to drive the tests. I'm trying to figure out how to get
Wicket to use the exact same IDs when it generates the HTML as with ou