[
https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-3117:
----------------------------------------
[~blafond] When JAR is already deployed into the WildFly as is, i.e. no module is created
then "deployment" prefix is needed. When you are including the JAR file inside
the "lib" directory then you don't need any property at all.
So, as per Designer adding the "lib" property with "deployment"
prefix, it should depend on UI says. If it a module and has post fix of ".jar"
yes that should be added otherwise no.
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)