I understand, but what most developers do instead of searching for the
component, actually because it makes refactoring easier, is to keep a
reference of that child-component. Eg. instead of
formBorder = new FormBorder(parent, formBorder)
formBorder.setBorderBodyContainer(formBorder)
new
I extened BoxBorderTestPage_7 to click the link and to validate the
output of the second render as well. The problem should be fixed.
Juergen
On 10/7/06, Alberto Bueno [EMAIL PROTECTED] wrote:
Hi Juergen Donnerstag,
The example BoxBorderTestPage_7 runs correctly because you only render
the
Hi Juergen Donnerstag
Thanks for you patience. ;)
The problem has been fixed with the changes that we have added to the
trunk.
Now I have another question.
In the example BoxBorderTextPage_7 we add a TextField in the FormBorder.
After that,
If I want to find this component into the FormBorder
Because FormBorder puts a form _around_ the wicket:body tag, the
name component gets added to the body container. The body container
id is border.getId() + Body. Hence
get(border.form.borderBody.name) or
border.getBodyContainer().get(name) or
formBorder.get(borderBody.name)
Juergen
On 10/9/06,
Yes, now the ways to find the child into the border are the ways that
you say, but I think that the
way would have to be transparent, like when we add a new child:
TextField textfield = new TextFieldString(formBorder, name,
new PropertyModelString(
properties, name));
In that
On 10/9/06, Alberto Bueno [EMAIL PROTECTED] wrote:
Yes, now the ways to find the child into the border are the ways that
you say, but I think that the
way would have to be transparent, like when we add a new child:
TextField textfield = new TextFieldString(formBorder, name,
new
we can add border.getBodyContainer() to make it easier to find the body container.a couple of notes on wicket 2.0 in general.because of constructor change and the need for IAlternateParentProvider you can no longer assume that
Container c=new Container(...);Label l=new
getBodyContainer() already exists
Juergen
On 10/9/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
we can add border.getBodyContainer() to make it easier to find the body
container.
a couple of notes on wicket 2.0 in general.
because of constructor change and the need for
Yes, this method can be used,
but imagine that I create my own FormBorder, that other people will use
to create different forms.
These developers can add content to this FormBorder, and they will add
this content in the FormBorder
component.
Border formBorder = new FormBorder(this, border);
Hi Juergen Donnerstag,
The example BoxBorderTestPage_7 runs correctly because you only render
the page only one time. The problem is if
you have to reload the page again, because TextField has been removed in
the first rendering and the markup
doesn't find this component in the second
you have the the test case:
public class BoxBorderTestPage_3 extends WebPage
{
private static final long serialVersionUID = 1L;
private final ValueMap properties = new ValueMap();
/**
* Construct.
*
*
*/
public BoxBorderTestPage_3()
{
Border
I've copied BoxBorderTestPage_3 into BoxBorderTestPage_7 and made the
change you suggested. It is working properly. The textield is no
longer printed.
Juergen
On 10/6/06, Alberto Bueno [EMAIL PROTECTED] wrote:
you have the the test case:
public class BoxBorderTestPage_3 extends WebPage
{
12 matches
Mail list logo
