[
https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3492:
-------------------------------------
Ok, I tried adding a different versions of the the "com.force.api" libraries to
the build such that one can easily add a new version, however it proved impossible with
current build system. So, I opted to keep to keep at the same version, but moved the
"com.force.api" to separate module, such that a user can easily provide a new
module and configure the translator and resource-adapter to use the new module.
The pull for changes is here
https://github.com/teiid/teiid/pull/494
I am not completely convinced that there are no other alternatives, but can't think of
any right now.
Provide a mechanism for users to modify the salesforce api version
------------------------------------------------------------------
Key: TEIID-3492
URL:
https://issues.jboss.org/browse/TEIID-3492
Project: Teiid
Issue Type: Feature Request
Components: Salesforce Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
We should provide a mechanism to easily target a different salesforce api version. We
are currently defaulting to v22, which is quite old. The version change must be
controlled as the metadata and the sf jars can be incompatible - if you for example build
a model from v22, then you must stay on v22, and then recreate the model once you want to
move to a later version.
Currently the update procedure would be to copy/modify the salesforce translator module
and have it point to newer wsc and partner api jars (which are java api compatible from
what I have seen) and then change the any salesforce resource adapters to use the new api
url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)