[JBoss JIRA] (TEIIDDES-1901) Teiid Connection Importer is using the pool-name instead of jndi name
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1901?page=com.atlassian.jira.plu... ]
Lucie Fabrikova edited comment on TEIIDDES-1901 at 2/3/14 12:06 PM:
--------------------------------------------------------------------
In dialog "Import using a Teiid Connection", the section Data Sources shows the pool names of datasources in column "DataSource" (in Teiid Designer 8.3.1.Final)
was (Author: lfabriko):
In dialog "Import using a Teiid Connection", the section Data Sources shows the pool names of datasources in column "DataSource".
> Teiid Connection Importer is using the pool-name instead of jndi name
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1901
> URL: https://issues.jboss.org/browse/TEIIDDES-1901
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> When using the "Teiid Connection" importer the data sources are identified with "pool-name" rather than the "jndi" name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1944) Refreshing a server that's not started results in Exception & dialog
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1944?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1944:
---------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1035473|https://bugzilla.redhat.com/show_bug.cgi?id=1035473] from ON_QA to VERIFIED
> Refreshing a server that's not started results in Exception & dialog
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1944
> URL: https://issues.jboss.org/browse/TEIIDDES-1944
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.3
>
>
> With single defined Server & Teiid instance.... I can generate same error in RefeshServerAction
> *Case 1:* Select server and click *Refesh* toolbar button
> Result:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.execute(RefreshServerAction.java:127)
>
> ==============
> *Case 2:* In Guides View > Teiid (action set) select *Refresh Teiid Instance*
> Results:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RuntimeAssistant.runRefreshServerAction(RuntimeAssistant.java:186)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:632)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1944) Refreshing a server that's not started results in Exception & dialog
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1944?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1944:
----------------------------------------
I believe so. In order to disable the refresh button, we would have needed a framework to ping the server list and that seemed like a lot of extra work.
> Refreshing a server that's not started results in Exception & dialog
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1944
> URL: https://issues.jboss.org/browse/TEIIDDES-1944
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.3
>
>
> With single defined Server & Teiid instance.... I can generate same error in RefeshServerAction
> *Case 1:* Select server and click *Refesh* toolbar button
> Result:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.execute(RefreshServerAction.java:127)
>
> ==============
> *Case 2:* In Guides View > Teiid (action set) select *Refresh Teiid Instance*
> Results:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RuntimeAssistant.runRefreshServerAction(RuntimeAssistant.java:186)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:632)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1944) Refreshing a server that's not started results in Exception & dialog
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1944?page=com.atlassian.jira.plu... ]
Lucie Fabrikova commented on TEIIDDES-1944:
-------------------------------------------
Is expected behavior to show dialog with warning, nothing in Error log?
> Refreshing a server that's not started results in Exception & dialog
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1944
> URL: https://issues.jboss.org/browse/TEIIDDES-1944
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.3
>
>
> With single defined Server & Teiid instance.... I can generate same error in RefeshServerAction
> *Case 1:* Select server and click *Refesh* toolbar button
> Result:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.execute(RefreshServerAction.java:127)
>
> ==============
> *Case 2:* In Guides View > Teiid (action set) select *Refresh Teiid Instance*
> Results:
> java.lang.Exception: The parent JBoss Server is not started.
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:218)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:84)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RuntimeAssistant.runRefreshServerAction(RuntimeAssistant.java:186)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:632)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1963) Designer Create User Defined Function Dialog contains Result Set Tab
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1963?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1963:
---------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1035356|https://bugzilla.redhat.com/show_bug.cgi?id=1035356] from ON_QA to VERIFIED
> Designer Create User Defined Function Dialog contains Result Set Tab
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1963
> URL: https://issues.jboss.org/browse/TEIIDDES-1963
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Original Description below, however, investigation determined that UDF's should now allow creating Result Set children, so the Result Set tab needs to be removed.
> Description of problem:
> Following the E2E Yahoo UDF Test Script, I tried to create the UDF. When I got to the part to create the return parameter for the function the "Add" column button could not be enabled.
> Version-Release number of selected component (if applicable):
> DV 6.0.0 ER4
> JBDS 7.1.0 CR1
> JBIS 4.1.3 Beta5
> Teiid Designer 8.3.0 CR1
> OS X 10.9
> How reproducible:
> Happens every time.
> Steps to Reproduce:
> Using Designer:
> 1. Create a new relational model
> 2. New Child > Procedure > User Defined Function > OK
> 3. Enter a function "Name" and a "Java Class" (to get rid of error message)
> 4. Click the "Result Set" tab
> 5. There is no way to add a result set column
> Actual results:
> Unable to create a return parameter for relational UDF model. But the model can be created and the return parameter can be added later using the New Child menu option.
> Expected results:
> The "Add" button in the wizard should enable so that a return parameter can be entered.
> Additional info:
> None
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1962) Incorrect Wizard Error Message When Creating A User Defined Function
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1962?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1962:
---------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1035372|https://bugzilla.redhat.com/show_bug.cgi?id=1035372] from ON_QA to VERIFIED
> Incorrect Wizard Error Message When Creating A User Defined Function
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1962
> URL: https://issues.jboss.org/browse/TEIIDDES-1962
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Description of problem:
> After filling in the function name, the error message states "User defined function category is undefined." Filling in the "Function Category" does not change the error message. Once the "Java Class" is filled in the error message goes away.
> Turns out the "Function Category" isn't required at all.
> Version-Release number of selected component (if applicable):
> DV 6.0.0 ER4
> JBDS 7.1.0 CR1
> JBIS 4.1.3 Beta5
> Teiid Designer 8.3.0 CR1
> How reproducible:
> Steps to Reproduce :
> Using Designer:
> 1. Create a new relational model
> 2. New Child > Procedure > User Defined Function > OK
> 3. Enter a function "Name."
> 4. Wizard error message now shows "User defined function category is undefined"
> 5. Only way to get rid of this error message is to enter a "Java Class"
> Actual results:
> Incorrect, misleading error message.
> Expected results:
> A correct error message indicating the "Java Class" is missing.
> Additional info:
> None.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months