[
https://issues.apache.org/jira/browse/METRON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832544#comment-15832544
]
ASF GitHub Bot commented on METRON-503:
---------------------------------------
Github user jjmeyer0 commented on the issue:
https://github.com/apache/incubator-metron/pull/316
@merrimanr you shouldn't need a config class. If I remember correctly,
Spring is smart enough to pick up instances. As long as its scanning the
package containing the services. If there are multiple implementations for an
interface you should be able to do the following:
```
interface SomeService {}
@Service("SomeServiceImpl")
class SomeServiceImpl implements SomeService {}
@Service("SomeService2")
class SomeServiceImpl2 implements SomeService {}
// usage:
@Autowired
@Qualifier("SomeServiceImpl")
SomeService SomeService;
```
> Metron REST API
> ---------------
>
> Key: METRON-503
> URL: https://issues.apache.org/jira/browse/METRON-503
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Attachments: Metron REST API.docx
>
>
> As discussed on the dev list ([DISCUSS] Metron REST API Requirements), this
> Jira includes adding a REST API to Metron.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
