tag:robotlegs.tenderapp.com,2009-10-18:/discussions/problems/92-rl-and-signals-with-interfacesRobotlegs: Discussion 2018-10-18T16:35:12Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/17094092010-05-17T21:52:13Z2010-05-17T21:52:13ZRL and Signals with Interfaces<div><p>Hi.</p>
<p>I'm fairly new to RL and did not go further than a
testapplication with signals, as I did not get it to work with
modules. But from what I understand with general RL practice, you
should inject the Signal rather than the Signal's content. Then
access IMerchantOrder via SelectOrderSignal. (Same as with
events)</p>
<p>Hope it helps,</p>
<p>Alex</p></div>Alextag:robotlegs.tenderapp.com,2009-10-18:Comment/17094092010-05-17T22:33:53Z2013-06-20T02:43:30ZRL and Signals with Interfaces<div><p>Alex,</p>
<p>Thanks for the reply. You are correct with the general RL
practice. Signals that should be mapped to a command are a bit of
an exception I believe. All the examples inject the signals
properties/payload into the command. For all other signals that are
dispatched (like ones used to update mediators, etc) I do inject
the signal into the class as you mention.</p>
<p>Joel Hooks example on github shows this. Take a look at the
controller directory with the commands. <a href=
"http://github.com/joelhooks/robotlegs-examples-RobotlegsSignalsCafe/tree/master/src/org/robotlegs/examples/signalcommands">
http://github.com/joelhooks/robotlegs-examples-RobotlegsSignalsCafe...</a></p>
<p>Thanks,<br>
Beau N. Brewer</p></div>beaubrewertag:robotlegs.tenderapp.com,2009-10-18:Comment/17094092010-05-17T22:46:47Z2010-05-17T22:46:50ZRL and Signals with Interfaces<div><p>Oh ok. Sorry, my bad.<br>
I studied that example already, but I seem to have
overlooked/forgotten that detail.<br>
Ok, now I'm curious what's the right solution. :)</p></div>Alex