[
https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3492:
-------------------------------------
[~shawkins] Removal would be very confusing for the user, so I would say lets opt for the
multiple versions. We need to keep 22 and then jump whatever is the latest for now. I did
not realize that when we moved to Partner API we completely moved away from the the WSDL
code generation based code. One thing I am not sure I still understand is where wsc jar
dependency coming into picture, is this a run time dependency for partner api?
BTW, if you want I can work on this, just need to understand issue better.
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)