[
https://issues.apache.org/jira/browse/GERONIMO-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873627#action_12873627
]
Jürgen Weber commented on GERONIMO-5183:
----------------------------------------
A work-around is to use the wrapped connection (as suggested as Approach III in
the IBM document cited above):
org.tranql.connector.jdbc.ConnectionHandle ch =
(org.tranql.connector.jdbc.ConnectionHandle)connection;
org.tranql.connector.ManagedConnectionHandle association = ch.getAssociation();
connection = (Connection)association.getPhysicalConnection();
> Support DB2 static SQLJ
> -----------------------
>
> Key: GERONIMO-5183
> URL: https://issues.apache.org/jira/browse/GERONIMO-5183
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: databases
> Affects Versions: 2.2
> Reporter: Jürgen Weber
> Priority: Critical
>
> Currently Geronimo does not support applications that use statically bound
> SQL via DB2 SQLJ.
> If you run Geronimo with the setting
> JAVA_OPTS="-Ddb2.jcc.sqljUncustomizedWarningOrException=2"
> that forces an Exception when an uncustomized SQLJ application is run
> you get
> java.sql.SQLException: Profile is not customized, ProfileName :
> sqlj.CS_SJProfile0
>
> sqlj.runtime.error.RuntimeErrors.raise_UNCUSTOMIZED(RuntimeErrors.java:87)
> This is even thrown when the profile is indeed customized, so it looks like
> the Geronimo DB2 connection wrapper does not support SQLJ.
> This document describes what an app server has to implement to support SQLJ:
> http://www-01.ibm.com/support/docview.wss?&uid=swg27017902
> SQLJ samples for Java are included with DB2 Express-C
> DB2-Express-C/db2/V9.5/samples/java/sqlj
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
