Hi Willem,
Thanks for the reply. I do realize that jsmpp != camel-smpp.
But there is a contains relationship...
camel-smpp 2.13.3
contains-> org.apache.servicemix.bundles.jsmpp-2.1.0_4
contains--> jsmpp 2.10
After closer look, the jsmpp sourcecode at
http://jsmpp.googlecode.com/svn/tags/2.1.0/ does match the jsmpp version
contained in camel-smpp. So now i have the source code :-)
The jsmpp project was migrated to github https://github.com/uudashr/jsmpp in
2009
The resulting fork(s) on github are more active and it is clear that a
number of important problems and fixes have been contributed there.
But the codebase has also diverged ... and it is not possible to just
replace the jsmpp in camel-smpp with the latest from github
The problem from a camel user perspective is that the jsmpp component used
by camel-smpp is
not being actively maintained and now when i have a problem with that
component it is not clear where i should seek/contiribute a solution.
So what is the future of camel-smpp?
is there any ideas to integrate a later version of jsmpp or use another smpp
stack?
/Alan
--
View this message in context:
http://camel.465427.n5.nabble.com/Repo-and-tag-for-the-jsmpp-source-bundled-with-camel-smpp-tp5759380p5759421.html
Sent from the Camel - Users mailing list archive at Nabble.com.
