[JBoss JIRA] Created: (TEIIDDES-975) Need additional options for Model Project wizard to assist in setting up working folders for source, views, web services, schemas, extension models and function models
by Barry LaFond (JIRA)
Need additional options for Model Project wizard to assist in setting up working folders for source, views, web services, schemas, extension models and function models
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-975
URL: https://issues.jboss.org/browse/TEIIDDES-975
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 7.5
Reporter: Barry LaFond
Priority: Minor
Fix For: 7.5
Need to enhance the concept of best-practices for maintaining model projects with several models in them.
Maybe on the New Teiid Model Project wizard, add check-box options to create folders for "sources", "views", etc....
Possible an action to Add those after project creation time
This could also be a visual-only thing or a special filter. Designer back in MM days had a Dimension product that displayed models in folders based on metamodel type
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (TEIIDDES-126) Add a warning for the use of a model supports property
by Steven Hawkins (JIRA)
Add a warning for the use of a model supports property
------------------------------------------------------
Key: TEIIDDES-126
URL: https://jira.jboss.org/jira/browse/TEIIDDES-126
Project: Teiid Designer
Issue Type: Quality Risk
Components: Modeling
Affects Versions: 6.0.0
Reporter: Steven Hawkins
See TEIID-131. Model support properties that are simply overrides for connector binding properties are no longer checked by the Teiid runtime, rather TEIID-205 is used to control specific capabilities through the connector binding without requiring the creation of a custom capabilities class.
Usage of 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", Supports "Outer Join", and Supports "Where all" should generate a warning stating that the connector binding should be used instead.
--
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
12 years, 11 months
[JBoss JIRA] Created: (TEIIDDES-417) Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled
by Paul Nittel (JIRA)
Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled
---------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-417
URL: https://jira.jboss.org/jira/browse/TEIIDDES-417
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.3
Environment: Iced Tea, Teiid Designer 6.3
Reporter: Paul Nittel
Attachments: IMFTF.jpg
I was writing a SWTBot test to create a view model's tables when I ran into this.
Knowing SWTBot can't handle the File Chooser, I was delighted to see I could enter the text file's path and name directly into the importer dialog. It wasn't until some time later that I realized merely typing in the name does nothing; you MUST enter the name using the File Chooser. (Once that's been done, it appears you can use the drop-down to re-select that file, but you need that first time entry.)
What's really bad/confusing is manually entering the file and target location enables the Finish button. Clicking it appears to work, but no tables were added to the model.
--
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
12 years, 11 months
[JBoss JIRA] Created: (TEIIDDES-927) SQLServer import problem
by luca gioppo (JIRA)
SQLServer import problem
------------------------
Key: TEIIDDES-927
URL: https://issues.jboss.org/browse/TEIIDDES-927
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.3
Environment: Windows XP
Reporter: luca gioppo
Attachments: UfficioTecnico.xmi
Made import from SQL Server, tables imported correctly, but "Preview data" does not work also this essor is in the message lock
"Unable to select any database object(s) that match sa"
eclipse.buildId=M20110210-1200
java.version=1.6.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.java.product
Any hint?
Thanks
Luca
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (TEIIDDES-683) JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password.
by John Doyle (JIRA)
JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password.
--------------------------------------------------------------------------------------------
Key: TEIIDDES-683
URL: https://jira.jboss.org/browse/TEIIDDES-683
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Reporter: John Doyle
Assignee: John Doyle
The UI in the JDBC importer allows a user to provide a password at import time, rather than keep it in the ConnectionProfile, for security purposes. In theory DTP supports this use and has a connect() method that allows a user to pass the username and password. In practice there is a defect in the ConnectionProfiles provided in the DTP enablement project. The username and password are not used.
This means that when a Teiid Designer user selects a ConnectionProfile w/o a password in the JDBC importer and supplies the password in our UI, the connection will fail.
Here's the eclipse bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=328738
Targeted to be fixed in DTP 1.9.
For our purposes the JDBC importer should validate that the profile has a password before attempting to connect, and inform the user that Teiid Designer can only use profiles with full credentials.
--
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
12 years, 11 months
[JBoss JIRA] Created: (TEIIDDES-915) WSDL Preview throws StringIndexOutOfBoundsException
by Ted Jones (JIRA)
WSDL Preview throws StringIndexOutOfBoundsException
---------------------------------------------------
Key: TEIIDDES-915
URL: https://issues.jboss.org/browse/TEIIDDES-915
Project: Teiid Designer
Issue Type: Feature Request
Components: Web Services Support
Affects Versions: 7.3
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 7.4
Previewing WSDL for a Web Service Model throws the following exception:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1949)
at com.metamatrix.modeler.webservice.ui.actions.PreviewWsdlAction.run(PreviewWsdlAction.java:76)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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:369)
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:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months