[
https://issues.apache.org/jira/browse/ARTEMIS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15585788#comment-15585788
]
ASF GitHub Bot commented on ARTEMIS-793:
----------------------------------------
Github user graben commented on the issue:
https://github.com/apache/activemq-artemis/pull/839
Well, I think it must be the same callback to avoid the protocol tracker to
start the broker if the datasource is not bounded yet. It's just another
"mandatory" dependency. I might rename the class to more general name, but
separating would end up in a mass.
> Improvement to OSGi integration
> --------------------------------
>
> Key: ARTEMIS-793
> URL: https://issues.apache.org/jira/browse/ARTEMIS-793
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker, osgi
> Reporter: Benjamin Graf
> Fix For: 1.5.0
>
>
> ARTEMIS-714 adds ability to configure external DataSource for usage instead
> of hardcoded driver. This feature should also be usable in OSGi environments
> like Karaf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
