[
https://issues.jboss.org/browse/AS7-4673?page=com.atlassian.jira.plugin.s...
]
John Mazzitelli commented on AS7-4673:
--------------------------------------
Just as an aside, as per
http://docs.oracle.com/cd/E11882_01/java.112/e16548/oralob.htm#CHDGEIHF
"The SetBigStringTryClob connection property of Oracle Database 10g Release 1 (10.1)
is no longer used or needed."
So if you don't support Oracle 9 and below, you can remove this setting.
This still doesn't solve the more general problem of how do you set any XA datasource
property that is translated to type Properties, but for this specific issue of
SetBigStringTryClob, if you only support Oracle 10g and above, you don't need it (as
per the Oracle documentation linked above).
Failure to set "SetBigStringTryClob=true"
ConnectionProperties in xa-datasource-property
----------------------------------------------------------------------------------------
Key: AS7-4673
URL:
https://issues.jboss.org/browse/AS7-4673
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.1.Final
Environment: Red Hat Enterprise Linux Server release 5.7, JDK 7, Oracle 10g
Reporter: Roger S
Labels: rhq
I found that when the following is set in the standalone.xml of JBoss-7.1.1.Final, it
will have a fatal error:
<xa-datasource....>
....
<xa-datasource-property
name="ConnectionProperties">SetBigStringTryClob=true</xa-datasource-property>
....
</xa-datasource>
The error is:
Caused by: javax.resource.ResourceException: No property editor found for type: class
java.util.Properties
at
org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:601)
at
org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:430)
When I don't define the SetBigStringTryClob setting, all is fine. However, the
SetBigStringTryClob is really important for the application to work correctly. Hope
there's at least a workaround.
This worked without problems in JBoss 4.2.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira