Re: Re: Teiid Camel component

2018-07-29 Thread Claus Ibsen
On Mon, Jul 23, 2018 at 1:55 PM, Hiram Chirino wrote: > Hi! > > Nice work! I tend to think lets just do the new teiid component. It keep > things more focused for things like the generated meta data for the SQL and > Teiid components. > Yeah I also think its best to keep it in a new camel-teiid

Re: Re: Teiid Camel component

2018-07-23 Thread Hiram Chirino
Hi! Nice work! I tend to think lets just do the new teiid component. It keep things more focused for things like the generated meta data for the SQL and Teiid components. On Wed, Jul 18, 2018 at 8:04 AM Rafal Korytkowski wrote: > Hey, > > I'm pretty much done with a proof of concept, at which

Re: Re: Teiid Camel component

2018-07-18 Thread Rafal Korytkowski
Hey, I'm pretty much done with a proof of concept, at which you can peek in this commit https://github.com/rkorytkowski/camel/commit/f66eea569963730032713c62f057a5685fea7089 . I've basically extended the SQL component to support a new dataSources parameter, where you can pass multiple data source

Re: Re: Teiid Camel component

2018-06-26 Thread Claus Ibsen
On Tue, Jun 19, 2018 at 12:44 PM, Andrea Cosentino wrote: > Not necessary. We can eventually wrap non OSGi-fied dependencies. > Yes that is correct as Andrea say. There are some components that cannot work in OSGi or does not make sense. However if possible we like to offer Camel components on as

R: Re: Teiid Camel component

2018-06-19 Thread Andrea Cosentino
Not necessary. We can eventually wrap non OSGi-fied dependencies. Inviato da Yahoo Mail su Android Il mar, 19 giu, 2018 alle 12:42, Rafal Korytkowski ha scritto: Hi Claus, Thanks a lot for your guidance! I've got one follow up question. Is it a strict requirement for component's dependen

Re: Teiid Camel component

2018-06-19 Thread Rafal Korytkowski
Hi Claus, Thanks a lot for your guidance! I've got one follow up question. Is it a strict requirement for component's dependencies to be OSGI-fied? On Mon, Jun 18, 2018 at 9:01 AM Claus Ibsen wrote: > Hi Rafal > > Welcome to the Camel community. > It sounds great with a camel-teiid component.

Re: Teiid Camel component

2018-06-18 Thread Claus Ibsen
Hi Rafal Welcome to the Camel community. It sounds great with a camel-teiid component. Writing a Camel component is very open ended and you have a lot of freedom. In terms of how to embed Teiid engine then Camel has no restrictions. If there is one instance in the JVM, then we can let Camel auto