On Wed, Oct 12, 2022 at 7:53 PM Christofer Dutz <christofer.d...@c-ware.de> wrote:
> Hi Claus, > > that sounds great … so I guess I would probably do another discussion on > the PLC4X list and then start a vote as long as I don’t see any negative > responses to this thread here, right? > > Yes corect > Chris > > From: Claus Ibsen <claus.ib...@gmail.com> > Date: Wednesday, 12. October 2022 at 12:11 > To: dev@camel.apache.org <dev@camel.apache.org> > Subject: Re: [DISCUSS] Moving the Apache PLC4X Camel components into the > Apache Camel project? > Hi Chris > > Thanks for reaching out to us. > > I assume its this code that you want to move to Apache Camel > > https://github.com/apache/plc4x/tree/develop/plc4j/integrations/apache-camel > > That seems very doable as it's a smaller component (camel code vice) and > it's up to date with the latest Camel release, so the move of code and > adjustments afterwards would be minimal. > > > > > On Wed, Oct 12, 2022 at 5:53 PM Andrea Cosentino <anco...@gmail.com> > wrote: > > > Hello, > > > > Moving the component to Camel is more than welcome. > > > > We might help with the migration for sure. > > > > Thanks for reaching out to us. > > > > Il giorno mer 12 ott 2022 alle ore 16:06 Christofer Dutz < > > christofer.d...@c-ware.de> ha scritto: > > > > > Hi all, > > > > > > after a few chats at last week’s ApacheCon, I would like to start a > > > discussion on moving the Apache PLC4X Camel components into the Apache > > > Camel project. > > > > > > With these components, we are able to read data from industrial > > > programmable logic controllers or other hardware and stream that into > > Camel > > > or consume data in Camel and write this information back into the PLCs. > > > > > > We started off building the components in PLC4X, but I think there are > > > several benefits for bringing it to the Camel project such as: > > > > > > * Having the components listed in the official “Camel Store” for > easy > > > setup > > > * Having the components maintained to keep them up to date with > > > changes in Camel > > > > > > I know that on the other side, if we moved the components here, the > Camel > > > project now would need to react to changes in the PLC4X project, but > our > > > Read/Write/Subscribe API has generally been pretty stable and the ones > > > we’re currently fine-tuning (Auto-Discover, Browse) are ones the > > components > > > not yet utilize. > > > > > > I’d also be willing to come along and take care of maintaining PLC4X > > > related changes. > > > > > > What do you folks think? We had discussed this in the Apache PLC4X > > project > > > before and then it was general consensus, that we’d love to do this. > But > > I > > > would re-activate that discussion on our list, if there’s interest on > > your > > > side. > > > > > > Chris > > > > > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
