[teiid-issues] [JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090567#comment-13090567 ] 

Steven Hawkins commented on TEIID-3492:
---------------------------------------

> 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 ?

Generally yes, you could need to support multiple versions.  And I don't believe we can have the user change built-in parts of the module structure - that's a dangerous precedent.

One path with kitting multiple versions is that we explicitly have a v 22 and a v 34 translator / resource adapter.  We can also provide the full instructions for creating custom translator / resource adapters that reference whatever version the user needs.

> 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)