Details

    • Type: Feature Request Feature Request
    • Status: Resolved Resolved (View Workflow)
    • Priority: Blocker Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.0.0.GA
    • Component/s: birt
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      I am going to integrate JBoss Tools with BIRT.

      The integration will include the following functionalities:

      • creating a data source based on the Hibernate Tools configuration
      • creating a data set including most of the Hibernate Tools features (browsing the Hibernate artifacts, syntax highlighting, formating, content assist...), D&D ...
      • the data set preview
      • creating reports using the Hibernate data source
      • adding deployment within a web projects (JSF, Seam...)

        Activity

        Hide
        Max Rydahl Andersen
        added a comment -

        just reopening to remember to review the doc as requested.

        Show
        Max Rydahl Andersen
        added a comment - just reopening to remember to review the doc as requested.
        Hide
        Max Rydahl Andersen
        added a comment -

        slip

        Show
        Max Rydahl Andersen
        added a comment - slip
        Hide
        Max Rydahl Andersen
        added a comment -

        finally an update:

        I reviewed the docs - feature looks overall good.

        I'm still not convinced that the integration is done in a way we want to promote/support; i.e. Birt looks like a monster to configure in this setup - can't be true can it ? And the seam integration should live in seam repo - not part of jbosstools.

        Show
        Max Rydahl Andersen
        added a comment - finally an update: I reviewed the docs - feature looks overall good. I'm still not convinced that the integration is done in a way we want to promote/support; i.e. Birt looks like a monster to configure in this setup - can't be true can it ? And the seam integration should live in seam repo - not part of jbosstools.
        Hide
        Max Rydahl Andersen
        added a comment -

        this will do for now.

        Its not in JBDS and ill consider the integration experimental until we find the holy grail of how to integrate seam properly with Birt (right now it is just invoking a servlet - no reuse of connection, sesseionfactory nor objects/classes are happening)

        Show
        Max Rydahl Andersen
        added a comment - this will do for now. Its not in JBDS and ill consider the integration experimental until we find the holy grail of how to integrate seam properly with Birt (right now it is just invoking a servlet - no reuse of connection, sesseionfactory nor objects/classes are happening)
        Hide
        Snjezana Peco
        added a comment -

        The servlet is used to start BIRT OSGi Runtime that renders a report. This is the standard way used within the BIRT project.
        The Hibernate ODA driver is executed within the OSGi Runtime. It uses a session factory or entity manager factory from the server's JNDI namespace, entity classes included into the session factory/entity manager factory (hql queries). See ServerOdaFactory.getSessionFactory(). The OSGi Runtime is executed within the JBoss server's JVM, uses the server's classpath (we don't deploy hibernate libraries), server's JNDI (session factory/entity manager factory) ...

        The servlet is the way to start the OSGi framework. It is also possible to create a JBoss AS service to start the OSGi framework.
        Advantages:

        • we would have most of the BIRT libraries at one place on the server; the BIRT WAR would be significantly reduced
          Disadvantages:
        • the service would be JBoss specific
        • we would have to upgrade the service when upgrading BIRT
        Show
        Snjezana Peco
        added a comment - The servlet is used to start BIRT OSGi Runtime that renders a report. This is the standard way used within the BIRT project. The Hibernate ODA driver is executed within the OSGi Runtime. It uses a session factory or entity manager factory from the server's JNDI namespace, entity classes included into the session factory/entity manager factory (hql queries). See ServerOdaFactory.getSessionFactory(). The OSGi Runtime is executed within the JBoss server's JVM, uses the server's classpath (we don't deploy hibernate libraries), server's JNDI (session factory/entity manager factory) ... The servlet is the way to start the OSGi framework. It is also possible to create a JBoss AS service to start the OSGi framework. Advantages: we would have most of the BIRT libraries at one place on the server; the BIRT WAR would be significantly reduced Disadvantages: the service would be JBoss specific we would have to upgrade the service when upgrading BIRT

          People

          • Assignee:
            Max Rydahl Andersen
            Reporter:
            Snjezana Peco
          • Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: