subject:"The component\(s\) below failed to render"

Re: WicketRuntimeException: The component(s) below failed to render. A common problem is that you have added a component in code but forgot to reference

2020-01-17 Thread Francois Meillet

Hi Prasanna,

Could you make a quickstart ?

François



> Le 17 janv. 2020 à 19:29, prasanna bajracharya 
>  a écrit :
> 
> Dear Wicket Community,
> 
> I am a new to wicket. I am trying to run someone else's legacy code in my
> local machine which is currently working in production environment. All my
> MyPanel.java, MyPanel.html and MyPanel.properties are in same package but
> still i'm getting following error in my weblogic console:
> 
> [image: enter image description here] 
> 
> Below is my Project structure for one of the component "sessionId": [image:
> enter image description here] 
> 
> I am using Ant build.xml to create MyApplication.jar and deploy it in my
> local weblogic server. I'm using eclipse as my IDE.
> 
> 
> Best regards,
> 
> Prasanna


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

WicketRuntimeException: The component(s) below failed to render. A common problem is that you have added a component in code but forgot to reference

2020-01-17 Thread prasanna bajracharya

Dear Wicket Community,

I am a new to wicket. I am trying to run someone else's legacy code in my
local machine which is currently working in production environment. All my
MyPanel.java, MyPanel.html and MyPanel.properties are in same package but
still i'm getting following error in my weblogic console:

[image: enter image description here] 

Below is my Project structure for one of the component "sessionId": [image:
enter image description here] 

I am using Ant build.xml to create MyApplication.jar and deploy it in my
local weblogic server. I'm using eclipse as my IDE.


Best regards,

Prasanna

Re: component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

2012-04-13 Thread Adrian Wiesmann


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 (renderedComponents == null ||
 !renderedComponents.contains(component))

and this method:

 public final void componentRendered(final Component component)
 {
  // Inform the page that this component rendered
  if (getApplication().getDebugSettings().getComponentUseCheck())
  {

This method is obviously only run in the debug mode when the 
ComponentUseCheck is activated (which is by default). Which also means 
that said Set is only instantiated when ComponentUseCheck is activated. 
Which also means the check in the first copy above will not be run when 
ComponentUseCheck is false/deactivated.


Now that I deactivated that check, my renderer works again.

So there must be some problem with dynamic components. I looked through 
the render methods of 1.5x and 1.4x. While some things changed, the flow 
seems to be mostly the same. Nothing obvious.


I'd love to do a minimal quickstart but that won't be very minimal. I'd 
have to add most of the renderer, or rewrite parts. I'll see if I find 
some time to put together something small.


In the meantime. If somebody has an idea where to look at, I'd be happy 
to test things out on my codebase.


Cheers,
Adrian


On 4/12/12 5:02 PM, Martin Grigorov wrote:

Hi,

On Thu, Apr 12, 2012 at 5:48 PM, Adrian Wiesmannawiesm...@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 not an instance of InlineEnclosure. Which all of my components obviously
are not...

While the isAuto(true) results in a nicely rendered component tree, when you
try to click on - say a row in a list - then Wicket throws an error because
the component in question was removed.

Well here we are again. How can I port my renderer which adds components to
the component tree on the fly as I was able to do in Wicket  1.5? What was
the intention to change the behaviour there?


It is not clear to me which behavior exactly has changed and now
causes you troubles.
Create a minimal quickstart that works on 1.4 and attach it to a ticket in Jira.



Regards,
Adrian



On 2/12/12 7:27 PM, Adrian Wiesmann wrote:


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 where I take an XML file, build an object
tree from that and have a renderer rendering a Wicket object tree and
finally Wicket which renders the HTML UI from that.

Now I noticed with version 1.5 of Wicket, that this line in the
org.apache.wicket.Page.class are the key to my problem (lines 611, 612):

// If not an auto component ...
if (!component.isAuto()  component.isVisibleInHierarchy())

I noticed that many of my components I add in my renderer on the fly are
returning isAuto = false on that line (and of course they are visible,
which adds them to unrenderedComponents and ultimately provokes the
error).

I then added this.setAuto(true); in one of my components. And voila, it
was not in the list of components which failed to render.

So here are my questions:

- What did change from version 1.4.x to version 1.5.x that results in
this error?
- Is that a bug in Wicket or do I need to fix my renderer somehow?
- What side effects does it have if I just add a setAuto(true) to all of
my components?

Thanks for your help!

Cheers,
Adrian




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

Re: component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

2012-04-12 Thread Adrian Wiesmann


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...


While the isAuto(true) results in a nicely rendered component tree, when 
you try to click on - say a row in a list - then Wicket throws an error 
because the component in question was removed.


Well here we are again. How can I port my renderer which adds components 
to the component tree on the fly as I was able to do in Wicket  1.5? 
What was the intention to change the behaviour there?


Regards,
Adrian


On 2/12/12 7:27 PM, Adrian Wiesmann wrote:

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 where I take an XML file, build an object
tree from that and have a renderer rendering a Wicket object tree and
finally Wicket which renders the HTML UI from that.

Now I noticed with version 1.5 of Wicket, that this line in the
org.apache.wicket.Page.class are the key to my problem (lines 611, 612):

// If not an auto component ...
if (!component.isAuto()  component.isVisibleInHierarchy())

I noticed that many of my components I add in my renderer on the fly are
returning isAuto = false on that line (and of course they are visible,
which adds them to unrenderedComponents and ultimately provokes the error).

I then added this.setAuto(true); in one of my components. And voila, it
was not in the list of components which failed to render.

So here are my questions:

- What did change from version 1.4.x to version 1.5.x that results in
this error?
- Is that a bug in Wicket or do I need to fix my renderer somehow?
- What side effects does it have if I just add a setAuto(true) to all of
my components?

Thanks for your help!

Cheers,
Adrian

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




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

Re: component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

2012-04-12 Thread Martin Grigorov

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 not an instance of InlineEnclosure. Which all of my components obviously
 are not...

 While the isAuto(true) results in a nicely rendered component tree, when you
 try to click on - say a row in a list - then Wicket throws an error because
 the component in question was removed.

 Well here we are again. How can I port my renderer which adds components to
 the component tree on the fly as I was able to do in Wicket  1.5? What was
 the intention to change the behaviour there?

It is not clear to me which behavior exactly has changed and now
causes you troubles.
Create a minimal quickstart that works on 1.4 and attach it to a ticket in Jira.


 Regards,
 Adrian



 On 2/12/12 7:27 PM, Adrian Wiesmann wrote:

 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 where I take an XML file, build an object
 tree from that and have a renderer rendering a Wicket object tree and
 finally Wicket which renders the HTML UI from that.

 Now I noticed with version 1.5 of Wicket, that this line in the
 org.apache.wicket.Page.class are the key to my problem (lines 611, 612):

 // If not an auto component ...
 if (!component.isAuto()  component.isVisibleInHierarchy())

 I noticed that many of my components I add in my renderer on the fly are
 returning isAuto = false on that line (and of course they are visible,
 which adds them to unrenderedComponents and ultimately provokes the
 error).

 I then added this.setAuto(true); in one of my components. And voila, it
 was not in the list of components which failed to render.

 So here are my questions:

 - What did change from version 1.4.x to version 1.5.x that results in
 this error?
 - Is that a bug in Wicket or do I need to fix my renderer somehow?
 - What side effects does it have if I just add a setAuto(true) to all of
 my components?

 Thanks for your help!

 Cheers,
 Adrian

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



 -
 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

component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

2012-02-12 Thread Adrian Wiesmann


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 where I take an XML file, build an object 
tree from that and have a renderer rendering a Wicket object tree and 
finally Wicket which renders the HTML UI from that.


Now I noticed with version 1.5 of Wicket, that this line in the 
org.apache.wicket.Page.class are the key to my problem (lines 611, 612):


// If not an auto component ...
if (!component.isAuto()  component.isVisibleInHierarchy())

I noticed that many of my components I add in my renderer on the fly are 
returning isAuto = false on that line (and of course they are visible, 
which adds them to unrenderedComponents and ultimately provokes the error).


I then added this.setAuto(true); in one of my components. And voila, it 
was not in the list of components which failed to render.


So here are my questions:

- What did change from version 1.4.x to version 1.5.x that results in 
this error?

- Is that a bug in Wicket or do I need to fix my renderer somehow?
- What side effects does it have if I just add a setAuto(true) to all of 
my components?


Thanks for your help!

Cheers,
Adrian

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

Wicket 1.5: The component(s) below failed to render

2011-12-21 Thread 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 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 error:


 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).

Below that message I get a list with all components.

We mostly use ListViews to build the UI:

ListViewObjectBase listView = new ListViewObjectBase(eachGuiElem, 
formRoot.getChildren())

{
@Override
protected void populateItem(ListItemObjectBase item)
{
ObjectBase ob = item.getModelObject();

item.add(new Panel(...));
}
};

So here is my question. What did change with Wicket 1.5? How can I make 
our renderer work again? Where should I look at to find out whats wrong?


Thanks,
Adrian

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

Re: Wicket 1.5: The component(s) below failed to render

2011-12-21 Thread Martin Grigorov

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 Wicket 1.5.3. Without changing anything from the
 rendering part, I now get this error:

 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 that Wicket sees these components only in the Java
component tree but doesn't see them in the markup tree.
How exactly do you pass the generated markup to Wicket ?


 Below that message I get a list with all components.

 We mostly use ListViews to build the UI:

 ListViewObjectBase listView = new ListViewObjectBase(eachGuiElem,
 formRoot.getChildren())
 {
        @Override
        protected void populateItem(ListItemObjectBase item)
        {
                ObjectBase ob = item.getModelObject();

                item.add(new Panel(...));
        }
 };

 So here is my question. What did change with Wicket 1.5? How can I make our
 renderer work again? Where should I look at to find out whats wrong?

 Thanks,
 Adrian

 -
 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

Re: Wicket 1.5: The component(s) below failed to render

2011-12-21 Thread Adrian Wiesmann


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 that Wicket sees these components only in the Java
component tree but doesn't see them in the markup tree.
How exactly do you pass the generated markup to Wicket ?


Let's have a simple example:

Simple layout/UI in XML:

frame
actionbox DataBinding=@Inventory[0]
fop-action enabled=true /
/actionbox

list DataBinding=@Inventory[0]
field DataBinding=name/
/list   
/frame

Which is read and converted into an in-memory object tree:

frame
actionbox
fop-action
...

This is then taken and Wicket classes are instantiated for every 
in-memory object.


In the constructor of every class (depending on its nature) there is 
code to build the Wicket based object structure. Something like this:


ListViewObjectBase listView = new ListViewObjectBase(eachGuiElem, 
formRoot.getChildren())

{
@Override
protected void populateItem(ListItemObjectBase item)
{
ObjectBase ob = item.getModelObject();

item.add(getPanelFromObjectBase(cell, ob, model, form));
}
};

With that html content:

...
tr wicket:id=eachGuiElem
  td style=border:0px;margin:0px;padding:0px; wicket:id=cell/td
/tr 
...

Where getOPanelFromObjectBase contains something like this:

protected Panel getPanelFromObjectBase(String id, ObjectBase ob, 
IModel? model, final Form? form)

{
if (ob.getClass().equals(GListAndDetail.class))
{
return new GWListAndDetail(id, model, (GListAndDetail) ob, 
form);
}
else if (ob.getClass().equals(GActionBox.class))
{
return new GWActionBox(id, model, (GActionBox) ob, form);
}
...

All classes starting with GWxxx are subclasses of Wicket Panels.

Every GWxxx class has an HTML file with the same name and the ending 
html in the same directory as the class file. So Wicket should be able 
to find the right markup. And with the right markup it should be able to 
render not only the object tree but also the html representation.



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

Re: Wicket 1.5: The component(s) below failed to render

2011-12-21 Thread Martin Grigorov

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 in the markup (thus the component
 will never be rendered).


 This error means that Wicket sees these components only in the Java
 component tree but doesn't see them in the markup tree.
 How exactly do you pass the generated markup to Wicket ?


 Let's have a simple example:

 Simple layout/UI in XML:

 frame
        actionbox DataBinding=@Inventory[0]
                fop-action enabled=true /
        /actionbox

        list DataBinding=@Inventory[0]
                field DataBinding=name/
        /list
 /frame

 Which is read and converted into an in-memory object tree:

 frame
        actionbox
                fop-action
 ...

 This is then taken and Wicket classes are instantiated for every in-memory
 object.

 In the constructor of every class (depending on its nature) there is code to
 build the Wicket based object structure. Something like this:


 ListViewObjectBase listView = new ListViewObjectBase(eachGuiElem,
 formRoot.getChildren())
 {
        @Override
        protected void populateItem(ListItemObjectBase item)
        {
                ObjectBase ob = item.getModelObject();

                item.add(getPanelFromObjectBase(cell, ob, model, form));
        }
 };

 With that html content:

 ...
 tr wicket:id=eachGuiElem
  td style=border:0px;margin:0px;padding:0px; wicket:id=cell/td
 /tr
 ...

 Where getOPanelFromObjectBase contains something like this:

 protected Panel getPanelFromObjectBase(String id, ObjectBase ob, IModel?
 model, final Form? form)
 {
        if (ob.getClass().equals(GListAndDetail.class))
        {
                return new GWListAndDetail(id, model, (GListAndDetail) ob,
 form);
        }
        else if (ob.getClass().equals(GActionBox.class))
        {
                return new GWActionBox(id, model, (GActionBox) ob, form);
        }
 ...

 All classes starting with GWxxx are subclasses of Wicket Panels.

 Every GWxxx class has an HTML file with the same name and the ending html in
 the same directory as the class file. So Wicket should be able to find the
 right markup. And with the right markup it should be able to render not only
 the object tree but also the html representation.

All this looks OK.
Can you paste the ids of the components which cannot be rendered ?




 -
 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

Re: Wicket 1.5: The component(s) below failed to render

2011-12-21 Thread Adrian Wiesmann


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. [AjaxFallbackHeadersToolbar [Component id = 1]]
5. [RepeatingView [Component id = headers]]
6. [AbstractItem [Component id = 1]]
7. [ [Component id = header]]
8. [BorderBodyContainer [Component id = header_body]]
9. [Component id = label]
10. [ [Component id = orderByLink]]
11. [BorderBodyContainer [Component id = header_body]]
12. [Component id = label]
13. [AbstractItem [Component id = 2]]
14. [ [Component id = header]]
15. [BorderBodyContainer [Component id = header_body]]
16. [Component id = label]
17. [ [Component id = orderByLink]]
18. [BorderBodyContainer [Component id = header_body]]
19. [Component id = label]
20. [AbstractItem [Component id = 3]]
21. [ [Component id = header]]
22. [BorderBodyContainer [Component id = header_body]]
23. [Component id = label]
24. [ [Component id = orderByLink]]
25. [BorderBodyContainer [Component id = header_body]]
26. [Component id = label]
27. [AbstractItem [Component id = 4]]
28. [ [Component id = header]]
29. [BorderBodyContainer [Component id = header_body]]
30. [Component id = label]
31. [ [Component id = orderByLink]]
32. [BorderBodyContainer [Component id = header_body]]
33. [Component id = label]
34. [AbstractItem [Component id = 5]]
35. [ [Component id = header]]
36. [BorderBodyContainer [Component id = header_body]]
37. [Component id = label]
38. [ [Component id = orderByLink]]
39. [BorderBodyContainer [Component id = header_body]]
40. [Component id = label]
41. [GWListFilterToolbar [Component id = 2]]
42. [FilterForm [Component id = filterform]]
43. [RepeatingView [Component id = filters]]
44. [WebMarkupContainer [Component id = 1]]
45. [TextFilterEx [Component id = filter]]
46. [TextField [Component id = filter]]
47. [WebMarkupContainer [Component id = 2]]
48. [ChoiceFilter [Component id = filter]]
49. [DropDownChoice [Component id = filter]]
50. [WebMarkupContainer [Component id = 3]]
51. [TextFilterEx [Component id = filter]]
52. [TextField [Component id = filter]]
53. [WebMarkupContainer [Component id = 4]]
54. [NoFilter [Component id = filter]]
55. [WebMarkupContainer [Component id = 5]]
56. [NoFilter [Component id = filter]]
57. [Component id = caption]
58. [RepeatingView [Component id = toolbars]]
59. [GWListActionToolbar [Component id = 5]]
60. [AjaxFallbackHeadersToolbar [Component id = 6]]
61. [RepeatingView [Component id = headers]]
62. [AbstractItem [Component id = 1]]
63. [ [Component id = header]]
64. [BorderBodyContainer [Component id = header_body]]
65. [Component id = label]
66. [ [Component id = orderByLink]]
67. [BorderBodyContainer [Component id = header_body]]
68. [Component id = label]
69. [AbstractItem [Component id = 2]]
70. [ [Component id = header]]
71. [BorderBodyContainer [Component id = header_body]]
72. [Component id = label]
73. [ [Component id = orderByLink]]
74. [BorderBodyContainer [Component id = header_body]]
75. [Component id = label]
76. [AbstractItem [Component id = 3]]
77. [ [Component id = header]]
78. [BorderBodyContainer [Component id = header_body]]
79. [Component id = label]
80. [ [Component id = orderByLink]]
81. [BorderBodyContainer [Component id = header_body]]
82. [Component id = label]
83. [AbstractItem [Component id = 4]]
84. [ [Component id = header]]
85. [BorderBodyContainer [Component id = header_body]]
86. [Component id = label]
87. [ [Component id = orderByLink]]
88. [BorderBodyContainer [Component id = header_body]]
89. [Component id = label]
90. [GWListFilterToolbar [Component id = 7]]
91. [FilterForm [Component id = filterform]]
92. [RepeatingView [Component id = filters]]
93. [WebMarkupContainer [Component id = 1]]
94. [TextFilterEx [Component id = filter]]
95. [TextField [Component id = filter]]
96. [WebMarkupContainer [Component id = 2]]
97. [TextFilterEx [Component id = filter]]
98. [TextField [Component id = filter]]
99. [WebMarkupContainer [Component id = 3]]
100. [TextFilterEx [Component id = filter]]
101. [TextField [Component id = filter]]
102. [WebMarkupContainer [Component id = 4]]
103. [TextFilterEx [Component id = filter]]
104. [TextField [Component id = filter]]

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

Re: Wicket 1.5: The component(s) below failed to render

2011-12-21 Thread Per Newgro


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 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 error:


 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).

Below that message I get a list with all components.

We mostly use ListViews to build the UI:

ListViewObjectBase listView = new 
ListViewObjectBase(eachGuiElem, formRoot.getChildren())

{
@Override
protected void populateItem(ListItemObjectBase item)
{
ObjectBase ob = item.getModelObject();

item.add(new Panel(...));
}
};

So here is my question. What did change with Wicket 1.5? How can I 
make our renderer work again? Where should I look at to find out whats 
wrong?


Thanks,
Adrian

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





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

Re: Wicket 1.5: The component(s) below failed to render

2011-12-21 Thread Adrian Wiesmann


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: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

The component(s) below failed to render (BasePage components are not rendering)

2011-01-24 Thread Teddy C


Using the Wicket Phonebook as a base, I am having problem dispalyng the
EditContactPage. To the BasePage I add user and role and a Session to save
the login user and role. The listContactPage wich extends the BasePage works
fine. The EditContactPage which also extends the Basepage, is mot able to
display the EditContactPage, failing to render the Components that are
defined in the BasePage.

I would appreciate if someone has any idea of a  solution to this problem.

BasePage.Html
html
head
titleWicket Phonebook/title
link rel=stylesheet type=text/css href=styles.css/

/head
body
div
Login Name:

/div
div
Login Role: 

/div
div wicket:id=status class=status[[status 
messages]]/div
wicket:child/
/body
/html

ListContactpage:
html xmlns:wicket
wicket:extend
form wicket:id=filter-form
input type=hidden name=tracker wicket:id=focus-tracker/
table wicket:id=cars cellspacing=0 cellpadding=2 class=grid
/table
[call to focus restore script]
input wicket:id=delete-selected value=PROCEED TO APPROVAL STAGE
type=submit/
/form

/wicket:extend
/html

EditContactPage:
html xmlns:wicket
wicket:extend
form wicket:id=contactForm
table cellspacing=0 cellpadding=2
tr
tdwicket:message
key=passenger[passenger]/wicket:message/tdtdlabel
wicket:id=passenger size=30//td
/tr
tr
tdwicket:message
key=costcenter[costcenter]/wicket:message/tdtdinput type=text
wicket:id=costcenter size=5 maxlength=6//td
/tr
tr
tdwicket:message 
key=car_no[car_no]/wicket:message/tdtdlabel
wicket:id=car_no size=30//td
/tr
tr
tdwicket:message 
key=pu_addr[pu_addr]/wicket:message/tdtdlabel
wicket:id=pu_addr size=30//td
/tr
tr
tdwicket:message
key=dest_addr[dest_addr]/wicket:message/tdtdlabel
wicket:id=dest_addr size=30//td
/tr
tr
tdwicket:message key=rate[rate]/wicket:message/tdtdlabel
wicket:id=rate size=30//td
/tr
tr
tdwicket:message key=toll[toll]/wicket:message/tdtdlabel
wicket:id=toll size=30//td
/tr
tr
tdwicket:message key=wait[wait]/wicket:message/tdtdlabel
wicket:id=wait size=30//td
/tr
tr
tdwicket:message key=stops[stops]/wicket:message/tdtdlabel
wicket:id=stops size=30//td
/tr
tr
tr
tdwicket:message key=other[other]/wicket:message/tdtdlabel
wicket:id=other size=30//td
/tr
tr
tr
tdwicket:message 
key=wc2pct[wc2pct]/wicket:message/tdtdlabel
wicket:id=wc2pct size=30//td
/tr
tr
tr
tdwicket:message key=total[total]/wicket:message/tdtdlabel 
wicket:id=total size=10//td
/tr
tr
tdnbsp;/tdtdinput type=submit wicket:id=save value=[save]
input type=submit wicket:id=cancel value=[cancel]//td
/tr
/table
/form
/wicket:extend
/html

ERROR:
WicketMessage: 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).1. [MarkupContainer
[Component id = status]]2. [Component id = Name]3. [Component id = Role]Root
cause: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).1. [MarkupContainer [Component id = status]]2. [Component id =
Name]3. [Component id = Role] at
org.apache.wicket.Page.checkRendering(Page.java:1182) at
org.apache.wicket.Page.renderPage(Page.java:922) at
org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:167)

at
org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:58)

at
org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:105)

at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)  
  
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329) at
org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428) at
org.apache.wicket.RequestCycle.request(RequestCycle.java:545) at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:312)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)

at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76

Re: The component(s) below failed to render (BasePage components are not rendering)

2011-01-24 Thread Martin Sachs

hi,

i dont see problems in the markup. Can u please post some
java-components ? Do you have called super. ... -methodes (e.g.
onInitialize)

martin

Am 24.01.2011 20:19, schrieb Teddy C:
 Using the Wicket Phonebook as a base, I am having problem dispalyng the
 EditContactPage. To the BasePage I add user and role and a Session to save
 the login user and role. The listContactPage wich extends the BasePage works
 fine. The EditContactPage which also extends the Basepage, is mot able to
 display the EditContactPage, failing to render the Components that are
 defined in the BasePage.

 I would appreciate if someone has any idea of a  solution to this problem.

 BasePage.Html
 html
   head
   titleWicket Phonebook/title
   link rel=stylesheet type=text/css href=styles.css/
   
   /head
   body
   div
   Login Name:
   
   /div
   div
   Login Role: 
   
   /div
   div wicket:id=status class=status[[status 
 messages]]/div
   wicket:child/
   /body
 /html

 ListContactpage:
 html xmlns:wicket
 wicket:extend
 form wicket:id=filter-form
   input type=hidden name=tracker wicket:id=focus-tracker/
   table wicket:id=cars cellspacing=0 cellpadding=2 class=grid
   /table
   [call to focus restore script]
   input wicket:id=delete-selected value=PROCEED TO APPROVAL STAGE
 type=submit/
 /form

 /wicket:extend
 /html

 EditContactPage:
 html xmlns:wicket
 wicket:extend
 form wicket:id=contactForm
 table cellspacing=0 cellpadding=2
 tr
   tdwicket:message
 key=passenger[passenger]/wicket:message/tdtdlabel
 wicket:id=passenger size=30//td
 /tr
 tr
   tdwicket:message
 key=costcenter[costcenter]/wicket:message/tdtdinput type=text
 wicket:id=costcenter size=5 maxlength=6//td
 /tr
 tr
   tdwicket:message 
 key=car_no[car_no]/wicket:message/tdtdlabel
 wicket:id=car_no size=30//td
 /tr
 tr
   tdwicket:message 
 key=pu_addr[pu_addr]/wicket:message/tdtdlabel
 wicket:id=pu_addr size=30//td
 /tr
 tr
   tdwicket:message
 key=dest_addr[dest_addr]/wicket:message/tdtdlabel
 wicket:id=dest_addr size=30//td
 /tr
 tr
   tdwicket:message key=rate[rate]/wicket:message/tdtdlabel
 wicket:id=rate size=30//td
 /tr
 tr
   tdwicket:message key=toll[toll]/wicket:message/tdtdlabel
 wicket:id=toll size=30//td
 /tr
 tr
   tdwicket:message key=wait[wait]/wicket:message/tdtdlabel
 wicket:id=wait size=30//td
 /tr
 tr
   tdwicket:message key=stops[stops]/wicket:message/tdtdlabel
 wicket:id=stops size=30//td
 /tr
 tr
 tr
   tdwicket:message key=other[other]/wicket:message/tdtdlabel
 wicket:id=other size=30//td
 /tr
 tr
 tr
   tdwicket:message 
 key=wc2pct[wc2pct]/wicket:message/tdtdlabel
 wicket:id=wc2pct size=30//td
 /tr
 tr
 tr
   tdwicket:message key=total[total]/wicket:message/tdtdlabel 
 wicket:id=total size=10//td
 /tr
 tr
   tdnbsp;/tdtdinput type=submit wicket:id=save value=[save]
   input type=submit wicket:id=cancel value=[cancel]//td
 /tr
 /table
 /form
 /wicket:extend
 /html

 ERROR:
 WicketMessage: 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).1. [MarkupContainer
 [Component id = status]]2. [Component id = Name]3. [Component id = Role]Root
 cause: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).1. [MarkupContainer [Component id = status]]2. [Component id =
 Name]3. [Component id = Role] at
 org.apache.wicket.Page.checkRendering(Page.java:1182) at
 org.apache.wicket.Page.renderPage(Page.java:922) at
 org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:167)
 
 at
 org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:58)
 
 at
 org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:105)
 
 at
 org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)
 
 at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329) at
 org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428) at
 org.apache.wicket.RequestCycle.request(RequestCycle.java:545) at
 org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479)
 at
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:312)  
   
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206

Re: The component(s) below failed to render

2008-06-17 Thread Michael_Bo


No that doesn't really help, because I do not want to edit the second bean, I
only want to see all objects of the second bean. And if possible that
objects in a dropdownlist.

chears Michael



Dan Syrstad-2 wrote:
 
 In WWB, if you want the related bean to only show certain attributes, you
 can put something like:
 
 YourBean { ...  props: name, -someOtherAttribute, ...;  ... }
 
 in your beanprops file. This will remove someOtherAttribute from your
 view. Does that help?
 
 -Dan
 
 On Fri, Jun 13, 2008 at 6:02 AM, Michael_Bo [EMAIL PROTECTED]
 wrote:
 

 No, i've added the dropdownchoice to the markup and did not forgot. My
 problem is a little bit more complex.
 with wicket web beans you can't display a bean, that has a relation to an
 another bean. This relationed bean is showed with all attributes. But i
 Only
 wan't one or two, like 'name'. So What i've tried was to remove first the
 relationed attribut from the bean, then create a BeanForm, and then add
 my
 special DropDownChoice to this created BeanForm. But because using the
 wicket templates, adding an own Componte doesn't realy work.

 Did you understand the problem?

 chears Michael


 greeklinux wrote:
 
  Do you add the DropDownChoice to the markup and forgott the wicket id?
 
 
 
  Michael_Bo wrote:
 
  Hi,
 
  i have a problem with some Components. I'm using Wicket Web beans.
  If tried to add an additional form to a beanFrom. Then I get The
  following Error:
 
  WicketMessage: 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).
 
  1. [MarkupContainer [Component id = beanRForm, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
  isVersioned = true]]
  2. [MarkupContainer [Component id = beanDropDown, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
  isVersioned = false]]
 
  Root cause:
 
  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).
 
  1. [MarkupContainer [Component id = beanRForm, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
  isVersioned = true]]
  2. [MarkupContainer [Component id = beanDropDown, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
  isVersioned = false]]
 
  at org.apache.wicket.Page.checkRendering(Page.java:1116)
  at org.apache.wicket.Page.renderPage(Page.java:914)
  at
 
 org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:163)
  at
 
 org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:58)
  at
 
 org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
  at
 
 org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1172)
  at org.apache.wicket.RequestCycle.step(RequestCycle.java:1243)
  at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1330)
  at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
  at
 
 org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:358)
  at
 
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
  at
 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
  at
 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
  at
 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
  at
 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
  at
 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
  at
 org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
  at
 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
  at org.mortbay.jetty.Server.handle(Server.java:295)
  at
 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
  at
 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
  at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
  at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
  at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
  at
 
 org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
  at
 
 org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
 
  What I want is an Additional Dropdownchoice in my beanFrom because the
  beanFrom gets its field from a Bean.
  I don't really know in what .html file I have to put this additional
 Bean
 
  chears
  Michael
 
 
 

 --
 View this message in context:
 http://www.nabble.com

Re: The component(s) below failed to render

2008-06-13 Thread Michael_Bo


No, i've added the dropdownchoice to the markup and did not forgot. My
problem is a little bit more complex.
with wicket web beans you can't display a bean, that has a relation to an
another bean. This relationed bean is showed with all attributes. But i Only
wan't one or two, like 'name'. So What i've tried was to remove first the
relationed attribut from the bean, then create a BeanForm, and then add my
special DropDownChoice to this created BeanForm. But because using the
wicket templates, adding an own Componte doesn't realy work.

Did you understand the problem?

chears Michael


greeklinux wrote:
 
 Do you add the DropDownChoice to the markup and forgott the wicket id?
 
 
 
 Michael_Bo wrote:
 
 Hi,
 
 i have a problem with some Components. I'm using Wicket Web beans.
 If tried to add an additional form to a beanFrom. Then I get The
 following Error:
 
 WicketMessage: 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).
 
 1. [MarkupContainer [Component id = beanRForm, page =
 metaWicket.EditPage, path =
 2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
 isVersioned = true]]
 2. [MarkupContainer [Component id = beanDropDown, page =
 metaWicket.EditPage, path =
 2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
 isVersioned = false]]
 
 Root cause:
 
 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).
 
 1. [MarkupContainer [Component id = beanRForm, page =
 metaWicket.EditPage, path =
 2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
 isVersioned = true]]
 2. [MarkupContainer [Component id = beanDropDown, page =
 metaWicket.EditPage, path =
 2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
 isVersioned = false]]
 
 at org.apache.wicket.Page.checkRendering(Page.java:1116)
 at org.apache.wicket.Page.renderPage(Page.java:914)
 at
 org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:163)
 at
 org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:58)
 at
 org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
 at
 org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1172)
 at org.apache.wicket.RequestCycle.step(RequestCycle.java:1243)
 at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1330)
 at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
 at
 org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:358)
 at
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
 at
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
 at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
 at
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
 at
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
 at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
 at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
 at org.mortbay.jetty.Server.handle(Server.java:295)
 at
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
 at
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
 at
 org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
 at
 org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
 
 What I want is an Additional Dropdownchoice in my beanFrom because the
 beanFrom gets its field from a Bean. 
 I don't really know in what .html file I have to put this additional Bean
 
 chears
 Michael
 
 
 

-- 
View this message in context: 
http://www.nabble.com/The-component%28s%29-below-failed-to-render-tp17803377p17821002.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: The component(s) below failed to render

2008-06-13 Thread Dan Syrstad

In WWB, if you want the related bean to only show certain attributes, you
can put something like:

YourBean { ...  props: name, -someOtherAttribute, ...;  ... }

in your beanprops file. This will remove someOtherAttribute from your
view. Does that help?

-Dan

On Fri, Jun 13, 2008 at 6:02 AM, Michael_Bo [EMAIL PROTECTED]
wrote:


 No, i've added the dropdownchoice to the markup and did not forgot. My
 problem is a little bit more complex.
 with wicket web beans you can't display a bean, that has a relation to an
 another bean. This relationed bean is showed with all attributes. But i
 Only
 wan't one or two, like 'name'. So What i've tried was to remove first the
 relationed attribut from the bean, then create a BeanForm, and then add my
 special DropDownChoice to this created BeanForm. But because using the
 wicket templates, adding an own Componte doesn't realy work.

 Did you understand the problem?

 chears Michael


 greeklinux wrote:
 
  Do you add the DropDownChoice to the markup and forgott the wicket id?
 
 
 
  Michael_Bo wrote:
 
  Hi,
 
  i have a problem with some Components. I'm using Wicket Web beans.
  If tried to add an additional form to a beanFrom. Then I get The
  following Error:
 
  WicketMessage: 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).
 
  1. [MarkupContainer [Component id = beanRForm, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
  isVersioned = true]]
  2. [MarkupContainer [Component id = beanDropDown, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
  isVersioned = false]]
 
  Root cause:
 
  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).
 
  1. [MarkupContainer [Component id = beanRForm, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
  isVersioned = true]]
  2. [MarkupContainer [Component id = beanDropDown, page =
  metaWicket.EditPage, path =
  2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
  isVersioned = false]]
 
  at org.apache.wicket.Page.checkRendering(Page.java:1116)
  at org.apache.wicket.Page.renderPage(Page.java:914)
  at
 
 org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:163)
  at
 
 org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:58)
  at
 
 org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
  at
 
 org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1172)
  at org.apache.wicket.RequestCycle.step(RequestCycle.java:1243)
  at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1330)
  at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
  at
 
 org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:358)
  at
 
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
  at
 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
  at
  org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
  at
 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
  at
  org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
  at
  org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
  at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
  at
  org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
  at org.mortbay.jetty.Server.handle(Server.java:295)
  at
  org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
  at
 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
  at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
  at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
  at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
  at
 
 org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
  at
 
 org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
 
  What I want is an Additional Dropdownchoice in my beanFrom because the
  beanFrom gets its field from a Bean.
  I don't really know in what .html file I have to put this additional
 Bean
 
  chears
  Michael
 
 
 

 --
 View this message in context:
 http://www.nabble.com/The-component%28s%29-below-failed-to-render-tp17803377p17821002.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL

Re: The component(s) below failed to render

2008-06-12 Thread greeklinux


Do you add the DropDownChoice to the markup and forgott the wicket id?



Michael_Bo wrote:
 
 Hi,
 
 i have a problem with some Components. I'm using Wicket Web beans.
 If tried to add an additional form to a beanFrom. Then I get The following
 Error:
 
 WicketMessage: 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).
 
 1. [MarkupContainer [Component id = beanRForm, page = metaWicket.EditPage,
 path = 2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible =
 true, isVersioned = true]]
 2. [MarkupContainer [Component id = beanDropDown, page =
 metaWicket.EditPage, path =
 2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
 isVersioned = false]]
 
 Root cause:
 
 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).
 
 1. [MarkupContainer [Component id = beanRForm, page = metaWicket.EditPage,
 path = 2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible =
 true, isVersioned = true]]
 2. [MarkupContainer [Component id = beanDropDown, page =
 metaWicket.EditPage, path =
 2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
 isVersioned = false]]
 
 at org.apache.wicket.Page.checkRendering(Page.java:1116)
 at org.apache.wicket.Page.renderPage(Page.java:914)
 at
 org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:163)
 at
 org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:58)
 at
 org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
 at
 org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1172)
 at org.apache.wicket.RequestCycle.step(RequestCycle.java:1243)
 at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1330)
 at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
 at
 org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:358)
 at
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
 at
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
 at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
 at
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
 at
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
 at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
 at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
 at org.mortbay.jetty.Server.handle(Server.java:295)
 at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
 at
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
 at
 org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
 at
 org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
 
 What I want is an Additional Dropdownchoice in my beanFrom because the
 beanFrom gets its field from a Bean. 
 I don't really know in what .html file I have to put this additional Bean
 
 chears
 Michael
 

-- 
View this message in context: 
http://www.nabble.com/The-component%28s%29-below-failed-to-render-tp17803377p17810721.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WicketRuntimeException: The component(s) below failed to render. A common problem is that you have added a component in code but forgot to reference

WicketRuntimeException: The component(s) below failed to render. A common problem is that you have added a component in code but forgot to reference

Re: component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

Re: component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

Re: component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

component.isAuto - was: Wicket 1.5: The component(s) below failed to render (revisited)

Wicket 1.5: The component(s) below failed to render

Re: Wicket 1.5: The component(s) below failed to render

Re: Wicket 1.5: The component(s) below failed to render

Re: Wicket 1.5: The component(s) below failed to render

Re: Wicket 1.5: The component(s) below failed to render

Re: Wicket 1.5: The component(s) below failed to render

Re: Wicket 1.5: The component(s) below failed to render

The component(s) below failed to render (BasePage components are not rendering)

Re: The component(s) below failed to render (BasePage components are not rendering)

Re: The component(s) below failed to render

Re: The component(s) below failed to render

Re: The component(s) below failed to render

Re: The component(s) below failed to render

19 matches

Site Navigation

Mail list logo

Footer information