[teiid-issues] [JBoss JIRA] Updated: (TEIID-55) Salesforce connector doesn't expose standard connection pooling or caching connector properties

Ramesh Reddy (JIRA) jira-events at lists.jboss.org
Tue Feb 10 21:29:54 EST 2009


     [ https://jira.jboss.org/jira/browse/TEIID-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy updated TEIID-55:
------------------------------

          Component/s: Salesforce Connector
        Fix Version/s: 6.x
    Affects Version/s: 6.x


> Salesforce connector doesn't expose standard connection pooling or caching connector properties
> -----------------------------------------------------------------------------------------------
>
>                 Key: TEIID-55
>                 URL: https://jira.jboss.org/jira/browse/TEIID-55
>             Project: Teiid
>          Issue Type: Bug
>          Components: Salesforce Connector
>    Affects Versions: 6.x
>         Environment: SFDC Connector 5.5 GA; MM Designer 5.5.2 0037 Linux
>            Reporter: Greg Haber
>            Assignee: John Doyle
>             Fix For: 6.x
>
>
> The connector framework provides both caching and pooling support for connectors that implement the required interfaces.  The SFDC connector code does indeed implement all of these interfaces.  
> In order to allow users to  fine tune caching or pooling behavior for a connector binding, the connector type's CDK file must also list all of the standard connector framework caching and pooling properties.  The SFDC connector does not currently expose these properties.
> The SFDC connector's CDK file should be updated to include these properties.  Unfortunately we don't document in the connector developer's guide what properties should be defined, but this info can be found in the definition of any of the standard JDBC connector types (Oracle ANSI, etc). These can be marked as "advanced" properties for SFDC as they are for the JDBC connector types.
> The max pooled connections per user property is especially important for SFDC, because of the hard limit on 5 concurrent server side cursors per user in SFDC.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the teiid-issues mailing list