[JBoss JIRA] (TEIIDDES-2141) URL Validation when creating XML Connection profile results in long pauses
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-2141:
---------------------------------------
Summary: URL Validation when creating XML Connection profile results in long pauses
Key: TEIIDDES-2141
URL: https://issues.jboss.org/browse/TEIIDDES-2141
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 8.5
Reporter: Mark Drilling
The URL validation (when typing in a URL) seems over aggressive, resulting in long delays.
To reproduce:
1) Choose import from XML Remote source.
2) create new connection profile in the wizard for Xml Remote source. In the URL text box, start typing the url below.
http://www.w3schools.com/xml/Plant_Catalog.xml
Every keystroke seems like its doing validation to access the url and verify that it's valid - resulting in long pauses. recommend simpler url validation, then use the Test Connection button to further verify - if necessary.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2140) VDB Execution - no translators problem running with teiid 8.6
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-2140:
---------------------------------------
Summary: VDB Execution - no translators problem running with teiid 8.6
Key: TEIIDDES-2140
URL: https://issues.jboss.org/browse/TEIIDDES-2140
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.5
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.5
Attachments: NoTranslatorWTeiid86.png
When running with Designer 8.5 and connecting to a Teiid 8.6 server, the translators are not picked up.
There are no translators in the server view. Also, when you select a VDB and attempt to execute you get the attached error.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2139) 2 Connections to same VDB in JBDS seem to share one password
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2139?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2139:
----------------------------------
Assignee: Barry LaFond
> 2 Connections to same VDB in JBDS seem to share one password
> ------------------------------------------------------------
>
> Key: TEIIDDES-2139
> URL: https://issues.jboss.org/browse/TEIIDDES-2139
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.2
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Priority: Blocker
>
> Description of problem:
> Connections to same VDB seem to share one password.
> I have 2 connections to one VDB and each connection should use different username and password(one with longer password and the other one with shorter).
> When I save the password in configuration of the first connection, the second connection doesn't work. In the preferences of the second one is obvious that the saved password is too long to be right, after retyping the password this connection works, but the other one doesn't...
> JBDS 7.1.1.GA + TeiidDesigner 8.3.2
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2139) 2 Connections to same VDB in JBDS seem to share one password
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2139?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-2139:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1093617
> 2 Connections to same VDB in JBDS seem to share one password
> ------------------------------------------------------------
>
> Key: TEIIDDES-2139
> URL: https://issues.jboss.org/browse/TEIIDDES-2139
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.2
> Reporter: Matus Makovy
> Priority: Blocker
>
> Description of problem:
> Connections to same VDB seem to share one password.
> I have 2 connections to one VDB and each connection should use different username and password(one with longer password and the other one with shorter).
> When I save the password in configuration of the first connection, the second connection doesn't work. In the preferences of the second one is obvious that the saved password is too long to be right, after retyping the password this connection works, but the other one doesn't...
> JBDS 7.1.1.GA + TeiidDesigner 8.3.2
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2139) 2 Connections to same VDB in JBDS seem to share one password
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2139:
--------------------------------------
Summary: 2 Connections to same VDB in JBDS seem to share one password
Key: TEIIDDES-2139
URL: https://issues.jboss.org/browse/TEIIDDES-2139
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.3.2
Reporter: Matus Makovy
Priority: Blocker
Description of problem:
Connections to same VDB seem to share one password.
I have 2 connections to one VDB and each connection should use different username and password(one with longer password and the other one with shorter).
When I save the password in configuration of the first connection, the second connection doesn't work. In the preferences of the second one is obvious that the saved password is too long to be right, after retyping the password this connection works, but the other one doesn't...
JBDS 7.1.1.GA + TeiidDesigner 8.3.2
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2129) Issues with cli interaction on Windows OS
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2129?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-2129:
-----------------------------------------
We are making calls via the ModelControllerClient. Code is here if interested https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/teii...
We are hitting DV600 in EAP6.1 or a later version of teiid which runs on EAP 6.1 alpha. Was wondering if this looked similar to anything you've seen previously.
The client gets stuck on read operation where it is fetching server status. for example I've seen it get stuck on the "getRAConnections" method in the above class. I'll continue to do some profiling but any insight you might have is appreciated.
> Issues with cli interaction on Windows OS
> -----------------------------------------
>
> Key: TEIIDDES-2129
> URL: https://issues.jboss.org/browse/TEIIDDES-2129
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: DesignerThreadDump.txt, ServerThreadDump.txt
>
>
> Several issues observed in the Teiid Connection Importer on Windows 7 OS (not observed on linux OS)
> - First page of wizard, the datasources table does not populate
> - Click 'New...' to create a new datasource - the driver column of the table is not populated.
> - Continue in the wizard to deploy the dynamic VDB. In the server console you can see the vdb deploy and go ACTIVE, be the control never returns to the wizard. It times out.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-1779) Designer error when trying to read a remote server configuration that's running in domain mode
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1779?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1779:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 982741|https://bugzilla.redhat.com/show_bug.cgi?id=982741] from NEW to CLOSED
> Designer error when trying to read a remote server configuration that's running in domain mode
> ----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1779
> URL: https://issues.jboss.org/browse/TEIIDDES-1779
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 8.5
>
>
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:58)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.getTeiidRuntimeVersion(JBoss7ServerUtil.java:172)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.createJboss7TeiidServer(TeiidServerAdapterFactory.java:204)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:185)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:78)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:66)
> at org.eclipse.wst.server.core.internal.ResourceManager.fireServerEvent(ResourceManager.java:560)
> at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:712)
> at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:474)
> at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:266)
> at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:463)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:432)
> at org.eclipse.wst.server.ui.internal.editor.ServerEditor.doSave(ServerEditor.java:389)
> at org.eclipse.ui.internal.DefaultSaveable.doSave(DefaultSaveable.java:54)
> at org.eclipse.ui.Saveable.doSave(Saveable.java:214)
> at org.eclipse.ui.internal.SaveableHelper.doSaveModel(SaveableHelper.java:348)
> at org.eclipse.ui.internal.WorkbenchPage$11.run(WorkbenchPage.java:3633)
> at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:276)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1812)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1809)
> at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284)
> at org.eclipse.ui.internal.WorkbenchPage.saveAll(WorkbenchPage.java:3644)
> at org.eclipse.ui.internal.WorkbenchPage.saveAllEditors(WorkbenchPage.java:3440)
> at org.eclipse.ui.internal.handlers.SaveAllHandler.execute(SaveAllHandler.java:47)
> 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.GeneratedMethodAccessor80.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> 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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:327)
> ... 76 more
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2028:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1056756|https://bugzilla.redhat.com/show_bug.cgi?id=1056756] from NEW to ASSIGNED
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: 8.6
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years