Originally posted by Andrew Patzer:
I am pretty strict when it comes to MVC and I do advocate a Type II model to JSP/Servlet development. I understand some situations may not call for it, but I find that most situations can benefit from it.
I do access model objects directly from JSP's. My controller servlet calls an action object, which generates a JavaBean (model), then adds the bean to the request attributes, and forwards the user to a specific JSP. The JSP then grabs the bean and uses it. I think this is a clean approach, but I can't say for sure that it's the best one. It's just the way I prefer to do it.
Originally posted by Andrew Patzer:
Regarding the questions about MVC -- I believe that using a model view controller framework is by far the best way to approach web development. It allows not only for reuse of key components, but it also gives you a very flexible 'plug-n-play' architecture that allows you to insert functionality into the request stream.
Originally posted by Budi Kurniawan:
- A complete guide to file upload, from the HTTP request to obtaining the uploaded file.
Originally posted by Junilu Lacar:
My only request is that you all please keep posts on-topic for this forum. All posts that are off-topic will be closed and moved as soon as I see them. Closed threads will be deleted on Thursday so any posts in them will not be eligible for the drawing.
If a native implementation is present it is, by default, the preferred implementation. But if the nature of the sources and parameters of the operation are incompatible with the native operation then processing will revert to Java code. In general the following minimum requirements must be adhered to for the mediaLib native implementation of an operation to be executed:
* All sources must be RenderedImages.
* All sources and destination must have a SampleModel which is a ComponentSampleModel and a ColorModel which is a ComponentColorModel or no ColorModel (i.e., it is null).
* All sources and the destination must have at most 4 bands of pixel data.
* If Interpolation type is one of the arguments to the operator, then native acceleration is available only for Nearest, Bilinear, Bicubic and Bicubic2 cases. Additionally for byte images InterpolationTable is also supported for native acceleration.