[teiid-designer-dev] Teiid configuration in Designer
John Doyle
jdoyle at redhat.com
Wed May 6 13:50:35 EDT 2009
Just logged https://jira.jboss.org/jira/browse/TEIIDDES-175. I'll link the Jira back to this discussion if the forums ever catch up.
Ramesh, like I said earlier, I've very much talking out of school in technical understanding of what I'm proposing, but can I infer from your response that Teiid exposes sufficient APIs to retain current functionality to accomplish what I suggest?
~jd
----- "John Verhaeg" <jverhaeg at redhat.com> wrote:
> But as far as I'm aware, we don't have a ticket for this yet. Can you
>
> log one that captures your thoughts?
>
> On May 6, 2009, at 10:49 AM, Ramesh Reddy wrote:
>
> > Well that is certainly the case going forward to have such
> modularity,
> > as this has been discussed before. However, that is not case today.
> > There needs to be huge re-work needs to be done in designer before
> we
> > can achieve this. Currently Designer knows too much about the
> Teiid's
> > configuration, that needs to be fixed such that it only
> communicates
> > only through the known public API like JDBC and Admin API.
> >
> > Ramesh..
> >
> > On Wed, 2009-05-06 at 11:35 -0400, John Doyle wrote:
> >> I'm throwing this idea out there with very little idea of how the
>
> >> links between Teiid and Designer function, but I think it would be
>
> >> cool and beneficial.
> >>
> >> AFAIK we don't have a user story abut how you update the version of
>
> >> Teiid that is delivered with Designer. I think that it would be
> >> very cool if we exposed this cabability in designer similar to the
>
> >> way Installed JREs are exposed through the Preferences page.
> >> Designer could come with a version of Teiid, but users could point
>
> >> Designer to other versions of Teiid installed on their system and
>
> >> choose to run with those. One of the goals we have discussed is
> >> that we don't want Designer to be wedded to a particular version of
>
> >> Teiid. Defining the links between to two in this manner would
> >> force a contract and make it easy to test and validate that
> >> Designer 6.X works with Teiid 6.X and 7.X, etc.
> >>
> >> What do you think?
> >>
> >> ~jd
> >> _______________________________________________
> >> teiid-designer-dev mailing list
> >> teiid-designer-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
> >
> > _______________________________________________
> > teiid-designer-dev mailing list
> > teiid-designer-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
>
> _______________________________________________
> teiid-designer-dev mailing list
> teiid-designer-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
More information about the teiid-designer-dev
mailing list