-
1. Re: Custom Connector Development With JCA
jdoyle Mar 3, 2010 10:29 AM (in response to shawkins)I'm not a fan of option #1. The problem with 'the minimum' is that there's still guarantee that the minimum won't cause problems. We saw this recently with the commons-logging. Were we to go this route I thing we need to be specific about what's in the classpath that the connector writer gets. #2 seems too complicated to me. Of these I guess I prefer #3.
~jd
-
2. Re: Custom Connector Development With JCA
shawkins May 17, 2010 6:16 PM (in response to jdoyle)The new split between translator and resource adapter logic ensures that custom development intended to extend our functionality will just utilize our translator jars (of which there will only be a single copy) and/or would be entirely new JCA development, which would be completely independent of Teiid.
The only issues remaining are about dependency management. If a custom translator extension is introduced for examle, it would be placed with the teiid deployer or the lib, which implies that we only support a single version.