Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9719

Deploys Teiid artifacts to deploy folder configured in JBDS

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.0.0.Alpha1-SOA
    • Component/s: teiid
    • Labels:
      None

      Description

      When we deploy Teiid artifacts (like Datasources, VDB), JBDS always deploys the artifacts to JBoss deploy folder. It should use deploy folder configured in JBDS.

        Gliffy Diagrams

          Activity

          Hide
          maxandersen Max Rydahl Andersen added a comment -

          datasources sounds like another duplication/overlap of what should be part of core tools instead of teiid specific.

          Maybe would be good to outline what kind of deployment mechanisms you actually need and how it compare to what I consider "normal" jboss ear/war/jar deployments. ?

          Maybe start a forum thread or email thread on this or is a hangout a better start to sync up on what can be done?

          Show
          maxandersen Max Rydahl Andersen added a comment - datasources sounds like another duplication/overlap of what should be part of core tools instead of teiid specific. Maybe would be good to outline what kind of deployment mechanisms you actually need and how it compare to what I consider "normal" jboss ear/war/jar deployments. ? Maybe start a forum thread or email thread on this or is a hangout a better start to sync up on what can be done?
          Hide
          rareddy Ramesh Reddy added a comment -

          I agree about datasources. However, the integration goes deep here, as Designer uses configured DTP's Connection Profile to create a data source or connection factory. As Teiid Designer uses the connection from DTP connection profile to import metadata and as well create DS in JBoss AS for use with preview. I believe this is done as extension to DTP.

          Teiid Designer does not really need any UI to manage any of these that I know of, as long as it has access to underlying API to perform these tasks then it works. Deployment, data-sources are parts that are generic in nature, there are few other operations on teiid subsystem that Designer needs access to, to full fill its functionality (ex:merge-vdbs)

          One part I have seen JBoss AS falls little short is in describing properties for the connection factories (JCA connectors, the RAR ra.xml properties not exposed through DMR), I added JIRA asking for these but meanwhile Teiid fills this gap with its own operations on its subsystem.

          max, bmlafond, it is your discretion to see what can moved to core etc. I will participate in discussion anyway you guys want.

          +1 for hangout

          Show
          rareddy Ramesh Reddy added a comment - I agree about datasources. However, the integration goes deep here, as Designer uses configured DTP's Connection Profile to create a data source or connection factory. As Teiid Designer uses the connection from DTP connection profile to import metadata and as well create DS in JBoss AS for use with preview. I believe this is done as extension to DTP. Teiid Designer does not really need any UI to manage any of these that I know of, as long as it has access to underlying API to perform these tasks then it works. Deployment, data-sources are parts that are generic in nature, there are few other operations on teiid subsystem that Designer needs access to, to full fill its functionality (ex:merge-vdbs) One part I have seen JBoss AS falls little short is in describing properties for the connection factories (JCA connectors, the RAR ra.xml properties not exposed through DMR), I added JIRA asking for these but meanwhile Teiid fills this gap with its own operations on its subsystem. max, bmlafond, it is your discretion to see what can moved to core etc. I will participate in discussion anyway you guys want. +1 for hangout
          Hide
          maxandersen Max Rydahl Andersen added a comment -

          DTP connection profiles is what we want to use for creating datasources - that is what the datasource wizard in core does now.

          "One part I have seen JBoss AS falls little short is in describing properties for the connection factories (JCA connectors, the RAR ra.xml properties not exposed through DMR), I added JIRA asking for these"

          Which Jira ?

          "but meanwhile Teiid fills this gap with its own operations on its subsystem."

          so teiid has its own AS7 subsystem where these a "double exposed" or ?

          Show
          maxandersen Max Rydahl Andersen added a comment - DTP connection profiles is what we want to use for creating datasources - that is what the datasource wizard in core does now. "One part I have seen JBoss AS falls little short is in describing properties for the connection factories (JCA connectors, the RAR ra.xml properties not exposed through DMR), I added JIRA asking for these" Which Jira ? "but meanwhile Teiid fills this gap with its own operations on its subsystem." so teiid has its own AS7 subsystem where these a "double exposed" or ?
          Hide
          rareddy Ramesh Reddy added a comment -

          This forum request https://community.jboss.org/message/628016#628016

          I was thinking this was going to cover it https://issues.jboss.org/browse/AS7-1339, but does not look it covers the issue. I tried with 7.1.1.

          Teiid has its own subsystem in AS7, it exposes a custom operation to expose ra.xml "config-property" definitions.

          Show
          rareddy Ramesh Reddy added a comment - This forum request https://community.jboss.org/message/628016#628016 I was thinking this was going to cover it https://issues.jboss.org/browse/AS7-1339 , but does not look it covers the issue. I tried with 7.1.1. Teiid has its own subsystem in AS7, it exposes a custom operation to expose ra.xml "config-property" definitions.
          Hide
          blafond Barry LaFond added a comment -

          For Designer 8.0 we implemented the changes necessary to maintain current feature set. This includes deploying VDB's and creating Data Sources through Teiid's API. VDB's get deployed as "metadata", not as standard artifacts. For Data Sources, Teiid utilizes AS7 functionality and Designer will deploy the connection profile jars to the appropriate server folder.

          Show
          blafond Barry LaFond added a comment - For Designer 8.0 we implemented the changes necessary to maintain current feature set. This includes deploying VDB's and creating Data Sources through Teiid's API. VDB's get deployed as "metadata", not as standard artifacts. For Data Sources, Teiid utilizes AS7 functionality and Designer will deploy the connection profile jars to the appropriate server folder.

            People

            • Assignee:
              blafond Barry LaFond
              Reporter:
              jpviragine Joao Viragine
            • Votes:
              5 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development