Jaikiran Pai wrote:
It will default to the value that's set for the javax.servlet.context.tempdir context attribute, which is set by the server.
I wish to validate the extension of the file being uploaded.
Maneesh Godbole wrote:Do you wish to validate the file extension(s) of the file being uploaded (tar.gz/zip) or the file extension(s) of the file(s) inside the compressed file being uploaded?
Thank you. I will do that. Thanks for your patience and help.
Ulf Dittmer wrote:There may be something that gets logged, but is not visible due to the logging level being set too high. You can find out what happens be stepping through the servlet container's code in your debugger.
Yeah, this is also right. I agree with you.
Ulf Dittmer wrote:Note that I said "The most likely scenario". It's perfectly possible that something else happens - I've never tried to find out, especially as this is likely dependent on the server you're using. So whatever happens on the server you're using may not be what happens on some other server.
Yes, the servlet finishes without any exception. So you mean to say that after the servlet's execution finishes the control is transferred to some other lower level class which might throw an exception but is not being logged. Am I right?
Ulf Dittmer wrote:So your code writes (and flushes) an OutputStream that is connected to a connection that is no longer valid, and the servlet code finishes without an exception? That's interesting, and not what I would have expected. Of course, servlets operate on a higher level than sockets, and need not necessarily be aware what happens underneath.
If the server throws an exception definitely it will be logged in the log files and I don't see one in my logs.
Ulf Dittmer wrote:The most likely scenario is that the connection gets closed, which the server will notice (possibly by an exception being thrown) when trying to send a response. Before that
If the processing of the request continues then definitely it is a serious issue. Why is the design like this. Any guess.
Ulf Dittmer wrote:the processing of the request will continue as it normally would.
No I was speaking about java List not and array.
It seems to me that when you are thinking "list" you are really thinking array
What? An array? But why? I mean I want to know the advantage and how returning a List is bad. What if I want to return list of employees, their count, start index, end index for example.
Ulf Dittmer wrote:No, Bill is suggesting an array: Employee