Ticket #300 (new defect)
Messages are not always broadcast in correct order.
| Reported by: | RichardDavies | Owned by: | somebody |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.0.x-next-patch |
| Version: | 2.0.304 | Severity: | normal |
| Keywords: | Cc: |
Description
The documentation for the <broadcast> element states "The <message> tags will be broadcast in the order in which they are defined." It appears that this is not always true. All MG generic database messages are broadcast before any other messages, irregardless of the order they appear in ModelGlue?.xml.
For example, given the following ModelGlue?.xml:
<broadcasts> <message name="ModelGlue.GenericRead"> ... </message> <message name="customFunction" /> <message name="ModelGlue.GenericList"> ... </message> </broadcasts>
the messages should be broadcast in this order: GenericRead?, customFunction, GenericList?. But they are actually broadcast in this order: GenericRead?, GenericList?, customFunction.
The desired outcome would be to follow the documentation and broadcast the messages in the order that they appear in the config file.
![(please configure the [header_logo] section in trac.ini)](/ModelGlue.com/trac.cgi/chrome/site/your_project_logo.png)