I'm working on a Camel component for SMSLib (http://www.smslib.org).
This is a Java library for communicating with mobile phones and modems
via a serial connection to send and receive SMS messages using the
Hayes (AT) command set.
I have a working prototype - you can see the source at
https://gith
ver the code?
>
--
View this message in context:
http://camel.465427.n5.nabble.com/Component-Design-SMSLib-tp5432954p5433557.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Alex, smslib is distributed under ALv2, which is great. I didn't check
yet if it's OSGi ready, we're looking for that too. All our components
are now OSGi ready. If smslib isn't we'll try to work with them to make
it OSGi ready or find another solution.
The question I have for you is how to yo
components whose source
>> might provide guidance?
>> * are there any patterns or base classes that I should obviously be
>> using for my Component, Endpoint, Consumer or Producer
>> implementations?
>> * is there anyone else interested in this component who could cast
Hi Hadrian,
I made a mock implementation of the Java serial API specifically for
unit testing: https://github.com/frontlinesms/mock-serial
Do you have any practical advice for developing components, or
resources I should be reading?
Thanks,
Alex
On 26 January 2012 21:22, Hadrian Zbarcea wrot
Alex, it's not really clear what the license is for mock serial, looks
like you didn't think of that yet, maybe?
In a previous mail deckerego gave you some useful advice. It's actually
fairly easy, I'd recommend to just start working on it and look at the
examples. Good starting points are [1]
