I fixed the issue until you have implemented the fix by subclassing the XA datasource. See below for anyone else wanting to do this.
| import com.ibm.as400.access.AS400JDBCXADataSource; | | /** | * This class is a work around for a JBoss JCA datasource missing feature. For | * more details see Jboss JIRA issue JBAS-4072 | * | * @link http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4011836#4011836 | * @link http://jira.jboss.org/jira/browse/JBAS-4072 | * @since 0.0.1 | */ | public class AS400JDBCXADataSourceWrapper extends AS400JDBCXADataSource | { | | /** | * Serial version uid | */ | private static final long serialVersionUID = 3851238116015754390L; | | /** | * Proxy method to the isTranslateBinary() method of this class. This is to | * allow JBoss XA datasources to set the translate binary property on the | * datasource using setTranslateBinary. In JBoss 5.0.0.Beta1 and JBoss 4 | * versions before 4.2 do not support binary properties on XA datasources. | * | * @return | */ | public boolean getTranslateBinary() | { | return this.isTranslateBinary(); | } | | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011848#4011848 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011848 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
