I have a project that uses Wicket 1.x, and it's overwriting my
hardcoded ids with generated ones if setOutputMarkupId it true. If
this is not the intended behavior then I will open a JIRA issue.
On 12/18/06, Otan [EMAIL PROTECTED] wrote:
It works fine now. Thanks
On 19/12/06, Igor Vaynberg
i believe in the 1.x branch we always override.
-igor
On 12/27/06, Caleb Land [EMAIL PROTECTED] wrote:
I have a project that uses Wicket 1.x, and it's overwriting my
hardcoded ids with generated ones if setOutputMarkupId it true. If
this is not the intended behavior then I will open a JIRA
why do I still get this exception:
SEVERE: cannot update component that does not have setOutputMarkupId
property set to true. Component: [MarkupContainer [Component id = title,
page = openknowledge.EditPage, path = 5:editForm:title.RequiredTextField,
isVisible = true, isVersioned = false]]
try now
-igor
On 12/18/06, Otan [EMAIL PROTECTED] wrote:
why do I still get this exception:
SEVERE: cannot update component that does not have setOutputMarkupId
property set to true. Component: [MarkupContainer [Component id = title,
page = openknowledge.EditPage, path =
It works fine now. Thanks
On 19/12/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
try now
-igor
On 12/18/06, Otan [EMAIL PROTECTED] wrote:
why do I still get this exception:
SEVERE: cannot update component that does not have setOutputMarkupId
property set to true. Component:
its reverted
-igor
On 12/12/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 12/12/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
yeah i changed it, didnt think anyone was using this particular facet.
We use it also.
im not sure if we should put it back. the problem is sometimes you can
On 12/12/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
yeah i changed it, didnt think anyone was using this particular facet.
We use it also.
im not sure if we should put it back. the problem is sometimes you can paint
yourself into a nasty corner. if you have a component that uses a hardcoded
I've been using 2.0-SNAPSHOT for a while now and I noticed a behavior
recently that is new. If I have an HTML id defined in my markup:
wicket:panel
div id=labels wicket:id=labels/div
/wicket:panel
When the panel is rendered the HTML id attribute is replaced with
something that is generated by
yeah i changed it, didnt think anyone was using this particular facet.
im not sure if we should put it back. the problem is sometimes you can paint
yourself into a nasty corner. if you have a component that uses a hardcoded
id, and later the user of that component uses it twice in a page, or
Imo, quite strongly this time, if it is explicitly set, it should be
honored. As for the dangers of having conflicting ids, we could
introduce another debug utility that checks on duplicate ids when (or
after) rendering.
Eelco
On 12/11/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
yeah i changed
Hi Igor,
I also have a few hardcoded ids in my current Wicket 1.2 application.
Regards,
Erik.
Igor Vaynberg schreef:
yeah i changed it, didnt think anyone was using this particular facet.
im not sure if we should put it back. the problem is sometimes you can
paint yourself into a
11 matches
Mail list logo
