Hi Martin, hi list
I guess I narrowed things down a bit. I was obviously looking at the
wrong places. The problem is with the renderedComponents Set (and not
with the isAuto flag as thought at first).
In the Page class there is that check here:
// If component never rendered
if
Hi
Me again with a follow up to my isAuto() problem.
Setting component.setAuto(true) is quite bad, since Wicket will remove
all components in the detachChildren() method which have the Auto Flag
and which are not an instance of InlineEnclosure. Which all of my
components obviously are not...
Hi,
On Thu, Apr 12, 2012 at 5:48 PM, Adrian Wiesmann awiesm...@somap.org wrote:
Hi
Me again with a follow up to my isAuto() problem.
Setting component.setAuto(true) is quite bad, since Wicket will remove all
components in the detachChildren() method which have the Auto Flag and which
are
Hello list
Some while ago I posted a few messages to this list where I asked for
help in finding a problem with Wicket 1.5. I was not able to find the
bug back then. Now I downloaded the bleeding edge version 1.5.4 and
tried again. And now I am a step further.
I have that rendering engine
Hello list
We built a rendering engine in Wicket 1.4 which takes a UI description
from an XML file and builds an HTML representation from that. Everything
worked fine in Wicket 1.4.x.
Now I tried to switch to Wicket 1.5.3. Without changing anything from
the rendering part, I now get this
Hi,
On Wed, Dec 21, 2011 at 11:58 AM, Adrian Wiesmann awiesm...@somap.org wrote:
Hello list
We built a rendering engine in Wicket 1.4 which takes a UI description from
an XML file and builds an HTML representation from that. Everything worked
fine in Wicket 1.4.x.
Now I tried to switch to
On 12/21/11 11:05 AM, Martin Grigorov wrote:
org.apache.wicket.WicketRuntimeException: The component(s) below
failed to render. A common problem is that you have added a component
in code but forgot to reference it in the markup (thus the component
will never be rendered).
This error means
On Wed, Dec 21, 2011 at 12:17 PM, Adrian Wiesmann awiesm...@somap.org wrote:
On 12/21/11 11:05 AM, Martin Grigorov wrote:
org.apache.wicket.WicketRuntimeException: The component(s) below
failed to render. A common problem is that you have added a component
in code but forgot to reference it
On 12/21/11 11:23 AM, Martin Grigorov wrote:
All this looks OK.
Can you paste the ids of the components which cannot be rendered ?
You mean this?
1. [Component id = caption]
2. [RepeatingView [Component id = toolbars]]
3. [GWListActionToolbar [Component id = 0]]
4.
Do you use a border? Because border component assignment changed
Cheers
Per
Am 21.12.2011 10:58, schrieb Adrian Wiesmann:
Hello list
We built a rendering engine in Wicket 1.4 which takes a UI description
from an XML file and builds an HTML representation from that.
Everything worked fine in
On 12/21/11 11:46 AM, Per Newgro wrote:
Do you use a border? Because border component assignment changed
No borders. Mostly iterators and plain panels...
Cheers,
Adrian
-
To unsubscribe, e-mail:
11 matches
Mail list logo
