[
https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3492:
---------------------------------------
It looks like the simplest paths would be removal of the sf jars, or inclusion of multiple
versions.
It looks like even if we could try to make the connector only dependent upon the wsc jar,
that it could still be a problem in that the partner api jar can be version dependent upon
the wsc jar. Also moving the PartnerConnection out of connector layer to be statefully
held in the executions would loose a lot of the benefit of pooling the connections.
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)