Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 22560 invoked by uid 500); 10 Jun 2002 11:57:28 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 22549 invoked from network); 10 Jun 2002 11:57:28 -0000 Message-ID: <014601c21075$cc418820$0500a8c0@hypernexinc.local> From: "Roger I Martin PhD" To: , References: <010301c20fab$692100b0$0500a8c0@hypernexinc.local> <20020610110618.E1980@bremen.dvs1.informatik.tu-darmstadt.de> Subject: Re: getBlob patch for esql Date: Mon, 10 Jun 2002 07:56:04 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, Testing today. Perhaps because reading xsl format is not my strong suit, I am not seeing how the esql:parameter could help push a blob into a database. I'll have to test. I looked at the callable statement example ... {? = foo(1)} ... and it appears like primitives can be wrapped with their corresponding Object types by the esql:parameter. Blobs are an interface and ResultSets return them but when you need to set one, a significant implementation is required. If esql:parameter can do it then the Blob implementation would need to be present in the xsp; when you say it should be done in an action you mean there needs to be something like byte[] buffer=new byte[size]; .... buffer ... ? Which is relevant:) This way an xsp author need not have an implementation of a Blob lying around; It would be implemented and applied internally relieving an xsp author of the task. Also with jdk1.4 there is the java.nio package which allows other arrays of primitives such as double to be treated as a byte array and can then be blobbed. Therefore there could be esql:set-double-array-as-blob, esql:get-double-array-from-blob, etc. I'm having good success with Cocoon; have data flowing from Blobs and queries to svg charts and graphs from a crystallography database which is output from a semiconductor metrology tool. It is very fast and robust. Very close to applying the Java Advance Imaging JAI API to generate image and color contour plots from more scientific data. The tool can be controlled and data can be viewed outside clean rooms with our Cocoon powered webapp. I plan to develop a smaller illustration of what I am doing some time this year and provide it as a Cocoon example. Thanks, Roger ----- Original Message ----- From: "Christian Haul" To: Sent: Monday, June 10, 2002 5:06 AM Subject: Re: getBlob patch for esql > On 09.Jun.2002 -- 07:47 AM, Roger I Martin PhD wrote: > > I needed blobs. I only added getBlob into a byte array. Setting a > > Thanks for your patch. Applied to HEAD. Please cross-check. > > > blob works best if done with a prepared statement. If there is > > interest I can put in PreparedStatement functionality. The life span > > Could you explain this a bit more? ESQL uses PreparedStatements > whenever a is present in the query string. > > > of a prepared statement may be short albeit it would allow Blobs to be > > pushed into a database. If someone knows the future architecture of > > the esql logicsheet please let me know if there are any chunks of code > > needed. > > Storing BLOBs would be nice (although I believe it should be done in > an action and not on a XSP, but that's irrelevant). > > Currently, no changes are planned. > > Chris. > > -- > C h r i s t i a n H a u l > haul@informatik.tu-darmstadt.de > fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org