Package	org.springextensions.actionscript.mvc.processor
Class	public class MVCControllerObjectFactoryPostProcessor
Inheritance	MVCControllerObjectFactoryPostProcessor Object
Implements	IObjectFactoryPostProcessor

IObjectFactoryPostProcessor that checks the specified IConfigurableListableObjectFactory if it contains an MVCRouteEventsMetaDataPostProcessor. If not, it creates one and adds it to the IConfigurableListableObjectFactory using its addObjectPostProcessor() method.

After that it loops through all the object definitions and examines each class for the presence of [Command] metadata annotations.

Any class can be annotated with [Command] metadata, as long as some metadata keys are provided as well.

What follows are some examples of typical usage:

If an object acts as a command that needs to be executed after a specific event type was dispatched add this metadata to the class:

	 [Command(eventType="someEventType")]
	 public class SomeCommandClass {
	 //implementation ommitted...
	 }
	 

If the command needs to be excecuted after a specific event Class was dispatched then add this metadata:

	 [Command(eventClass="com.events.MyEvent")]
	 public class SomeCommandClass {
	 //implementation ommitted...
	 }
	 

By default the method that will be invoked on the command object will be 'execute', but it is also possible to specify the method like this:

	 [Command(eventType="someEventType",executeMethod="process")]
	 public class SomeCommandClass {
	 //implementation ommitted...
	 }
	 

If more than one command is to be executed after a specific event and it is needed to control the order in which these command will be executed, use the priority key:

	 [Command(eventType="someEventType",priority=10)]
	 public class SomeCommandClass {
	 //implementation ommitted...
	 }
	 

Properties on the Event instance can be mapped to the arguments of the specified execution method or to properties on the command instance.

First there will be a check if the first argument for the specified execute method is of the same type as the associated event, in this case the event is simply passed into the execute method.

If this is not the case the properties of the event or the properties defined by the properties metadata key will be mapped by type to the arguments of the execute method.

Finally, if this is not possible, the properties on the event will be mapped by type to the properties on the command instance.

[Command] annotations can be stacked, so one command class can be triggered by multiple Events.

---