[jboss-jira] [JBoss JIRA] (JBJCA-943) Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property

[Jesper Pedersen (JIRA)]

     [ https://issues.jboss.org/browse/JBJCA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesper Pedersen moved AS7-4673 to JBJCA-943:
--------------------------------------------

              Project: IronJacamar  (was: Application Server 7)
                  Key: JBJCA-943  (was: AS7-4673)
             Workflow: jira  (was: GIT Pull Request workflow )
    Affects Version/s: 1.1.0.Beta3
                       1.0.13.Final
                           (was: 7.1.1.Final)
          Component/s: JDBC
                           (was: JCA)

    
> Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property
> ----------------------------------------------------------------------------------------
>
>                 Key: JBJCA-943
>                 URL: https://issues.jboss.org/browse/JBJCA-943
>             Project: IronJacamar
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 1.1.0.Beta3, 1.0.13.Final
>         Environment: Red Hat Enterprise Linux Server release 5.7, JDK 7, Oracle 10g
>            Reporter: Roger S
>            Assignee: Stefano Maestri
>              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