Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: 0.1.3
    • Component/s: None
    • Global Rank:
      15587

      Description

      -Many are starting to view OSGi as the perfect solution both for deploying server-side applications and client-side GUI applications.. If \
      you need a GUI front-end or a web application to interface with a database back-end, there is a rich array of standard components to choos\
      e from in the OSGi community. Before OSGi-based servers, if you wanted a full fledged application server with a Transaction provider and J\
      MS integration, you had to either run some large, monolithic application server like WebSphere, or you had to hack some custom components \
      to a lightweight servlet-container such as Apache Tomcat or Jetty. Today, you wouldn't install Jetty from scratch, you will install it as \
      an OSGi bundle in an OSGi container such as Apache Felix. If you needed an embedded database like Apache Derby or a transaction provider, \
      you can now tell your container what bundles to deploy and every component is developed to operate in a standard operating environment. On\
      ce you've figured out how to instantiate an empty OSGi container such as Apache Felix there is no simpler deployment mechanism for your ap\
      plication, and once you've connected it to Nexus Professional, you've instantly solved the deployment problem in Java. This chapter takes \
      you through the steps required to start using Maven and OSGi together and how to use Nexus Professional to support the distribution and de\
      ployment opportunities that are possible with an OSGi bundle repository (OBR).
      +Many are starting to view OSGi as the perfect solution both for deploying server-side applications and client-side GUI applications. If y\
      ou need a GUI front-end or a web application to interface with a database back-end, there is a rich array of standard components to choose\
      from in the OSGi community. Before OSGi-based servers, if you wanted a full fledged application server with a Transaction provider and JM\
      S integration, you had to either run some large, monolithic application server like WebSphere, or you had to hack some custom components t\
      o a lightweight servlet-container such as Apache Tomcat or Jetty. Today, you wouldn't install Jetty from scratch, you will install it as a\
      n OSGi bundle in an OSGi container such as Apache Felix. If you needed an embedded database like Apache Derby or a transaction provider, y\
      ou can now tell your container what bundles to deploy and every component is developed to operate in a standard operating environment. Onc\
      e you've figured out how to instantiate an empty OSGi container such as Apache Felix there is no simpler deployment mechanism for your app\
      lication, and once you've connected it to Nexus Professional, you've instantly solved the deployment problem in Java. This chapter takes y\
      ou through the steps required to start using Maven and OSGi together and how to use Nexus Professional to support the distribution and dep\
      loyment opportunities that are possible with an OSGi bundle repository (OBR).

        Activity

        Hide
        Tim O'Brien added a comment -

        Fixed

        Show
        Tim O'Brien added a comment - Fixed
        Hide
        Manfred Moser added a comment -

        Closing issue to establish clear status for workflow going forward.

        Show
        Manfred Moser added a comment - Closing issue to establish clear status for workflow going forward.

          People

          • Assignee:
            Tim O'Brien
            Reporter:
            Tim O'Brien
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Date of First Response: