I do that for my current application that allows users to upload documents to the server.
I found that the byte[] fields of our beans were loaded by Hibernate regardless of lazy loading for that property. What I ended up doing was refactoring our objects to put the blobs into a separate child class and use lazy=true for those associations. This only solves the problem of the byte[] properties being loaded when you don't expect it. It doesn't solve any performance issues with it being loaded slowly (as I'm still experiencing myself). On 5/17/06, Chris Chiappone <[EMAIL PROTECTED]> wrote:
Sorry this is a bit off topic but I have a question relating to hibernate in my tapestry application. I have a document object that contains a byte[] field to hold the actually file. It seems as though if the file is relatively large than any access to that object is extremly slow. Is there a work around to this? Or something that I may have missed when it comes to dealing with byte[] in hibernate? Thanks. -- ~chris
