I tried to create a JIRA first but could not figure out to create one. Anyway I was pretty sure it was just not using the API correctly. And it ended-up being the case now it work perfectly on Linux but I still have some issue on Solaris and windows.
I agree that it should throw an exception which is more specific to deft instead of just doing a null pointer exception. I was also thinking about introducing another class which create an new instance of AsynchronousHttpClient for each request so you don’t need to do it yourself and so it can be optimized by the framework latter on. Thanks a lot to everybody this project seem really alive hope it will continue to be. Regard Maxime Caron -----Original Message----- From: Emmanuel Lecharny [mailto:[email protected]] Sent: Tuesday, November 08, 2011 5:39 PM To: [email protected] Subject: Re: I think i found a bug in the latest version 0.4.0 On 11/8/11 8:04 PM, Roger Schildmeijer wrote: > Hi Caron, > > You should create a new AsynchronousHttpClient for each new request (The > async http client can't handle concurrent request atm). > So above client.fetch(..) you should add > > AsynchronousHttpClient client = new AsynchronousHttpClient(); > > > HTH > Roger Schildmeijer > > Ps. Don't hesitate to contact us again if experience other problems. irc > (#deft, freenode) or here on the mailing list. Ds. JIRA... This is where such errors should be logged. Don't hesitate to ask the user to flll one, even if it's invalid : many other users ay check the JIRA before asking on the ML, and taht would spare you a lot of time. And a NPE should not be considered as a user error : it deserves a correct error message in the framework, IMO. My 2 cts... -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com -------------------------------------------------------------------------- NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers. If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing.
