June 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-467) VDB's "name" value should not contain the ".vdb" file extension in the vdb.xml file.

by Barry LaFond (JIRA)

VDB's "name" value should not contain the ".vdb" file extension in the vdb.xml file. ------------------------------------------------------------------------------------ Key: TEIIDDES-467 URL: https://jira.jboss.org/browse/TEIIDDES-467 Project: Teiid Designer Issue Type: Bug Components: Editors, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Johnny Verhaeg Priority: Blocker Fix For: 7.0 Attempting to deploy and connect to a VDB in Designer/DTP it was discovered that the VDB "name" property in a vdb.xml file does NOT include the file extension ".vdb". Note that when deploying it via Admin API deployVDB( fileName, fileContents), the fileName DOES contain the .vdb -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-295) "EResourceImpl" class must implement "XResource" interface

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-295?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDDES-295. ----------------------------------- Resolution: Out of Date Teiid runtime no longer depends upon the metadata library which is emf based; so no longer an issue from Teiid stand point. > "EResourceImpl" class must implement "XResource" interface > ---------------------------------------------------------- > > Key: TEIIDDES-295 > URL: https://jira.jboss.org/browse/TEIIDDES-295 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Currently "EResourceImpl" does not implement XResource, and thus fail to look up the UUID. Lack of this creates a Stack Over Flow, it it tries to find the id using the URL fragment and calls itself. To get over the hump, I putting in the interface on the object and returning null, however the implementation is still due. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-295) "EResourceImpl" class must implement "XResource" interface

by John Verhaeg (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-295?page=com.atlassian.jira.plugin... ] John Verhaeg reassigned TEIIDDES-295: ------------------------------------- Assignee: Ramesh Reddy (was: John Verhaeg) If this is still an issue, we need more info on how to reproduce this. If it's no longer an issue, feel free to resolve it. > "EResourceImpl" class must implement "XResource" interface > ---------------------------------------------------------- > > Key: TEIIDDES-295 > URL: https://jira.jboss.org/browse/TEIIDDES-295 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Currently "EResourceImpl" does not implement XResource, and thus fail to look up the UUID. Lack of this creates a Stack Over Flow, it it tries to find the id using the URL fragment and calls itself. To get over the hump, I putting in the interface on the object and returning null, however the implementation is still due. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-176) Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs.

by Ramesh Reddy (JIRA)

Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs. ---------------------------------------------------------------------------------------------- Key: TEIIDDES-176 URL: https://jira.jboss.org/jira/browse/TEIIDDES-176 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: Ramesh Reddy Assignee: Johnny Verhaeg Priority: Critical > 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? > 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.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-18) UnsupportedOperationException when importing from Rose

by John Verhaeg (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-18?page=com.atlassian.jira.plugin.... ] John Verhaeg reassigned TEIIDDES-18: ------------------------------------ Assignee: John Verhaeg (was: Johnny Verhaeg) > UnsupportedOperationException when importing from Rose > ------------------------------------------------------ > > Key: TEIIDDES-18 > URL: https://jira.jboss.org/browse/TEIIDDES-18 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Environment: fedora 10 > Reporter: Paul Nittel > Assignee: John Verhaeg > Fix For: Future > > Attachments: PartsSupplierLogical.mdl > > > I tried to import PartsSupplierLogical.mdl (attached) and received this exception: > !ENTRY com.metamatrix.rose 4 0 2008-12-15 10:55:10.304 > !MESSAGE java.lang.UnsupportedOperationException > !STACK 0 > java.lang.UnsupportedOperationException > at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) > at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) > at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) > at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) > at java.util.AbstractList.add(AbstractList.java:91) > at com.metamatrix.rose.internal.handler.UmlHandler.createPackage(UmlHandler.java:773) > at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:261) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) > at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:876) > at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:605) > at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:362) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > Dec 15, 2008 10:55:09.870 [ModalContext|0] ERROR <com.metamatrix.rose|0> java.lang.UnsupportedOperationException > java.lang.UnsupportedOperationException > at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) > at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) > at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) > at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) > at java.util.AbstractList.add(AbstractList.java:91) > at com.metamatrix.rose.internal.handler.UmlHandler.createPackage(UmlHandler.java:773) > at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:261) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) > at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:876) > at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:605) > at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:362) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > While it appears to continue, if you clickpast the exception, it just hangs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-279) UUID values being created and stored in memory for XSD Schema elements.

by John Verhaeg (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-279?page=com.atlassian.jira.plugin... ] John Verhaeg reassigned TEIIDDES-279: ------------------------------------- Assignee: John Verhaeg (was: Johnny Verhaeg) > UUID values being created and stored in memory for XSD Schema elements. > ----------------------------------------------------------------------- > > Key: TEIIDDES-279 > URL: https://jira.jboss.org/browse/TEIIDDES-279 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Barry LaFond > Assignee: John Verhaeg > > Noticed that adding XML Document models to VDB and saving created validation errors indicating the XML Doc elements contained href's with UUID's to XSD elements that did NOT have uuid's in stored/saved models. > Talked to John and we are currently still creating UUID's for All schema model objects but just not "saving" them to file system. We need to fix this, of course. > The simple use case is to create take any Schema model and generate an XML Doc model from it and SAVE. The validation error won't show up unless you fix all errors (i.e. transformations) and add to a VDB and save, so there is probably a problem with Validation rules??? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-295) "EResourceImpl" class must implement "XResource" interface

by John Verhaeg (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-295?page=com.atlassian.jira.plugin... ] John Verhaeg reassigned TEIIDDES-295: ------------------------------------- Assignee: John Verhaeg (was: Johnny Verhaeg) > "EResourceImpl" class must implement "XResource" interface > ---------------------------------------------------------- > > Key: TEIIDDES-295 > URL: https://jira.jboss.org/browse/TEIIDDES-295 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: John Verhaeg > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Currently "EResourceImpl" does not implement XResource, and thus fail to look up the UUID. Lack of this creates a Stack Over Flow, it it tries to find the id using the URL fragment and calls itself. To get over the hump, I putting in the interface on the object and returning null, however the implementation is still due. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-280) Update Count metadata property is not avaialble on the Web Service procedure

by John Verhaeg (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-280?page=com.atlassian.jira.plugin... ] John Verhaeg reassigned TEIIDDES-280: ------------------------------------- Assignee: John Verhaeg (was: Johnny Verhaeg) > Update Count metadata property is not avaialble on the Web Service procedure > ---------------------------------------------------------------------------- > > Key: TEIIDDES-280 > URL: https://jira.jboss.org/browse/TEIIDDES-280 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: John Verhaeg > > "Update Count" metadata is not available on the Web Service procedure, this is only available on the virtual procedures. This data is used at run time to determine if procedure is "readonly", or does "single" or "multiple" updates to the underlaying databases. If this property not available then by default it is assumed that "multiple" updates and subject to the transactional restrictions in the server and dqp. > Per SteveH, this property must be on any kind of procedure, may that be virtual, web and xml service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-239) CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-239?page=com.atlassian.jira.plugin... ] Steve Hawkins updated TEIIDDES-239: ----------------------------------- Assignee: (was: Steven Hawkins) > CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-239 > URL: https://jira.jboss.org/browse/TEIIDDES-239 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 6.1.0, 6.2.0 > Reporter: Michael Walker > Priority: Minor > Fix For: 7.0 > > > This problem occurs in our transformation editor, and also occurs with real-time queries (e.g. from QueryBuilder/SQLExplorer, or any client). > If you reference a non-qualified table name, e.g. "myTable", in a query, we'll attempt to resolve it if it is a unique name. > Strangely, we don't do the same thing for virtual procedures, even if they are unique. Instead, you must use the fully-qualified name. There should be no disparity. This is a usability defect. > This also happens to greatly extend the size of virtual procedure code, making it harder to read and debug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-384) Merge Designer IDE towards JBoss Dev Studio

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-384?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-384. ----------------------------------- Resolution: Done This is completed. Designer is now being both built (nightly) and installable as part of the JBoss Tools package and JBDS > Merge Designer IDE towards JBoss Dev Studio > ------------------------------------------- > > Key: TEIIDDES-384 > URL: https://jira.jboss.org/browse/TEIIDDES-384 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Affects Versions: 7.0 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 7.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010