Due to various reasons I can’t use the built in reconnect methods in SMACK. As a result I am reconnecting myself by calling connect(). Normally it works fine, but if there is an Exception thrown when it calls login(…) (a conflict for example), that exception is swallowed (printed to System.err) instead of thrown back up to the caller of connect().
Why is that being done? It seems really useful to have that exception back where connect() is being thrown. It seems like a bug to me. I’d really hate to have to make my own branch of the source just to make that change.
Really anywhere an exception is just being printed instead of dealt with meaningfully or sent up to the caller is a bug IMHO.
Just wanted to report that. Thanks,
Matt