Re: svn commit: r918769 - in /ofbiz/trunk/applications/accounting/widget: ap/CommonScreens.xml ar/CommonScreens.xml

[Adrian Crum <ad...@hlmksw.com>]

doogie@apache.org wrote:
> Author: doogie
> Date: Wed Mar  3 23:27:42 2010
> New Revision: 918769
> 
> URL: http://svn.apache.org/viewvc?rev=918769&view=rev
> Log:
> Fix bad screen definitions, you can't reference a
> value(defaultOrganizationPartyId) before it is set.  That variable was
> being set by the decorator, which hadn't yet run when the initial
> actions were being run for the main screens in these webapps.

Replying to the list, not Adam specifically...

A lesson for the developer community: screen widget actions are run from 
the inside out. The <screen> element's actions are run first, then that 
screen's decorator actions are run, then the decorator that decorates 
it... etc. The last actions to be run are in the global decorator.

Re: svn commit: r918769 - in /ofbiz/trunk/applications/accounting/widget: ap/CommonScreens.xml ar/CommonScreens.xml

[Scott Gray <sc...@hotwaxmedia.com>]

On 3/03/2010, at 4:36 PM, Adrian Crum wrote:

> doogie@apache.org wrote:
>> Author: doogie
>> Date: Wed Mar  3 23:27:42 2010
>> New Revision: 918769
>> URL: http://svn.apache.org/viewvc?rev=918769&view=rev
>> Log:
>> Fix bad screen definitions, you can't reference a
>> value(defaultOrganizationPartyId) before it is set.  That variable was
>> being set by the decorator, which hadn't yet run when the initial
>> actions were being run for the main screens in these webapps.
> 
> Replying to the list, not Adam specifically...
> 
> A lesson for the developer community: screen widget actions are run from the inside out. The <screen> element's actions are run first, then that screen's decorator actions are run, then the decorator that decorates it... etc. The last actions to be run are in the global decorator.

Not entirely true, as Adam's commit shows, the decorator-section actions are run after the decorator actions :-)

Regards
Scott