Last week I attempted to reverse engineer a 6.2 Teiid VDB with Hibernate in JBoss Tools. In the latest release Hibernate tools added Teiid as an option in the Hibernate Tools UI. However, the Teiid dialect is not included in any release of Hibernate, so the Tooling doesn't work. I'm still looking for a better way, but as of now the only way I have found to get the dialect discovered in Tools is to put it in the global classpath. I'm of the opinion that the Teiid dialect should be 'built into' Hibernate by default in order to ease the path for our existing users to use other JBoss technologies, as well as easing adoption of Teiid by existing Hibernate users. Does anyone have an opinion pro or con about trying to get the Teiid dialect into Hibernate? ~john _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev

My understanding of how things work (from just tinkering with it) is that the dialects are delivered with Hibernate (in the hibernate3.jar). Ours it not, which is what I'm asking opinions on. Hibernate Tools requires you to configure a Hibernate installation. I just pointed to my AS, but you can use a standalone if you want. From there I think the plug-ins load a static set of jars from the installation you configured. We blow up because the classpath defined by the plug-ins doesn't contain our dialect. Mike-I think you could define this as a Tools defect if you say that Tools should allow you to add a dialect. Ramesh-The drivers are supplied by the DataTools ConnectionProfiles and Drivers that you have to define before you use Hibernate, so drivers are a different issue, and not something that the hibernate plug-ins have 'built in'. It's an configuration step that's already extensible in a way that Dialects don't appear to be. I'm personally in favor of including our dialect in Hibernate because then Tools will just work, there won't be some additional step for Teiid. It seems to me that if Oracle just works out of the box in Tools, then a fellow JBoss project should just work. The only downside I can see to including our dialect in Hibernate is that our release cycles don't match up and changes/maintenance would have to be managed across our differing cycles. ~jd ----- "Ramesh Reddy" <rareddy(a)redhat.com&gt; wrote: > I do not know whether it makes sense to include or not in the JBoss > Tools distribution because, we would be only including the "dialect" > code. We still need the Teiid driver for whole thing to work (I > think). > > How do they handle supplying the Oracle driver by the user? If this a > separate operation too, then you have case to include Teiid Dialect > in > JBDS. > > Ramesh.. > > On Mon, 2010-03-22 at 14:47 -0800, Michael Walker wrote: > >> I agree that it would be useful to include full support for Teiid in >> >> JBoss Tools. >> >> It's odd that Teiid is listed as a legitimate pull-down option in >> > Tools, > >> but the dialect actually isn't included -- this seems like a JBoss >> > Tools > >> bug, doesn't it? >> >> John Doyle wrote: >> >>> Last week I attempted to reverse engineer a 6.2 Teiid VDB with >>> > Hibernate in JBoss Tools. In the latest release Hibernate tools added > Teiid as an option in the Hibernate Tools UI. However, the Teiid > dialect is not included in any release of Hibernate, so the Tooling > doesn't work. I'm still looking for a better way, but as of now the > only way I have found to get the dialect discovered in Tools is to put > it in the global classpath. > >>> I'm of the opinion that the Teiid dialect should be 'built into' >>> > Hibernate by default in order to ease the path for our existing users > to use other JBoss technologies, as well as easing adoption of Teiid > by existing Hibernate users. Does anyone have an opinion pro or con > about trying to get the Teiid dialect into Hibernate? > >>> ~john >>> _______________________________________________ >>> teiid-dev mailing list >>> teiid-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/teiid-dev >>> >>> >> _______________________________________________ >> teiid-dev mailing list >> teiid-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/teiid-dev >> _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev

I am not dis-agreeing. Just wanted to what our options were. I do think it is valuable for Teiid be included along with Hibernate. They are about to release 3.5 very soon, we need to see if we can make it into 3.5 final release. So, instead of making this JIRA in the Tools, we need to make this into Hibernate by communicating with its lead. Thanks Ramesh.. On Tue, 2010-03-23 at 11:01 -0400, John Doyle wrote: > Ramesh-The drivers are supplied by the DataTools ConnectionProfiles > and Drivers that you have to define before you use Hibernate, so > drivers are a different issue, and not something that the hibernate > plug-ins have 'built in'. It's an configuration step that's already > extensible in a way that Dialects don't appear to be. > > I'm personally in favor of including our dialect in Hibernate because > then Tools will just work, there won't be some additional step for > Teiid. It seems to me that if Oracle just works out of the box in > Tools, then a fellow JBoss project should just work. The only > downside I can see to including our dialect in Hibernate is that our > release cycles don't match up and changes/maintenance would have to be > managed across our differing cycles. _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev