Resizing ordimage on the fly

Question

I have a table with an ordimage column. I am using a servlet to display the image on my jsp page. It is for an online assessment application. It has several questions that have images, but because of size constraints, we are scaling down the images to fit in a certain window, but we also have a link so they can see the full-sized image if needed. So I need to keep the original image size. I have been using the process method.
otQuestionsViewRow.getQuestionImage().process("maxScale=510,400")
for a small user group this works ok, but I get a record locking situation when I get too many people accessing the same question at the same time. My thoughts were to use the copy or clone methods, but I have not been able to figure out how to implement, my question is what would be the best way to accomplish this? Should I continue working with one of these two methods or is there something else I can do.
This is my code I am using currently:
if (otQuestionsViewRow.getQuestionImage() != null )
imageWidth = otQuestionsViewRow.getQuestionImage().getWidth();
if (imageWidth > 510) {
otQuestionsViewRow.getQuestionImage().process("maxScale=510,400");
image = otQuestionsViewRow.getQuestionImage();
response.setContentType( image.getMimeType() );
OutputStream out = response.getOutputStream();
out.write( image.getDataInByteArray() );
out.flush();
}

Answer 1

Lars  -
As it is designed today, the logger requires that the SQL statement contain an INSERT command. If it is not found, I do not believe that on-the-fly logging will work if the schema defines a foreign key to the UUT record.
Now, I have not tried this, but if the step result statements in the schema do not define their UUT_RESULT columns as foreign keys, the logger will just assume that they are data that you will provide, and it will not attempt to log a placeholder for the UUT record. So I believe you can then set the expression for the UUT_RESULT in the step results to assign the UUT key and the logger will just log it as a value. The database schema will likely have a constraint, but if you pre-create the record as you were suggesting, the constraint will be satisfied when you log the step result. Lastly when the UUT completes, the logger will just log the values using the UPDATE statement that you supplied.
Note that we already do have a internal suggestion/problem tracking issue (ID 47056), specifically to add support to log more than just the key for the UUT result and parent sequence call steps, but we have not determined how easy that would be and whether there are any backwards compatibility issues.
Scott Richardson
National Instruments