On Tue, Nov 13, 2012 at 9:52 AM, c031917 <[email protected]> wrote: > This is very bad news. I had asked about mina2 availability in Dec. 2011 and > May 2012. > In May Claus Ibsen stated that mina2 would be in camel 2.10. > > In the meantime I had to use an ugly python workaround to get serial data > and post it via STOMP. > > I was happy that mina2 was mentionend in version 2.10 release notes. > > Now there is suddenly a hint : "camel-mina2 - camel-mina2 is expected to be > refactored in Camel 2.11, so use on own risk of having to migrate". >
You can use camel-mina component. Its stable and works. The camel-mina2 component is in development. The current code is a replica of camel-mina. However we want to refactor the code to allow higher scalability and make the component ready for new functionality The old code is not ready for that. And hence why we mentioned that camel-mina2 is in "development". I would anticipate the common usage of camel-mina2 would not change. It's more the edge cases and advanced stuff that may need some migration in a future release. Most of the work would be under the hood, to tap better in the async routing engine in Camel. All this work has been done in camel-netty. So it's more a question of having time to do this work again in camel-mina2. As an alternative you can use camel-netty which is using the Netty library. Netty is very much like Mina2. And created by past Apache Mina core committers. > It is really difficult to plan a real world camel pilot project when > deadlines on component availability are changed so short-noticed. > Use what's already released and not labeled as "in development". > I would like to contribute but I'm probably not in a position to do that > beyond perhaps trying and testing things. > Well that's the problem. There is only 24 hours per day. And even the people from the Camel team have day time jobs, and all sorts of things to work on. So some community tasks like refactor camel-mina2 may give us time to work on this as often as we would like. > There is a big grey area between using Camel (thus understanding all the > details of "Camel in Action") and > really contributing. In my role as architect and technology scout the depth > of the programming facette is not strong enough. I'm always wondering how > people in all those Open Source projects got this incredible deep knowledge, > this is really admirable. > Well there is a lot of people contributing to Apache Camel. http://camel.apache.org/contributing.html You can do this in any way. Help with docs, help people on mailing lists. Write blogs, write new examples. Fix bugs and submit patches. Or write new components etc. You work don't have to be contributed to Apache. There is plenty of stuff at 3rd party sites at github, or where else. > I will rais a Jira (my first one...) and enter the hold pattern. > > Peter > > > > Christian Mueller wrote >> The camel-mina2 component will be official released in Camel 2.11.0. At >> present, we do not support the serial connector as described at [1] (as >> far >> as I know). >> Feel free to rais a JIRA at [2] so that we don't forget this. And as you >> may know, we love contributions. You can find more about how to contribute >> at [3] and [4]. >> >> The camel-mina component is using Mina 1.x and it's not what you are >> looking for. >> >> [1] http://mina.apache.org/serial-tutorial.html >> [2] https://issues.apache.org/jira/browse/CAMEL >> [3] http://camel.apache.org/contributing.html >> [4] http://camel.apache.org/building.html >> >> Best, >> Christian >> >> On Wed, Nov 7, 2012 at 11:09 AM, c031917 < > >> peter.marx@ > >> >wrote: >> >>> I want to use the long awaited Camel + MINA 2 capability to get serial >>> data >>> onto the message bus. >>> >>> I can't find any documentation or example how to do that. >>> >>> What is the syntax ? something like >>> >>> from ("mina:*/dev/ttyUSB0*:....") >>> .to("jms:operations"); >>> >>> ? >>> >>> 2. question: how do i install >>> >>> camel-mina >>> mina-transport-serial-2.0.2.jar >>> RXTXcomm.jar >>> librxtxSerial.so >>> >>> correctly without maven so that Camel is happy ? >>> >>> I put the last two into jre/lib/i386 and jre/lib/ext according and hope >>> this >>> is also right for camel-mina. >>> >>> >>> Peter >>> >>> >>> >>> -- >>> View this message in context: >>> http://camel.465427.n5.nabble.com/MINA-Serial-what-route-syntax-and-how-to-install-tp5722293.html >>> Sent from the Camel - Users mailing list archive at Nabble.com. >>> >> >> >> >> -- > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/MINA-Serial-what-route-syntax-and-how-to-install-tp5722293p5722640.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
