Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. TEIIDDES-1969

Newly Created VDB Editor Does Not Show UDF JAR

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.3
    • Fix Version/s: 8.3
    • Component/s: Editors
    • Labels:
      None

      Description

      Using Teiid Designer:

      Description of problem:

      I created a VDB and added models from the workspace. One of these models, was a relational function model that had a UDF JAR associated with it. When the VDB is created and the VDB editor is shown for the first time, selecting the "UDF Jars" tab does not show the UDF JAR that was added to the VDB when the VDB was created.

      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:

      Always.

      Steps to Reproduce (using the E2EYahooUdfTestScript):

      1. New > Teiid VDB
      2. Select models from workspace. One of which is relational function with UDF JAR.
      3. Click on "UDF Jars" tab of the VDB editor.

      Actual results:

      The "UDF Jars" tab of VDB editor does not show the UDF JAR file associated with the relational function model.

      Expected results:

      The UDF JAR file should be displayed when the VDB is first created.

      Additional info:

      If the VDB editor is closed and reopened, the UDF JAR is shown in the editor. So it is obviously being added to the VDB.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                blafond Barry LaFond
                Reporter:
                van.halbert Van Halbert
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: