[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
14 years, 4 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
14 years, 5 months
[JBoss JIRA] Created: (TEIIDDES-824) Wrong runtime-type generated during the XML transformation generation from XSD
by Ramesh Reddy (JIRA)
Wrong runtime-type generated during the XML transformation generation from XSD
------------------------------------------------------------------------------
Key: TEIIDDES-824
URL: https://issues.jboss.org/browse/TEIIDDES-824
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 7.2
Environment: F14 JBDS-CR2
Reporter: Ramesh Reddy
1) Imported the Books.xsd, BookDataTypes.xsd
2) Open the Books, xml schema and select "bibilography" element
3) Right click "Modeling -> Create XML to Scalar Transformation"
The generated transformation for the "published" column is set as "gYear", thus the transformation validation fails.
"gYear" is not a Teiid "runtime" data type. "gYear" is design time XML data type, however there are mappings defined for each design time data type to runtime type. I suspect, we are not doing the translations. For Teiid "gYear" should be mapped to "biginteger". Although "gYear" definition can not really map to biginteger (as it has optional timezone its definition), that how Teiid understands currently. We need to also make sure other 'g' types are also mapped correctly.
If there is complex type that can not be deciphered correctly it may be good to leave as xml fragment.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (TEIIDDES-840) soften requirement limits in feature.xml <import> statements to ensure users can use DTP 1.7.x with latest Teiid 7.1.x
by Nick Boldt (JIRA)
soften requirement limits in feature.xml <import> statements to ensure users can use DTP 1.7.x with latest Teiid 7.1.x
----------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-840
URL: https://issues.jboss.org/browse/TEIIDDES-840
Project: Teiid Designer
Issue Type: Bug
Components: Build
Affects Versions: 7.1.1
Reporter: Nick Boldt
Looking in branches/7.1/features/org.teiid.designer.runtime.feature/feature.xml, I see that you have very restrictive limits on required imported features:
<requires>
<import feature="org.eclipse.datatools.common.doc.user" version="1.7.0.v200908280400-26-311A16321A3557"/>
<import feature="org.eclipse.datatools.connectivity.doc.user" version="1.7.0.v200908280400-37D-7733L3D753L7BBF"/>
<import feature="org.eclipse.datatools.connectivity.feature" version="1.7.0.v200908280400-7B7OAIEn1XeacwFFi4FhDyooRMY"/>
<import feature="org.eclipse.datatools.connectivity.oda.designer.feature" version="1.7.1.v200908280400-7E7C77DZRDEBDyIYEqgX"/>
<import feature="org.eclipse.datatools.connectivity.oda.feature" version="1.7.1.v200908280400-7H794CcNBC0BvEdEXZe"/>
<import feature="org.eclipse.datatools.doc.user" version="1.7.0.v200908280400-47C08w95ENAK6AFDFK7"/>
<import feature="org.eclipse.datatools.enablement.apache.derby.feature" version="1.7.0.v200908280400-7768bBmKDLfMjHuIFJW7SBI"/>
<import feature="org.eclipse.datatools.enablement.feature" version="1.7.0.v200908280400-7J8i2BWwQJOaz-Gi2C5seJM2FX2f"/>
...
</requires>
Wondering if you should explicitly include a match rule for the sake of clarity, and omit the qualifier/suffix so that you're not so brittle in your requirement.
For example, could use one of these formats:
<import plugin="org.eclipse.core.resources" version="3.2.0" match="compatible"/>
or
<import feature="org.hibernate.eclipse.feature" version="3.2.0" match="greaterOrEqual"/>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (TEIIDDES-717) Designer whoudl provide option to create datasources during the VDB deploy
by Ramesh Reddy (JIRA)
Designer whoudl provide option to create datasources during the VDB deploy
--------------------------------------------------------------------------
Key: TEIIDDES-717
URL: https://jira.jboss.org/browse/TEIIDDES-717
Project: Teiid Designer
Issue Type: Feature Request
Components: Teiid Integration
Affects Versions: 7.1
Reporter: Ramesh Reddy
Currently when a VDB is deployed, vdb is deployed but process does not check if the required data sources in the server exist or not. Designer should provide an option to the user to select to decide to create data sources or not in the same deploy action. This could be wizard driven if needed to. That way when a VDB is deployed all the required artifacts are also available in the server.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (TEIIDDES-859) Preview data failing for example project.
by Barry LaFond (JIRA)
Preview data failing for example project.
-----------------------------------------
Key: TEIIDDES-859
URL: https://issues.jboss.org/browse/TEIIDDES-859
Project: Teiid Designer
Issue Type: Feature Request
Components: VDB & Execution
Affects Versions: 7.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Blocker
Fix For: 7.3
Import Parts Example project
Continue with example and try to preview or Execute VDB and get no "Source" error from Teiid.
Problem is the Preview VDB is being created prior to the PartsSourceA.xmi being fully loaded. Result is the ModelEntry for it contains ModelType == "Type" instead of "Physical".
Fix is to not respond to Open Project events in TEiid Designer "PreviewManager" class
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months