August 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-540) Refactoring/Move view model dependant upon other view models gets errors since other view models didn't move

by Paul Nittel (JIRA)

Refactoring/Move view model dependant upon other view models gets errors since other view models didn't move ------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-540 URL: https://jira.jboss.org/browse/TEIIDDES-540 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1 Environment: Fedora 12, Designer 7.1 M1 Reporter: Paul Nittel Attachments: LogWithRefactorErrors.log After importing from JDBC, I created view models atop each of the 3 imported models. I then created another view model wihch used the first set of models. vParts <-- vPartsO, vPartsS, vPartsM I created a series of folder into which I began to refactor the models. Source models refactored w/o issue. I refactored vParts and then received errors that the other models couldn't be found in vParts' new folder. (Unresolved reference "file:/home/pnittel/workspace-T71M1/HotMonday/View/Relational/vPartsM.xmi -- in this case, it's still in HotMonday/) The Message Log shows other errors, at least one of which had a stack trace. I'll attach the log -- 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-507) Teiid 7.0 Designer does not display XML results - Instead get "org.teiid.core.types.SQLXMLImpl@8f2d5e"

by Paul Nittel (JIRA)

Teiid 7.0 Designer does not display XML results - Instead get "org.teiid.core.types.SQLXMLImpl@8f2d5e" ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-507 URL: https://jira.jboss.org/browse/TEIIDDES-507 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final Reporter: Paul Nittel I have created a simple XML document model (bookListing). After deploying the VDB to a Teiid server, executing a query ("select * from booksDoc.bookListingDocument") produces this cryptic result: org.teiid.core.types.SQLXMLImpl@8f2d5e. It should display the actual XML output, preferably formatted in the tree format. There do not appear to be any related exceptions when I execute the query. Model project set shall be attached! -- 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

13 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-522) Recursive XML doc model does not create mapping class structure for lower levels

by Paul Nittel (JIRA)

Recursive XML doc model does not create mapping class structure for lower levels -------------------------------------------------------------------------------- Key: TEIIDDES-522 URL: https://jira.jboss.org/browse/TEIIDDES-522 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Environment: Fedora 12, JBDS 3.0.1, Teiid 7 Designer Reporter: Paul Nittel I am following the E2eRecursiveXmlTextSource test script. I create a document model, based on the imported XSD and step through the creation wizard. On the third page, per the instructions, I expand the tree and select (check) the Supervisor node before clicking finish. What I get is a Supervisor mapping class which has no mapping tree elements against which to link the columns (which I add manually, again, per the instructions). It is possible this represents new behavior, but I suspect not. I'm attaching the Model Project Set (which has 3 projects). -- 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

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-573) Datatypes Editor get Unhandled event loop exception when creating subtype

by Paul Nittel (JIRA)

Datatypes Editor get Unhandled event loop exception when creating subtype ------------------------------------------------------------------------- Key: TEIIDDES-573 URL: https://jira.jboss.org/browse/TEIIDDES-573 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, TeiidDesigner 7.1M2 Reporter: Paul Nittel When trying to create a subtype of Boolean (or any other type, it seems), I'm getting this exception: Error 2010-08-20 09:57:36.209 Unhandled event loop exception java.lang.NullPointerException at java.io.File.<init>(File.java:239) at com.metamatrix.modeler.internal.ui.forms.HyperlinkComponentSet.valueClicked(HyperlinkComponentSet.java:46) at com.metamatrix.modeler.internal.ui.forms.HyperlinkComponentSet$1.valueClicked(HyperlinkComponentSet.java:84) at com.metamatrix.modeler.internal.ui.forms.FormTextObjectEditor$MyHyperlinkListener.linkActivated(FormTextObjectEditor.java:162) at org.eclipse.ui.forms.widgets.FormText.activateLink(FormText.java:1548) at org.eclipse.ui.forms.widgets.FormText.handleMouseClick(FormText.java:1351) at org.eclipse.ui.forms.widgets.FormText.access$16(FormText.java:1323) at org.eclipse.ui.forms.widgets.FormText$6.mouseUp(FormText.java:448) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:207) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- 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

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-525) In Import wizards, add ability to launch Connection Profile property editor (so I can easily fix bad connection props).

by Ken Johnson (JIRA)

In Import wizards, add ability to launch Connection Profile property editor (so I can easily fix bad connection props). ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-525 URL: https://jira.jboss.org/browse/TEIIDDES-525 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.0 Environment: Teiid Designer 7, Helios, RHEL 6, OpenJDK 6 Reporter: Ken Johnson When importing (e.g. Metadata from JDBC Database), I can choose an existing connection profile or create a new one. If the one I create or choose has an error - say a bad password, to fix it I have to: 1. cancel out of the import wizard 2. switch perspectives to DTP 3. edit the properties for the offending connection profile 4. switch perspective back to Designer 5. re-run import wizard to try again. Since connection property errors are a common occurrence, this is a usability issue. Suggest adding the ability to launch the connection profile property editor directly from the import wizard so the correction can be made, saved, and retested without the context switches. -- 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

13 years, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-567) Refactor display node logic

by Steve Hawkins (JIRA)

Refactor display node logic --------------------------- Key: TEIIDDES-567 URL: https://jira.jboss.org/browse/TEIIDDES-567 Project: Teiid Designer Issue Type: Quality Risk Components: Editors, Teiid Integration Affects Versions: 7.1 Reporter: Steve Hawkins DisplayNode logic duplicates Teiid SQLStringVisitor logic and quickly gets out of synch. There are also several pending changes (nested table syntax, named parameter syntax) that could have their fixes obviated by just changing the display node logic to use the SQLStringVisitor to construct the display node tree. The bulk of the display node classes can be removed since they contain no logic and could be replaced with instanceof checks on the underlying language object instead. Teiid's SQLStringVisitor will need some modifications to accommodate this change, which will get rolled into 7.1.1 -- 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-565) XML Document objects are not showing up in DTP VDB's.

by Barry LaFond (JIRA)

XML Document objects are not showing up in DTP VDB's. ----------------------------------------------------- Key: TEIIDDES-565 URL: https://jira.jboss.org/browse/TEIIDDES-565 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.1 Deploy a VDB with XML Docs in it and when viewed in DTP, the XML Doc nodes are missing. -- 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-562) Change Generate WSDL Option to Preview WSDL

by Ted Jones (JIRA)

Change Generate WSDL Option to Preview WSDL ------------------------------------------- Key: TEIIDDES-562 URL: https://jira.jboss.org/browse/TEIIDDES-562 Project: Teiid Designer Issue Type: Task Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1 With the introduction of the generate Web Service war feature, the option to generate the WSDL in the workspace is confusing. Need to allow a WSDL preview option either via a tab on the VDB or other means and remove the Generate WSDL option off of a web service model. -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-481) Checkboxes in VDB editor for Synch and visibility are "unusual" and never checked

by Paul Nittel (JIRA)

Checkboxes in VDB editor for Synch and visibility are "unusual" and never checked --------------------------------------------------------------------------------- Key: TEIIDDES-481 URL: https://jira.jboss.org/browse/TEIIDDES-481 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Milestone build from 6/28 Reporter: Paul Nittel Assuming I have a VDB which contains models, 1 - Modify one of the models 2 - Save the model 3 - The VDB editor shows the large "Synchronize All" button is enabled and the synch checkbox associated with the changed model is an empty checkbox. (The other checkboxes are large gray squares. See attached screenshot.) 4 - Click the checkbox (it now turns into the gray square - the large "All" button remains enabled) 5 - Save the VDB Now the large "Synchronize All" button is disabled If I click the "Synchronize All" button first, the checkbox is affected and the large button remains enabled until the VDB is saved. I would expect the button and checkbox(es) to work together and that once all models are synched, the large button would be disabled even without the VDB being saved. (Oddly, once I save a model in the VDB, the VDB becomes dirty. Maybe this is intentional, but now I don't have the option to deploy that VDB until I synch it.) -- 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

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-586) Please rename "XSD Schemas" on Teiid Deisgner importers list.

by Ken Johnson (JIRA)

Please rename "XSD Schemas" on Teiid Deisgner importers list. ------------------------------------------------------------- Key: TEIIDDES-586 URL: https://jira.jboss.org/browse/TEIIDDES-586 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.0 Environment: JBoss Tools 8/26/2010 Reporter: Ken Johnson Priority: Minor The Teiid Designer import option "XSD Schemas" is a redundant name. XSDs *are* schemas. Perhaps "XML Schemas" or "XSD Files" or something else. -- 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

13 years, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010