Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: Grails-Wave 0.4
-
Component/s: None
-
Labels:None
Description
In case of an single robot implementation the regarding bean should be looked up by its type (instead of a default bean name).
If several robot implementations are found in the services folder an exception should be thrown. In such a case the active robot implementation has to be set via a grails config-property.
Issue Links
| This issue is depended upon by: | ||||
| GPWAVE-6 | Script "CreateWaveRobot" should be able to generate a robot service with name argument |
|
|
|
A class which implements the interface GrailsWaveRobot is now automatically mapped as active robot. If several robot implementations are existing in the service folder one specific robot can be activated by setting the config prop "grails.plugins.wave.robotBeanName"