Go on, give us a clue! What is the problem that you experience? It is important to give people the information they need to help you, otherwise you generally won't get any help. Saying you get "a problem" is not helpful.
Only one small issue was immediately apparent to me, and it's certainly not the cause of your main problem. You check "out" for null at one point, but by then you've already tried to use "out". So you either need to check for null earlier, or not at all. The current check is pointless.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Joined: Jul 31, 2006
Thanks Peter ... You mean I have to check "out" whether it null or not for the first time?
We're pleased to have you here with us in the Servlets forum, but there are a few rules that need to be followed, and one is that proper names are required. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.
In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.
Originally posted by azie: Thanks Peter ... You mean I have to check "out" whether it null or not for the first time?
OutputStream out= null; out = response.getOutputStream();
Is this correct?
When you call an API method, you need to find out whether it can return null. If it can, you have to check for null after calling and do the right thing (which you have to decide - there's no fixed rule) if null has been returned. If it can't return null, do not bother checking, as this will waste CPU time and memory, and confuse future maintainers of your software.
"azie", Ben's request that you change your display name to adhere to JavaRanch standards was not a suggestion. Valid display names are mandatory for participation on the Ranch. Please change your display name as instructed prior to your next post.
Be aware that accounts with invalid display names are removed.