"new String(dataBytes)" is almost certainly incorrect. Files are binary data - they can't be converted to a string. And even if they are text, this call disregards the question of which encoding the file contents are in.
But more importantly, is there a particular reason you're trying to reinvent the wheel? HTTP file upload is rather complex, and has been comprehensively solved by libraries like Apache Commons FileUpload.
Srinivasa Maddi wrote:reason being, my requirement is demanding me not to go with any third party software though its free.
I really don't understand why ones always come up with such lame excuse? Where does this aversion come from?
Apache Commons FileUpload is a well developed and thoroughly tested file upload API. Honestly, with the knowledge you've shown as far, you would require and waste too much time to achieve the same robustness as Apache Commons FileUpload. That isn't worth the effort.
I child proofed my house but they still get in. Distract them with this tiny ad: