[
https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3492:
-------------------------------------
I started out with "34" and then renamed to "custom" such that user
can use this to copy their API jars into this, rather than creating a additional module
etc. My thinking is the user is going to be using at most yet one another version, so
tried to limit the editing as much as possible for them. Another is if I leave as
"34" Teiid will be pegging to another version, we need to maintain for eternity.
So, here 34 is just an example.
New translator/connector is possible, if we can define separate modules for that, with
different Partner API modules. The one issue I can think here is the duplicated name of
the translator/resource-adapter. Currently we do not have way to inject this from a
configuration. Not sure how this affects? Do you think we need to support to have multiple
translators simultaneously ?
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)