This content has been marked as final.
Show 5 replies
-
1. Re: Page parameters propagation DELAY
joblini Jan 4, 2009 3:41 AM (in response to recool.qiao_haibo.hotmail.com)Try setting @Out(required=false)
Outjection will be performed after any method call, in your example, this would be setDoorType.
-
2. Re: Page parameters propagation DELAY
recool.qiao_haibo.hotmail.com Jan 4, 2009 4:58 AM (in response to recool.qiao_haibo.hotmail.com)Thanks for ur reply.
After adding required=false, there isn't much difference. And I discovered that:
In my example,
1. setDoorType() was indeed invoked before getCurrentDoor()
2. However setDoorId() and setTemplate() were invoked after the outjection was done, which is a bit weird to me.
Is there any way to force the parameter propagation?
HB -
3. Re: Page parameters propagation DELAY
joblini Jan 4, 2009 5:07 AM (in response to recool.qiao_haibo.hotmail.com)Outjection is performed after any method call.
-
4. Re: Page parameters propagation DELAY
joblini Jan 4, 2009 5:13 AM (in response to recool.qiao_haibo.hotmail.com)<param name="doorType" value="#{scDoorOrder.doorType}"/> <param name="doorId" value="#{scDoorOrder.doorId}"/> <param name="template" value="#{scDoorOrder.template}"/> <action execute="#{scDoorOrder.onLoad}"/>
will result in this:
setDoorType is called. currentDoor is outjected. setDoorId is called. currentDoor is outjected. setTemplate is called. currentDoor is outjected. onload is called currentDoor is outjected.
-
5. Re: Page parameters propagation DELAY
recool.qiao_haibo.hotmail.com Jan 4, 2009 7:17 AM (in response to recool.qiao_haibo.hotmail.com)I got it, thank you very much.
HB