You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/08/19 17:57:15 UTC
[jira] Updated: (ODE-528) Modifying tables from other schemas than
default via extVar
[ https://issues.apache.org/jira/browse/ODE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated ODE-528:
------------------------------
Fix Version/s: (was: 1.3.3)
1.3.4
> Modifying tables from other schemas than default via extVar
> -----------------------------------------------------------
>
> Key: ODE-528
> URL: https://issues.apache.org/jira/browse/ODE-528
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.2
> Environment: All
> Reporter: Rafal Rusin
> Fix For: 1.3.4
>
> Attachments: addSchemaToSelectInsertUpdate.diff
>
>
> I did a following entry for extVar in deploy.xml
> <xvar:externalVariable id="var1">
> <jdbc:jdbc>
> <jdbc:datasource-jndi>myds</jdbc:datasource-jndi>
> <jdbc:table>MYSCHEMA1.MYTABLE</jdbc:table>
> </jdbc:jdbc>
> </xvar:externalVariable>
> My default schema from JDBC connection is MYSCHEMA2.
> When I insert, select or update values in DB, there's a following sql generated:
> insert into MYTABLE values (...)
> however it ought to be:
> insert into MYSCHEMA1.MYTABLE values (...)
> then a "table doesn't exist" error is issued at runtime (note that extVar initialization completes successfully).
> I did some research and fixed it in bpel-runtime/src/main/java/org/apache/ode/bpel/extvar/jdbc/DbExternalVariable.java for ode1x.
> I run extvar test, which completed successfully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.