<div>Thanks Ramesh,</div>
<div> </div>
<div>Here are the details for extension point definition:</div>
<div><em><font color="#3333ff"><extension point="org.teiid.cdk.core.connector"><br> <cdk <br> id="CDK_6.1.0" ----> Id field: Needs to be unique with respect to other cdk-dist plugin. This is the preferable format<br>
ver="6.1.0" ----> Version # of the cdk-disk<br> description="Teiid - CDK [6.1.0]" ---> The description that appears on Java-Build-Path properties dialog box<br> sdk-dir="teiid-6.1.0-cdk-dist"> ---> dir name of the cdk-distribution<br>
<classpath-jars> ---> Section for the jars those needs to be published and will be in the classpath for the cdk-connector projects<br> <jar dir="/"> ---> Specifies the following jars are located under /<sdk-dir>. The path are relative to /<sdk-dir><br>
<jar-file name="teiid-connector-api-6.1.0.jar"/> ---> Jar file to be published<br> <jar-file name="teiid-connector-sdk-6.2.0-SNAPSHOT-tests.jar"/><br>
</jar><br> <jar dir="/lib"> ---> Specifies the following jars are located under <sdk-dir>/lib<br> <jar-file name="teiid-connector-sdk-6.1.0.jar"/><br>
<jar-file name="teiid-engine-6.1.0.jar"/><br> <jar-file name="teiid-common-core-6.1.0.jar"/><br> </jar><br> </classpath-jars><br> </cdk><br>
</extension></font></em><br><br>The cdk-containers library attached during project creation can be changed after by right clicking on the project and then using Properties -> Java Build Path -> Libraries. Either double clicking on the Cdk Library or pressing the Edit button will bring up a dialog to edit it. A java project can also be attached manually to these cdk-libraries in similar manner.</div>
<div> </div>
<div>The cdk-dist libraries are reversely sorted based on the version number. The default library is always the highest version available in the environment. This means if a project has been created with the default option and 6.2.0 happened to be the highest, then those jars will be used. However at a later date if a new version 6.2.3 is put in the environment; the system will automatically start using it. So if an user needs to stick to a particular version, s/he needs to use the specific version radio button and choose the desired one. The advantage of such a feature is getting benefits of both worlds; ie being able to automatically use the highest version and also being able to use a specific version without any manual intervention.</div>
<div> </div>
<div> </div>
<div class="gmail_quote">On Wed, Nov 4, 2009 at 9:29 AM, Ramesh Reddy <span dir="ltr"><<a href="mailto:rareddy@redhat.com">rareddy@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Congratulations! and great work on delivery of the project. I will take<br>it for test drive and let you know my feedback.<br>
<br>Thanks.<br><br>Ramesh..<br>
<div>
<div></div>
<div class="h5"><br>On Wed, 2009-11-04 at 02:49 -0500, Sanjay Chaudhuri wrote:<br>> I checked in the Cdk plugins for review. It's available from :<br>> <a href="https://teiid.svn.sourceforge.net/svnroot/teiid/tools/cdk-plugin/" target="_blank">https://teiid.svn.sourceforge.net/svnroot/teiid/tools/cdk-plugin/</a>.<br>
><br>> Some details:<br>><br>> 1. There are currently 3 plugin:<br>> - org.teiid.cdk.connector.v610 : Wrapper plugin for<br>> teiid-6.1.0-cdk-dist<br>> - org.teiid.cdk.connector.v620 : Wrapper plugin for<br>
> teiid-6.2.0-M3-cdk-dist<br>> - org.teiid.cdk.core : Main plugin responsible for code generation and<br>> classpath injection<br>><br>> 2. The wizard can be invoked from these perspective right-clicking on<br>
> New in Package-Explorer:<br>> - JavaPerspective<br>> - JavaBrowsingPerspective<br>> - JavaHierarchyPerspective<br>> - J2EEPerspective<br>><br>> 3. The wizard is self-explanatory for creating a CDK Projects<br>
><br>> 4. The sources can be imported, built and executed in eclipse<br>> workspace. The plugins had been tested with Galileo 3.5, 3.6<br>><br>> 5. To build and deploy, the cdk wrapper plugins can be built and<br>
> deployed as individual jars, however the cdk-core plugin must be built<br>> and deployed unjarred.<br>><br>> 6. In order to test new cdk-distributions, similar wrapper plugins to<br>> be built and extension point to be used to publish jars. To understand<br>
> the wirings, plugin.xmls from teiid-6.1.0-cdk-dist and<br>> teiid-6.2.0-M3-cdk-dist to be compared. All the jar paths are relative<br>> to the sdk directory location specified through the extension point.<br>><br>
> 7. Project names are converted to lowercase and prepended with the<br>> word "connector-"; so the project name, LoopBack, will be converted to<br>> "connector-loopback". Any new project with the same name loopback<br>
> (case insensitive) cannot be furthur created.<br>><br>> 8. Errors are currently logged using eclipse infrastructure. Most of<br>> the common project creation errors are handled.<br>><br>> 9. Presently the following features are not available:<br>
> - Maven container integration : The project currently cannot be built<br>> as a maven project; however the maven directory structure exist with<br>> necessary project setting for proper compilation in eclipse<br>
> - CDK Preference<br>><br></div></div>> _______________________________________________<br>> teiid-dev mailing list<br>> <a href="mailto:teiid-dev@lists.jboss.org">teiid-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/teiid-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/teiid-dev</a><br>
<br></blockquote></div><br>