bind a component to null database object

answered 2014-05-11 17:15:46 +0800

nmpallas
115 ● 4
http://nmpallas.wordpress...

You are using form binding. Therefor take into account that there is also an intermediate object generated(POJO like) right? Thus this object is automatically handled by zk framework and you should handle in a specific manner described in the tutorial for form binding. On top of that the @bind() you must have initialized an object to map the @bind values or you are binding to the null object. The solution would be on the @Init to check if the entity you want to represent in the form is null and if such create a new instance of it. A bit different story if you want to do and update in that case on the select of the entity to update you have to map the entity say customer = findCustomer(id) and bind the information to the form using the data binding mechanism.

answered 2014-05-02 09:33:58 +0800

terrytornado
9393 ● 3 ● 7 ● 16
http://www.oxitec.de/

updated 2014-05-02 10:25:46 +0800

PUSH PUSH PUSH!

Please give us an answer with codes for this really 'real world' sample. This should be handled in the documentation.

thanks Stephan

<div form="@id('fx') @init(vm.myForm) @load(vm.selectedRecord) @save(vm.selectedRecord, before='onSave')">

    . . .
<textbox value="@bind(fx.customer.name1) @validator(vm.oxValidatorNotNull)" readonly="true" hflex="1" />

Target unreachable, 'customer' returned null

--> The validator is never called

selectedRecord=project

project.customer.name1

answered 2014-05-06 09:32:53 +0800

terrytornado
9393 ● 3 ● 7 ● 16
http://www.oxitec.de/

Ok. After thinking about the error i should say that this is not a zk or binder issue.

By using a deeper path of the properties like 'project.customer.name' the user/developer must ensure that the bean that holds the property 'name' is not null.

I do it now by setting a new empty 'customer' object before the binder have acces to it.

thanks Stephan