1. <config-property> is defined as: description*, config-property-name, config-property-type, config-property-value? Will the ra.xml editor show a 4 column table only with the config-properties ? This would mean that we DO NOT show the whole xml in a nested tree.

2. Capability to add/delete description, property-name, property-type, property-value which would update ra.xml on the fly.

3. Do we need to validate schema restrictions ?

4. Which properties class the get/set to be added ? Is the properties class generated if it's not in the workspace ?

5. How to use the optional <config-property-value> attribute in the properties class ?

Great; these answers will help me to move forward. Shall come back incase I need additional info. I shall replace the loopback classes with the 5 template java classes I see on the Cdk connector for now. Thanks Sanjay On Tue, Dec 15, 2009 at 11:48 AM, Ramesh Reddy <rareddy(a)redhat.com&gt; wrote: > > Good questions. > > > 1. <config-property> is defined as: description*, > > config-property-name, config-property-type, config-property-value? > > Will the ra.xml editor show a 4 column table only with the > > config-properties ? This would mean that we DO NOT show the whole xml > > in a nested tree. > I do not think showing the whole tree is necessary. Our main aim here is > to add "user" properties that are specific to the connector needed to be > added easily. Those are "config-property" section. So, if we can add > those through GUI that is enough to satisfy our need. You can leave > manual editing of "ra.xml" up to the user. We do not want hide the > resulting file either. > > > > > 2. Capability to add/delete description, property-name, property-type, > > property-value which would update ra.xml on the fly. > Yes. Note that "config-property-value" denotes a "default" value > supplied by the user. Also, "config-property" can have multiple > "description" fields. May be you can let them add multi-line description > and add each line as one "description" element inside "config-property". > Here is sample block. > > <config-property> > <description>Is Immutable</description> > <description>True if the source never changes.</description> > <config-property-name>Immutable</config-property-name> > <config-property-type>java.lang.Boolean</config-property-type> > <config-property-value>true</config-property-value> > </config-property> > > Note the "config-property-type", they can be any "java.lang" objects, > may be you want to provide a "drop down" selection on that field. > > > > > 3. Do we need to validate schema restrictions ? > Yes/no, the ra.xml schema is defined by JCA 1.5 spec. You can find it > here > http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd > > If we let user manually edit, Yes. Which I think we should. > > > > > 4. Which properties class the get/set to be added ? Is the properties > > class generated if it's not in the workspace ? > The template will have a configuration class with name like > "xxManagedConnectionFactory.java". Check here for the template classes I > promised. I will keep them updated if any changes and let you know. > > http://anonsvn.jboss.org/repos/teiid/branches/JCA/connectors/sandbox/conn... > > > > > > 5. How to use the optional <config-property-value> attribute in the > > properties class ? > > Properties call will only have getters and setters. By having the > "config-property-value" > in the ra.xml file the container will automatically assign them on startup > of connector. > > > Thanks. > > Ramesh.. > >

I find these files are missing from the template: - pom.xml - assembly/bundle.xml - main/resources/{connector-name}.xml Thanks Sanjay On Tue, Dec 15, 2009 at 12:24 PM, Sanjay Chaudhuri <email2sanjayc(a)gmail.com&gt; wrote: Great; these answers will help me to move forward. Shall come back incase I need additional info. I shall replace the loopback classes with the 5 template java classes I see on the Cdk connector for now. Thanks Sanjay On Tue, Dec 15, 2009 at 11:48 AM, Ramesh Reddy <rareddy(a)redhat.com&gt; wrote: Good questions. > 1. <config-property> is defined as: description*, > config-property-name, config-property-type, config-property-value? > Will the ra.xml editor show a 4 column table only with the > config-properties ? This would mean that we DO NOT show the whole xml > in a nested tree. I do not think showing the whole tree is necessary. Our main aim here is to add "user" properties that are specific to the connector needed to be added easily. Those are "config-property" section. So, if we can add those through GUI that is enough to satisfy our need. You can leave manual editing of "ra.xml" up to the user. We do not want hide the resulting file either. > > 2. Capability to add/delete description, property-name, property-type, > property-value which would update ra.xml on the fly. Yes. Note that "config-property-value" denotes a "default" value supplied by the user. Also, "config-property" can have multiple "description" fields. May be you can let them add multi-line description and add each line as one "description" element inside "config-property". Here is sample block. <config-property> <description>Is Immutable</description> <description>True if the source never changes.</description> <config-property-name>Immutable</config-property-name> <config-property-type>java.lang.Boolean</config-property-type> <config-property-value>true</config-property-value> </config-property> Note the "config-property-type", they can be any "java.lang" objects, may be you want to provide a "drop down" selection on that field. > > 3. Do we need to validate schema restrictions ? Yes/no, the ra.xml schema is defined by JCA 1.5 spec. You can find it here http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd If we let user manually edit, Yes. Which I think we should. > > 4. Which properties class the get/set to be added ? Is the properties > class generated if it's not in the workspace ? The template will have a configuration class with name like "xxManagedConnectionFactory.java". Check here for the template classes I promised. I will keep them updated if any changes and let you know. http://anonsvn.jboss.org/repos/teiid/branches/JCA/connectors/sandbox/conn... > > 5. How to use the optional <config-property-value> attribute in the > properties class ? Properties call will only have getters and setters. By having the "config-property-value" in the ra.xml file the container will automatically assign them on startup of connector. Thanks. Ramesh..

> Using the template classes, I get few compilation errors. Which > cdk-dist version do I need to use ? > The required API classes are still in the JCA branch. This is part of the container integration I am currently working on. > I have checked in the required changes to reflect the latest templates > as per your last email. Please review and let me know, which libraries > to use to fix these errors. Try the libraries I am attaching. Also, you need the JCA Connector API jar, you can download this from http://java.sun.com/j2ee/connector/download.html Let me know how this works. Ramesh..

Can attach the generated classes, I did not have a way to test when I wrote these. Thanks Ramesh.. On Wed, 2009-12-16 at 09:56 -0600, Sanjay Chaudhuri wrote: > I had to add teiid-engine-7.0.0-SNAPSHOT.jar to get rid of all import > errors. However compilation errors still exists in > {connector-name}Execution.java > 1. Arrays.asList(query.getColumnTypes()) in > determineOutputTypes(...) : Cannot convert from List<Class> to > List<Class<?>> > 2. In getValue(...) 'cal' cannot be resolved > > Thanks > > Sanjay > > On Wed, Dec 16, 2009 at 8:14 AM, Ramesh Reddy <rareddy(a)redhat.com&gt; > wrote: > > > Using the template classes, I get few compilation errors. > Which > > cdk-dist version do I need to use ? > > > > The required API classes are still in the JCA branch. This is > part of > the container integration I am currently working on. > > > I have checked in the required changes to reflect the latest > templates > > as per your last email. Please review and let me know, which > libraries > > to use to fix these errors. > > Try the libraries I am attaching. Also, you need the JCA > Connector API > jar, you can download this from > http://java.sun.com/j2ee/connector/download.html > > > Let me know how this works. > > > Ramesh.. > >

On Wed, 2009-12-16 at 11:42 -0600, Sanjay Chaudhuri wrote: > Here you go. I have also checked in relevant code changes with the > updated template on SVN. Ok, I fixed the "${connector-name}Execution.java" class in the SVN, so that it will not require the "teiid-engine-7.0.0-SNAPSHOT.jar" and no more compilation issues. It should work with jars I gave and connector-api.jar that's it. > Do you want me to check in a new cdk-dist_7.0.0 wrapper plugin for > developers to be able to use cdk-connector plugin instead of > hand-wiring classpaths ? > No, do not check-in as release 7 has more work to do. We will try to release this eclipse plug-in along with 7 release, then we can do that. (I wish we could define the classpath in the Eclipse from a Maven repo, then we never have to check-in anywhere) Ramesh..

On Wed, 2009-12-16 at 13:20 -0600, Sanjay Chaudhuri wrote: > Excellent idea about "classpath in Eclipse from a Maven repo". Give me > the location, and let me see, if I can do something about it .. an > interesting challenge !!! > Actually, if you add "maven" eclipse plugin as dependency to your plugin, and drive the connector's build from "pom.xml" any dependencies specified in the "pom.xml" are automatically added to the eclipse project. May be that is how we want to drive this. Obviously we would pre-can the "pom.xml" for our purpose that means it will dependencies specified to begin with. If you installed "maven" on your machine, then a local repo is in your "${user.home}/.m2/repository" directory. It may not have the files I gave, but you can create them easily like .m2/repository/org/jboss/teiid/teiid-common-core/7.0.0-SNAPSHOT/teiid-common-core-7.0.0-SNAPSHOT.jar .m2/repository/org/jboss/teiid/teiid-connector-api/7.0.0-SNAPSHOT/teiid-connector-api-7.0.0-SNAPSHOT.jar .m2/repository/javax/resource/connector-api/1.5/connector-api-1.5.jar Then use the attached pom file to build, it has jboss maven repo details(although Teiid files are not in there now, they will be in future). if we go this route I will add pom file to the template. Ramesh..

Bottom line is either we can make the project to build using the maven or use eclipse built-in build. 1) If we use maven, we need to depend on maven and maven eclipse plug-in. 2) If we use eclipse build, we can provide option to user to a) add the dependencies manually. b) and/or given a maven repo location and version, manually download the resources from URL and save in the project and use them just. Since (2) is minimum dependency route, I am OK with pursuing that. I see that what you are proposing below On Wed, 2009-12-16 at 17:02 -0600, Sanjay Chaudhuri wrote: > I was thinking, how about using http://repository.jboss.com/maven2 as > the place to go and get the plugins I would use the above as default, but in "preferences" for the project, I will let them change it. > either by hardcoded names or by parsing pom.xml to get both the the > repository location and the dependencies. I would just use the hard coded based on given version, as with every version this will change. Parsing pom.xml is bad idea, as this can be laborious. > The Cdk wizard may have a check-box to force a download or use an old > download. Downloaded jars can be kept in metadata location of the > workspace. Each Cdk project may either use a local copy which gets > copied from the metadata location or may directly point to the > metadata location to always get pointed to the latest download. No separate metadata location needed. Just copy them into the project the very first time when they create the connector. If some reason download is not successful or on users wish let them add manually. It does not matter how they got the jars. > > This is to facilitate build and export without maven installed and a > maven build. Let me know what you think.