[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-3117:
--------------------------------------
Assignee: Barry LaFond
> Dynamic VDB is not generated properly for UDF function
> ------------------------------------------------------
>
> Key: TEIIDDES-3117
> URL: https://issues.jboss.org/browse/TEIIDDES-3117
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.1
>
>
> I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error:
> {code:java}
> 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main
> at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> ... 5 more
> {code}
> According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>.
> The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar")
> *Actual property*
> {code:java}
> <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/>
> {code}
> *Valid property*
> {code:java}
> <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3117:
-----------------------------------
Fix Version/s: 11.1.1
> Dynamic VDB is not generated properly for UDF function
> ------------------------------------------------------
>
> Key: TEIIDDES-3117
> URL: https://issues.jboss.org/browse/TEIIDDES-3117
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 11.1.1
>
>
> I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error:
> {code:java}
> 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main
> at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> ... 5 more
> {code}
> According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>.
> The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar")
> *Actual property*
> {code:java}
> <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/>
> {code}
> *Valid property*
> {code:java}
> <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (TEIIDDES-3121) Create Web Service model from remote WSDL doesn't work on Windows
by Matej Kralik (JIRA)
Matej Kralik created TEIIDDES-3121:
--------------------------------------
Summary: Create Web Service model from remote WSDL doesn't work on Windows
Key: TEIIDDES-3121
URL: https://issues.jboss.org/browse/TEIIDDES-3121
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 11.1
Environment: Windows 10 - 1703
Reporter: Matej Kralik
Priority: Critical
Attachments: screenshot1.png, screenshot2.png
Generate Web Service Model from remote WSDL file doesn't work on Windows 10. I set URL(screenshot1) and click OK (wsdl is validating and after that, the wizard is closed) but nothing happens (screenshot2). In the error log is this error:
{code:java}
java.io.FileNotFoundException: C:\Users\jboss\AppData\Local\Temp\C:\Users\jboss\AppData\Local\Temp\dv-test-ws_soap5924564139032425684.wsdl (The filename, directory name, or volume label syntax is incorrect)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
at java.io.FileWriter.<init>(FileWriter.java:90)
at org.teiid.designer.core.util.URLHelper.createFileFromUrlInternal(URLHelper.java:204)
at org.teiid.designer.core.util.URLHelper.createFileFromUrl(URLHelper.java:192)
at org.teiid.designer.core.util.URLHelper.createFileFromUrl(URLHelper.java:153)
at org.teiid.designer.webservice.ui.wizard.WsdlSelectionPage.addURLWsdlFile(WsdlSelectionPage.java:848)
at org.teiid.designer.webservice.ui.wizard.WsdlSelectionPage.access$3(WsdlSelectionPage.java:830)
at org.teiid.designer.webservice.ui.wizard.WsdlSelectionPage$3.execute(WsdlSelectionPage.java:481)
at org.teiid.designer.ui.wizards.wsdl.WsdlFileSelectionComposite$6.run(WsdlFileSelectionComposite.java:318)
at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4213)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3820)
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.ui.wizards.wsdl.WsdlFileSelectionComposite.handleAddURLWsdlFile(WsdlFileSelectionComposite.java:314)
at org.teiid.designer.ui.wizards.wsdl.WsdlFileSelectionComposite.access$2(WsdlFileSelectionComposite.java:304)
at org.teiid.designer.ui.wizards.wsdl.WsdlFileSelectionComposite$3.widgetSelected(WsdlFileSelectionComposite.java:147)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
at org.eclipse.jface.window.Window.open(Window.java:794)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:390)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:151)
at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:161)
at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:99)
at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:167)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
at org.eclipse.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:57)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (TEIIDDES-3120) .vdb with JDG data source, with NATIVE defined, throws exception
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3120?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3120:
-----------------------------------
Fix Version/s: 11.1.1
> .vdb with JDG data source, with NATIVE defined, throws exception
> ----------------------------------------------------------------
>
> Key: TEIIDDES-3120
> URL: https://issues.jboss.org/browse/TEIIDDES-3120
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 11.1.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 11.1.1
>
> Attachments: Person.vdb
>
>
> When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy.
> However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there.
> Guessing that the translator doesn't know how to handle a .vdb file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (TEIIDDES-3120) .vdb with JDG data source, with NATIVE defined, throws exception
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3120?page=com.atlassian.jira.plu... ]
Van Halbert reassigned TEIIDDES-3120:
-------------------------------------
Assignee: Barry LaFond (was: Ramesh Reddy)
> .vdb with JDG data source, with NATIVE defined, throws exception
> ----------------------------------------------------------------
>
> Key: TEIIDDES-3120
> URL: https://issues.jboss.org/browse/TEIIDDES-3120
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 11.1.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Attachments: Person.vdb
>
>
> When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy.
> However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there.
> Guessing that the translator doesn't know how to handle a .vdb file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (TEIIDDES-3120) .vdb with JDG data source, with NATIVE defined, throws exception
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3120?page=com.atlassian.jira.plu... ]
Van Halbert moved TEIID-5101 to TEIIDDES-3120:
----------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-3120 (was: TEIID-5101)
Component/s: VDB & Execution
(was: Infinispan)
Affects Version/s: 11.1.1
(was: 8.12.x-6.4)
> .vdb with JDG data source, with NATIVE defined, throws exception
> ----------------------------------------------------------------
>
> Key: TEIIDDES-3120
> URL: https://issues.jboss.org/browse/TEIIDDES-3120
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 11.1.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
> Attachments: Person.vdb
>
>
> When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy.
> However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there.
> Guessing that the translator doesn't know how to handle a .vdb file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (TEIIDDES-3119) Save relationship model as another relationship model makes errors on view model
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3119?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3119:
-----------------------------------
Attachment: screenshot3.png
> Save relationship model as another relationship model makes errors on view model
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-3119
> URL: https://issues.jboss.org/browse/TEIIDDES-3119
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Reporter: Matej Kralik
> Attachments: SaveAsProject.zip, screenshot1.png, screenshot2.png, screenshot3.png
>
>
> I have source model and view model which uses source model for view tables. I want to save source model as new source model to another folder (screenshot1). I check that I don't want to modify view model (because original source model is still there) (screenshot2). This action causes errors in the view model (errors appear after Project->Clean).
> {code:java}
> Sql transformation in the model viewModel contains the unresolved reference file:/home/mkralik/workspace_testDesigner/SaveAsProject/partsupplier.xmi
> {code}
> The errors show to a model which doesn't exist because the saved new model has a different name (partsupplierSaveAs.xmi) but I uncheck modify view model so view model should still use original model.
> Next, the original source model was disappeared from transformation editor. (screenshot3)I must edit transformation (delete the last letter and add the letter back). After that, I am able to click on 'Save/Validate SQL ' button for fix error. After that error is disappeared.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (TEIIDDES-3119) Save relationship model as another relationship model makes errors on view model
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3119?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3119:
-----------------------------------
Attachment: (was: screenshot3.png)
> Save relationship model as another relationship model makes errors on view model
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-3119
> URL: https://issues.jboss.org/browse/TEIIDDES-3119
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Reporter: Matej Kralik
> Attachments: SaveAsProject.zip, screenshot1.png, screenshot2.png
>
>
> I have source model and view model which uses source model for view tables. I want to save source model as new source model to another folder (screenshot1). I check that I don't want to modify view model (because original source model is still there) (screenshot2). This action causes errors in the view model (errors appear after Project->Clean).
> {code:java}
> Sql transformation in the model viewModel contains the unresolved reference file:/home/mkralik/workspace_testDesigner/SaveAsProject/partsupplier.xmi
> {code}
> The errors show to a model which doesn't exist because the saved new model has a different name (partsupplierSaveAs.xmi) but I uncheck modify view model so view model should still use original model.
> Next, the original source model was disappeared from transformation editor. (screenshot3)I must edit transformation (delete the last letter and add the letter back). After that, I am able to click on 'Save/Validate SQL ' button for fix error. After that error is disappeared.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months