[
https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3492:
-------------------------------------
So, in that case there is no real precedent for us to provide version 34 and lock
ourselves in. Providing multiple versions within a single system does require coding
exercise from the user. We can provide a template project with all the required changes
except version information, that user can provide and build and follow deploy
instructions. Is that seems like viable approach?
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)