<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Cool stuff guys! <br>
<br>
I just caught up on this thread, downloaded the CDK and gave it a spin.
I was able to build the basic project and produce the RAR, neat! This
will be a great way to encourage custom connector development, and I
intend to use it for future work. <br>
<br>
I have a few questions and thoughts about it.<br>
<br>
1. Using the loopback connector code as the template may have some
drawbacks, namely:<br>
a. If the API changes, we have to update (or re-copy) the template code
(perhaps this is automated already?).<br>
b. The developer will have to remove most of the code specific to
loopback, since it wouldn't be useful in any other legitimate
connector. These changes will, of course, break the loopback-specific
tests as well, which will also require effort to fix. This adds up to
extra, unnecessary work for the developer.<br>
c. It includes lots of coding assumptions that the developer probably
wouldn't want initially. For example, the developer is probably going
to want all capabilities set to false initially, and will add support
for capabilities and functions over time. <br>
d. It doesn't use connection pooling, which should arguably be
something included in the boilerplate code (via @ConnectionPooling
annotation).<br>
e. As Ramesh mentioned earlier in the thread, it generates classes
called "LoopbackConnection", etc., when the developer really wants
"MyCustomConnection", where MyCustom is the name of their project. <br>
<br>
As an alternative, did we consider using Eclipse's built-in mechanism
for building boilerplate
classes based on the interfaces of the API, which we could then modify
as needed to create a more generic template?
<br>
<br>
This would allow forward-compatibility with any future changes to the
API. It would produce a simpler set of classes without all the loopback
stuff in there. We could still define a good set of tests based on the
API, not specific to loopback and the results it returns. This might
add up to a more straightforward developer experience.<br>
<br>
2. I wasn't able to run the JUnit tests against the newly-produced
connector; does this work for others? It looks like we are missing
com.metamatrix.query.unittest.FakeMetadataFactory. Presumably this
should be brought in as part of teiid-engine-6.2.0-SNAPSHOT.jar, but I
don't see it there. Did anyone else run into this problem?<br>
<br>
3. Will we make the CDK a Maven project? This seems like a standard for
all other projects in the Teiid trunk (perhaps an undocumented one).<br>
<br>
All in all, this is very cool stuff and I'm looking forward to using
it, thanks all!<br>
<br>
--Mike<br>
<br>
<br>
Ramesh Reddy wrote:
<blockquote cite="mid:1259689617.2921.111.camel@localhost.localdomain"
type="cite">
<pre wrap="">Here is the place holder I created.
<a class="moz-txt-link-freetext" href="http://www.jboss.org/community/wiki/TeiidConnectorDevelopmentEclipsePlugin">http://www.jboss.org/community/wiki/TeiidConnectorDevelopmentEclipsePlugin</a>
You can login using the Jboss.org credentials and edit this page. Also,
if anybody else edits the page you will get notification if you
subscribe to the page.
I have no experience with these template engines, but seems both are up
to the task. I hoping anybody else with more knowledge will chime in.
I agree that with current requirement we may not need to go to extent of
using a template engine, where we can just get the job done using simple
token replacement on the files
Thanks
Ramesh..
On Tue, 2009-12-01 at 10:59 -0600, Sanjay Chaudhuri wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Ramesh,
Absolutely. Let me know how to go ahead with the wiki; I mean
location, existing templates to look at, etc.
I have looked at the eclipse core sources for the templates; it's in
line with what I did. The other template frameworks are more elaborate
substitutions;conditions, etc, which I do not think will be necessary.
You can refer to Eclipse templates here:
<a class="moz-txt-link-freetext" href="http://www.ibm.com/developerworks/library/os-eclipse-pde/">http://www.ibm.com/developerworks/library/os-eclipse-pde/</a> and JET
templates here:
<a class="moz-txt-link-freetext" href="http://www.ibm.com/developerworks/opensource/library/os-ecl-jet/">http://www.ibm.com/developerworks/opensource/library/os-ecl-jet/</a>. Let
me know what you think, and possible use-cases incase you want to move
forward with either one.
There are few things left to be done, which I am planning to take up:
1. Preference Page with installed cdk plugin location or be able to
custom it with no plugins.
2. Wizard for output directory which will keep last few directories.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<pre wrap=""><!---->
_______________________________________________
teiid-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:teiid-dev@lists.jboss.org">teiid-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/teiid-dev">https://lists.jboss.org/mailman/listinfo/teiid-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>