Congratulations! and great work on delivery of the project. I will take it for test drive and let you know my feedback. Thanks. Ramesh.. On Wed, 2009-11-04 at 02:49 -0500, Sanjay Chaudhuri wrote:

Sanjay, I checked out the projects and built using Eclipse RCP Plugin development version. All these worked fine. Once I have the plug-ins compiled I right clicked in the "core" project and asked it run as "eclipse" application. It came up with new eclipse which has "cdk" new project wizard. Which is by way very neat. I typed in the name of the project and package and it created a new project with the name "connector-xxx" and copied all the loopback classes. This is very good start. For the next steps we should do something like below. Say we have the below as the sample class /** * License */ public class LoopbackConnector extends Connector{ public Connection getConnection(){ //TODO: fill in the code } } then we need to make this into a template such as /** * ${License} */ public class ${project-name}Connector extends Connector{ public Connection getConnection(){ //TODO: fill in the code } } where the "loopback" code is only used to drive the initial "template" then we derive the actual code by replacing the variables in those templates. These variables can be eclipse defined or we can come up with some. so, once the variable replacement is done the code will look as actual java code. This should be the function of the wizard. We do not need to take all methods as is from "looback" code either, we just need to put in connector-api required method stubs. 2) Let's only maintain one version of the "cdk" in the svn repository for now. As we talked before we really need to point this plugin to a "teiid" install somewhere on the disk and it should resolve it. Or on the wizard we can ask the user to point to a CDK distribution, that way we do not have to have these in the SVN at all. Keeping these in SVN is verbose. 3) "ra.xml" need to be treated same way as template. This needs to live in "src/main/rar/META-INF/ra.xml". 4) Then we need to bundle this project into a RAR file. Where the format looks like connector-custom.rar \--connector-custom.jar \--dependencies-1.jar \--dependencies-2.jar \META-INF ra.xml We need to write a some kind of "export" function of this. If we do not want write custom "export" may be we can just use eclipse "maven" plug-in to build this for us. All that takes is invoking a "run-as" on the pom.xml, which may be sufficient. Or there may be eclipse plugin to build a RAR file? Let me know what you think? Thanks again for all your help. Ramesh..

Sanjay, It will take me another week or little more to give you a copy of the template that matches with the new 6.3 Connector API. If you want go ahead with the variable replacement framework for this based on my previous email with some sample code. Yes, "ra.xml" will also need to be variable replaced. I was thinking if there is way you could use the Eclipse Java code template mechanism. Just a suggestion. connector-custom.jar --> will be the jar file of the all the custom connector classes that user generated using the plug-in + his/her additions. dependencies-${n}.jar --> these are any jar file that connector is dependent upon. So, any runtime dependencies for this connector. Lets say if user is writing a connector to "Oracle", then the jar file that contains the JDBC driver for "Oracle" will be a dependent jar for this connector. The user will add the dependent jars as part of building the connector, just like any other Java project. Then as part of building the RAR, we should build the "connector-custom.jar" and add it to RAR and then also add all the dependent JARs that are defined in the build. If we need to use "temp" directory for keeping the intermediate results we should do that, then delete it once we have the RAR file. Ramesh..

On Mon, 2009-11-09 at 11:16 -0500, Sanjay Chaudhuri wrote: I was thinking about using template variables like in "code" completion in java editor. Frankly I do not know much about Eclipse JET, I have written code generators before but always used my own techniques. You are correct as the number of variables for us would be a small set. So, use what you think is appropriate. Having a "lib" directory is just choice on part of the user. What I am saying is, during a normal Java project setup a user can define a set of dependent jars that project needs. We need to use this list and package them in RAR file generation.

Hi Ramesh, Will be integrating the RAR Export pretty soon along; am almost there. I want to make sure the generated rar contains *connector-custom.jar* and *NOT * expanded *.class* files with packages. Thanks Sanjay On Mon, Nov 9, 2009 at 4:45 PM, Sanjay Chaudhuri <email2sanjayc(a)gmail.com&gt;wrote:

That fine; will update with your new ones whenever you send it across. As of now will be using the existing one for my development. Please confirm on the custom-jar instead of splited class files. Making a jar will be some additional code, on top of the exporting a rar with the required resources. Few other questions: 1. The other question I have is, will compilation errors prevent from building the rar or do I export with whatever I get compiled ? 2. Does the custom connector sources gets exported too as connector-src.zip ? If yes, does it go inside the connector-custom.jar if we have one ? The operation currently will be a right-click export; will not have any wizards as of now atleast. The generated RAR will put on the root of the current workspace project. Thanks Sanjay On Mon, Nov 23, 2009 at 12:50 PM, Ramesh Reddy <rareddy(a)redhat.com&gt; wrote:

Hi Ramesh, Please find attached the generated rar for your review. The original project had an additional custom-lib directory with 2 jars. Let me know if you find the packaging proper. Thanks Sanjay On Mon, Nov 23, 2009 at 4:37 PM, Ramesh Reddy <rareddy(a)redhat.com&gt; wrote: