Hi Jeremiah, It appears that this is a bug in the code. The control checker used to validate JDBC control annotation values is enforcing that arrayMaxLength > 0 , but the runtime code is fine with that value and in that particular case will cause the array size to be unlimited.
Go ahead a file a JIRA bug on this issue and I'll start looking at a fix. - Chad On 6/19/06, Jeremiah Johnson <[EMAIL PROTECTED]> wrote:
I have a DB Control that returns an array; the default number max rows is 1024, but I don't want to limit the rows on this call. I can't change arrayMaxLength to zero, so I have to use a magic number in the annotation (i.e. arrayMaxLength=300000). I can put in an enhancement request, but I wonder if there is something that I am missing about requiring the arrayMaxLength to be greater than zero. Is there a reason for the current constraint? Thank you. - jeremiah _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
