Changes between Initial Version and Version 1 of Ticket #382

Show
Ignore:
Timestamp:
01/23/10 23:52:04 (16 years ago)
Author:
boomfish
Comment:

OUCH!

This is definitely a serious defect, but the original diagnosis of the cause (related to event types) was incorrect. The actual problem is that messages not tied to a format are always broadcast ahead of format-specific messages, even when that is not the order they are listed in.

Example:

<event-handler name="page.test">
	<broadcasts format="remote">
		<message name="remoteFunctions"/>
	</broadcasts>
	<broadcasts format="html">
		<message name="htmlFunctions"/>
	</broadcasts>
	<broadcasts>
		<message name="eventFunctions"/>
	</broadcasts>
</event-handler>

When the above event handler is executed, the "eventFunctions" message is always broadcast before the other two messages, even when the requestFormat is "remote" or "html".

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #382

    • Property priority changed from normal to high
    • Property severity changed from normal to major
    • Property summary changed from Event-type "before" blocks running after event-handler to Messages not broadcast in correct order when format is used
  • Ticket #382 – description

    initial v1  
    1 Event-type "before" blocks are running after the event-handler of that type. Here is a simple test case. 
     1Format-specific "broadcasts" blocks are running after other broadcasts in the same event. Here is a simple test case. 
    22 
    33[http://www.cf-ezcart.com/modelgluesamples/helloworld/?event=page.test&requestformat=remote]