That’s different. We are not implementing JDBC here.
We can still provide a pluggavle interface and have the feature you wrote plugging into artemis. Even adding examples with dependencies towards it. I think it was agreed back then. That’s a different discussion from here though. On Sun, Jan 14, 2018 at 5:26 PM Michael André Pearce < [email protected]> wrote: > Yes. And JDBC the pluggable interface point, JDBC is the api. This is just > as ConnectorService is the pluggable interface that’s a feature. > > Either we have some provided implementations of the pluggable interfaces > that exist within artemis or none at all. > > I really see this as no different. I’m happy for it to be there, but then > I’d like this to applied in general, and to add the kafka ConnectorService. > > > > Sent from my iPhone > > > On 14 Jan 2018, at 21:05, Clebert Suconic <[email protected]> > wrote: > > > > We already have jdnc as a feature. > > > > On Sun, Jan 14, 2018 at 2:47 PM Michael André Pearce < > > [email protected]> wrote: > > > >> My two cents is about consistency of either we do provide integrations > >> with other products out the box or not. > >> > >> If the arguments of people not wanting to add Kafka clients to the class > >> path for ability to link Artemis with Kafka, because it means having to > >> maintain it (see it’s thread for all discussion), I don’t see why > linking > >> Artemis with a specific JDBC vendors product like Apache Derby is any > >> different here. > >> > >> Not that I’m against this, quite the contrary actually if I could add > >> Kafka integration, but I would like this ruling to be consistent. > >> > >> > >> > >> Sent from my iPhone > >> > >>> On 12 Jan 2018, at 23:51, Clebert Suconic <[email protected]> > >> wrote: > >>> > >>> I would like to add an option on artemis create to enable jdbc. > >>> > >>> > >>> By default (if you don't provide any other configuration) it will use > >>> derby by default on the properties. > >>> > >>> > >>> And I wanted to add derby as a dependency on ./lib > >>> > >>> > >>> Anyone against it? > >>> > >>> > >>> so, you would do ./artemis create --jdbc > >>> > >>> > >>> and it would configure derby as an option > >>> > >>> > >>> > >>> (JDBC is not encouraged.. the journal is the best option.. but same as > >>> in ActiveMQ5, some people need it). > >>> > >>> > >>> > >>> > >>> also: I'm trying to understand what I need to change on dep.xml under > >>> artemis-distribution, but I can't make it to work... anyone can give > >>> me a hand on that? > >>> > >>> > >>> > >>> > >>> -- > >>> Clebert Suconic > >> > > -- > > Clebert Suconic > -- Clebert Suconic
