I'm using the com.oreilly.servlet class, and wanting to 'tweak' one of its classes.
For a very quick background on *exactly* what I'm trying to do, you can check this article
My problem is with the MultipartWrapper. Code of interest: The problem is the call to MultipartRequest(req, dir).
MultipartRequest has about 8 constructors. I need the one that allows me to set a file upload size larger than 1 MB (which is the default when you don't specify). So I thought to do the following: If I leave the call to super(req, dir) commented out, I get this error:By uncommenting that call to super(req, dir), it compiles. But unfortunately, because of what super(req, dir) *Does* to the req object, I cannot use it again in the next line.. (actually it compiles fine, but runtime you get "unexpected end of part".. which is what happens when you try to read a request object twice, but beyond the scope of the question...
The compiler will insert a call to the no-args constructor, when you don't specify one. But if I specify one, it breaks the functioning of the class. Is there a way around this? Am I doing something that is fundamentally wrong (trying to add constructor signature in a subclass) or is this just a side-effect of the *req* object being ... flakey.. when its touched more than once?
For a very quick background on *exactly* what I'm trying to do, you can check this article
My problem is with the MultipartWrapper. Code of interest: The problem is the call to MultipartRequest(req, dir).
MultipartRequest has about 8 constructors. I need the one that allows me to set a file upload size larger than 1 MB (which is the default when you don't specify). So I thought to do the following: If I leave the call to super(req, dir) commented out, I get this error:By uncommenting that call to super(req, dir), it compiles. But unfortunately, because of what super(req, dir) *Does* to the req object, I cannot use it again in the next line.. (actually it compiles fine, but runtime you get "unexpected end of part".. which is what happens when you try to read a request object twice, but beyond the scope of the question...
The compiler will insert a call to the no-args constructor, when you don't specify one. But if I specify one, it breaks the functioning of the class. Is there a way around this? Am I doing something that is fundamentally wrong (trying to add constructor signature in a subclass) or is this just a side-effect of the *req* object being ... flakey.. when its touched more than once?