[
https://issues.apache.org/jira/browse/DERBY-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5497:
---------------------------------
Attachment: ClassResolver.java
Attaching ClassResolver.java. This shows that the behavior of
java.lang.reflect.Array.newInstance( Byte.TYPE, new int[ 2 ] ) varies depending
on whether the platform is Java 6 or OJEC. This appears to me to be an OJEC bug.
This is the root cause of why Derby can't resolve BINARY output parameters on
OJEC.
Here is the output of ClassResolver on Java 6:
type of byte[] = class [B
type of byte[][] = class [[B
java.lang.reflect.Array.newInstance( Byte.TYPE, new int[ 2 ] ) is class [[B
Here is the output of ClassResolver on OJEC:
type of byte[] = class [B
type of byte[][] = class [[B
java.lang.reflect.Array.newInstance( Byte.TYPE, new int[ 2 ] ) is class [B
It would be interesting to know how BinaryArgSimple and ClassResolver behave on
other small device platforms. Thanks.
> Derby cannot resolve BINARY output procedure parameters on CDC/FP 1.1
> ---------------------------------------------------------------------
>
> Key: DERBY-5497
> URL: https://issues.apache.org/jira/browse/DERBY-5497
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: BinaryArgSimple.java, BinaryArgSimple.java,
> ClassResolver.java
>
>
> I will attach a repro showing this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
