Anyway, I have different problem with smslib 3.4.3+ (inclusive) - I get some String.substring call exception.
I traced it and it comes to be, that one of the indexes (in readMessages call), I think j = -1, is causing eventual exception, on both GenericATHandler and E160 Handler, when AT response +CMS: ERROR 321 (or 322) is encountered. Is it familiar to You? I switched to 3.4.2 (I do not get the exception). If not, I will post here the stacktrace. Cheers, Tomek On Mar 17, 6:30 pm, Thanasis <[email protected]> wrote: > Great! ;) > > On Mar 17, 4:36 pm, Tomek Jurkiewicz <[email protected]> > wrote: > > > > > And finally, the problem is solved ;) > > > I just came up with the idea right after submitting the previous post. > > Smslib works fine and is great, and JUnit is great testing library, > > but... > > i misused it. Notice, that for every test I get different testing > > class instance, but the gateway is started only once, in one of the > > tests... > > > That is all for now, > > Thank You for the attention ;) -- You received this message because you are subscribed to the Google Groups "SMSLib User Group" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/smslib?hl=en.
