Can I have multiple extension of AnnotateDataBinderInit for different zul pages?

answered 2010-04-05 19:56:54 +0800

madruga0315
937 ● 2 ● 12

This error means that both person and stock binders are handling the same component.

As far as I remember, you can use both, but have to specify the root component for each, and make sure they're not interlacing.

Pseudo code not tested warning:

<?init class="databind.PersonInit" arg0="./pnlPersons" ?>
<?init class="databind.StockInit" arg0="./pnlStocks" ?>

<window>
    <panel id="pnlPersons"> components here </panel>
    <panel id="pnlStocks"> components here </panel>
</window>

answered 2010-04-06 07:34:51 +0800

madruga0315
937 ● 2 ● 12

Based on the error message: "Cannot be covered by this Data Binder again. Page:LayoutPageId", both binder are covering the Page component, which is the root component, so the arg0="component" is not really working, and the binder is then attaching itself in the page instead of the component. I would put some break points on the binder init class, and really see what's going on in the background.

For your other comment, I believe that the data binding part of ZK is probably the most complex part, the part the most of us will struggle a bit. But even with all this complexity, I think that ZK is far more easier and intuitive than others web frameworks. I really don't think that our team would have a better productivity rate with other web ui framework.

answered 2010-04-06 10:05:12 +0800

robertpic71
1275 ● 1

Hi,

1.)

meanwhile, i prefer to create my own databinder-instance.

Here is some code form my standard-controller:

@Repository("mainController") 
@Scope("prototype")
public class Main extends GenericForwardComposer {

	private AnnotateDataBinder binder;
	...
	/*
	 * Model und Servicedata
	 */
	
	MainModel model;
	
	@Override
	public void doAfterCompose(Component _win) throws Exception {
		super.doAfterCompose(_win);
		win.setVariable("model", model, false);  // make models visible for the databinder [1]
		binder = new AnnotateDataBinder(_win);
		...
	}

Note: There is no <?init..> inside my zul.

2.) 2 binders for the same data
I've not tested this, maybe it works. However i do not need this, because it is possible to scope the databinder.

i.e.
<grid id="input">
<rows>
<row>* Lastname: <textbox id="lastname" value="@{model.PersonBean.lastname}" constraint="no empty" width="300px" /></row>
<row>* Firstname: <textbox id="firstname" value="@{model.PersonBean.firstname}" constraint="no empty" width="300px"/></row>
....
</rows>
<textbox id="other" value="@{model.CityBean.name}"/>
...

2a.)
binder.loadComponent(input);

load all Elements under "input", because "other" is outside "input" it will be not loaded!

2b.)
binder.loadAll();
load all Elements

2c.) of course, this works for binder.saveComponent() also

3.) For new windows, create a new databinder - no troubles at all

/Robert