Andrej Šmigala created TEIIDDES-2744: ---------------------------------------- Summary: Figure out a way for UDFs to work with dynamic VDB import and export Key: TEIIDDES-2744 URL: https://issues.jboss.org/browse/TEIIDDES-2744 Project: Teiid Designer Issue Type: Enhancement Components: Dynamic VDBs Reporter: Andrej Šmigala UDFs currently do not play nicely when exporting to dynamic VDBs. The way designer handles UDFs is that it adds the jar to the /lib folder in the .vdb archive and adds and <entry> element in the vdb.xml like so: {code:xml} <entry path="/lib/MyTestUdf-1.0-SNAPSHOT.jar"> <property name="checksum" value="2633160920"/> </entry> {code} This of course is not possible for -vdb.xml deployments, as there is no archive that the jar could be added to. The way UDFs work with -vdb.xml is that the jar must be added as eap module, and then referenced in a "lib" property in the vdb: {code:xml} <property name ="lib" value ="my-udf-module" /> {code} Since the end goal of dynamic vdb support in designer is to allow round-tripping, there should be a way to solve this mismatch. I suggest that designer should add support for UDFs defined as modules. The way this could work is that there would be a new extension property, say "module-name", that would allow the user to specify the name of the module to use. Designer would then use that value when exporting dynamic VDB and set it as the "lib" property in the -vdb.xml. When importing dynamic vdb, the reverse would be done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)