[
https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-3492.
---------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
Resolution: Done
I found a little hack in the build where I could add another version without much hassle
to the build.
Designed the modules and their dependencies such that Partner API modules can be easily
replaced with user's choice of API modules and update the translator and
resource-adapter. This model will work as along as Salesforce keeps the compatibility of
the API intact between version. If that is changed then this option will end up in errors
during runtime.
Added version 34 as sample version to the build.
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: Ramesh Reddy
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)