[JBoss JIRA] (TEIIDDES-2017) NPE while using Teiid Connection Importer
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2017?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2017:
---------------------------------------
Note, this isn't just a SOLR related issue. Duplicated it when trying to import using the Infinispan cache data source.
> NPE while using Teiid Connection Importer
> -----------------------------------------
>
> Key: TEIIDDES-2017
> URL: https://issues.jboss.org/browse/TEIIDDES-2017
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> While trying to use "Teiid Connection >> Source Model" importer with new SOLR source type I encountered
> {code}
> java.lang.NullPointerException
> at org.teiid.designer.teiidimporter.ui.wizard.ShowDDLPage.setVisible(ShowDDLPage.java:201)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> The dialog did not pop any dialog box about error, nor it can proceed any further, so notification given to user other than he/she can cancel it. But the above is logged in the "errors" panel.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2182) Issues with Excel import
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2182?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2182:
----------------------------------------
[~mdrillin] Is that all the DDL you received from Teiid Server? If yes, in that case there may be an issue with the DDL generation on the Teiid side, is should have included
{code}
SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel
{code}
if not that is an error IMO. You can open JIRA if that is the case, will fix on the Teiid side. When/If available, you can check this against the namespace in the Designer side to match up with names. Otherwise we will never be in sync.
> Issues with Excel import
> ------------------------
>
> Key: TEIIDDES-2182
> URL: https://issues.jboss.org/browse/TEIIDDES-2182
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: excelSheet.ddl
>
>
> See comment on this community thread -
> https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
> There are a couple of issues with this scenario in Designer:
> 1)
> {code}
> org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
> at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
> at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> {code}
> This is a bug with the array init on line 791 of TeiidImportManager
> 2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
>
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2183) Teiid connection importer looses its translator setting during "< back"
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2183:
--------------------------------------
Summary: Teiid connection importer looses its translator setting during "< back"
Key: TEIIDDES-2183
URL: https://issues.jboss.org/browse/TEIIDDES-2183
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 8.3.2
Reporter: Ramesh Reddy
When Teiid Connection importer is used, after creating a datasource, if user selects "translator" setting, for any reason if the user uses "< back" in wizard and come back, then the translator is switched back to "jdbc-ansi", if user does not pay attention, the process fails with most data sources.
Once user selection is made, that should kept in tact until user changes it again.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2182) Issues with Excel import
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2182?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2182:
------------------------------------
Description:
See comment on this community thread -
https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
There are a couple of issues with this scenario in Designer:
1)
{code}
org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
{code}
This is a bug with the array init on line 791 of TeiidImportManager
2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
was:
See comment on this community thread -
https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
There are a couple of issues with this scenario in Designer:
1)
{code}
org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
{code}
This is a bug with the array init on line 791 of TeiidImportManager
2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
> Issues with Excel import
> ------------------------
>
> Key: TEIIDDES-2182
> URL: https://issues.jboss.org/browse/TEIIDDES-2182
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: excelSheet.ddl
>
>
> See comment on this community thread -
> https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
> There are a couple of issues with this scenario in Designer:
> 1)
> {code}
> org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
> at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
> at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> {code}
> This is a bug with the array init on line 791 of TeiidImportManager
> 2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
>
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2182) Issues with Excel import
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2182?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2182:
------------------------------------
Attachment: excelSheet.ddl
> Issues with Excel import
> ------------------------
>
> Key: TEIIDDES-2182
> URL: https://issues.jboss.org/browse/TEIIDDES-2182
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: excelSheet.ddl
>
>
> See comment on this community thread -
> https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
> There are a couple of issues with this scenario in Designer:
> 1)
> {code}
> org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
> at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
> at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> {code}
> This is a bug with the array init on line 791 of TeiidImportManager
> 2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
>
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2182) Issues with Excel import
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-2182:
---------------------------------------
Summary: Issues with Excel import
Key: TEIIDDES-2182
URL: https://issues.jboss.org/browse/TEIIDDES-2182
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.5
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.5
See comment on this community thread -
https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
There are a couple of issues with this scenario in Designer:
1)
{code}
org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
{code}
This is a bug with the array init on line 791 of TeiidImportManager
2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2178) Teiid Connection importer by default only waits for 120 seconds for schema
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2178?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2178:
------------------------------------
Fix Version/s: 8.5
8.6
made wording changes to clarify to user that the timeout is a preference and can be configured.
https://github.com/Teiid-Designer/teiid-designer/pull/361
also target to 8.6 - for consideration of further improvements - (interactive dialog to add more time during deployment)
> Teiid Connection importer by default only waits for 120 seconds for schema
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2178
> URL: https://issues.jboss.org/browse/TEIIDDES-2178
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.4, 8.3.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.5, 8.6
>
>
> When using the Teiid connection importer it sends the query to the server and waits for up to 120 seconds for server to return metadata. If the server returned data it is fine, otherwise it fails.
> Some times when working with larger metadata or slower connections it may take more than 120 seconds, the UI should give user an option to terminate or wait for another +n of seconds.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2109) Create a Connections context menu group next to Modeling group
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2109?page=com.atlassian.jira.plu... ]
Barry LaFond reopened TEIIDDES-2109:
------------------------------------
pulled out of 8.5 and retargeted 8.6
> Create a Connections context menu group next to Modeling group
> --------------------------------------------------------------
>
> Key: TEIIDDES-2109
> URL: https://issues.jboss.org/browse/TEIIDDES-2109
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Views
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.6
>
> Attachments: connection-action-menu.png
>
>
> For source models, the Modeling action now contains a number of connection or translator related actions that really don't have anything to do with modeling.
> * Create a *Connection* menu group and place below *Modeling* group
> * Move the following actions to the *Connection* group
> ** Create Data Source
> ** Edit Translator Overrides
> ** Remove Connection Info
> ** Set Connection Profile
> ** Set Translator Name
> ** View Connection Profile Info
> * Maybe group these into Translator/Profile actions with separators
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2178) Teiid Connection importer by default only waits for 120 seconds for schema
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2178?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2178:
----------------------------------------
What is your resistance to add a confirmation to ask the user if he need to terminate?
> Teiid Connection importer by default only waits for 120 seconds for schema
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2178
> URL: https://issues.jboss.org/browse/TEIIDDES-2178
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.4, 8.3.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
>
> When using the Teiid connection importer it sends the query to the server and waits for up to 120 seconds for server to return metadata. If the server returned data it is fine, otherwise it fails.
> Some times when working with larger metadata or slower connections it may take more than 120 seconds, the UI should give user an option to terminate or wait for another +n of seconds.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2177) Teiid Connection Importer should continue to finish even the schema returns no tables
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2177?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2177:
----------------------------------------
Thanks [~blafond] I added comment per Max's question.
> Teiid Connection Importer should continue to finish even the schema returns no tables
> -------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2177
> URL: https://issues.jboss.org/browse/TEIIDDES-2177
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.4, 8.3.2
> Reporter: Ramesh Reddy
>
> Moving my comment from TEIIDDES-1981, as that is completely ignored
> Some basic metadata importing has been added to MongoDB translator in 8.7. It may not work with complex documents but simple documents should work. See https://issues.jboss.org/browse/TEIID-2849
> IMO, the way Teiid Connection importer should work is, when the importer does not return any tables it should still go ahead and create a "empty" source model but finish creating the data source stuff etc. Such that when user does add a view manually it works seamlessly. Or give a user an option to create a empty model rather than terminating the whole process. That way JBoss DS is always created when Teiid Connection Importing is used.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years