Grails
  1. Grails
  2. GRAILS-2221

To implement grails plugin system based on OSGI

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      To implement grails plugin system based on OSGI

        Issue Links

          Activity

          Hide
          Hans Westerbeek added a comment -

          I think the added value of having this feature does not outweigh the considerable effort to implement it. The Springsource-led OSGi hype has sort of quieted down, probably because people have found out it is a Really Hard Thing to do, especially when using software like Hibernate.

          Only in very specialized usecases does the idea of 'look i can replace a bundle' really have benefit.

          Furthermore, Wolfgang's OSGI plugin already allows a grails app to run in an OSGi container (albeit as a monolith), for those that really have to.

          I would vote for resolving this with a 'won't fix'...

          Show
          Hans Westerbeek added a comment - I think the added value of having this feature does not outweigh the considerable effort to implement it. The Springsource-led OSGi hype has sort of quieted down, probably because people have found out it is a Really Hard Thing to do, especially when using software like Hibernate. Only in very specialized usecases does the idea of 'look i can replace a bundle' really have benefit. Furthermore, Wolfgang's OSGI plugin already allows a grails app to run in an OSGi container (albeit as a monolith), for those that really have to. I would vote for resolving this with a 'won't fix'...
          Hide
          Henrique Lobo Weissmann (Kico) added a comment -

          Is there any plan to add OSGi support for Grails like was planned for 2.0 on this issue?
          What happened to this idea?

          Show
          Henrique Lobo Weissmann (Kico) added a comment - Is there any plan to add OSGi support for Grails like was planned for 2.0 on this issue? What happened to this idea?
          Hide
          Kim Betti added a comment -

          I hope that it has been scrapped.. I don't think it's a good idea to introduce this level of additional complexity.

          Show
          Kim Betti added a comment - I hope that it has been scrapped.. I don't think it's a good idea to introduce this level of additional complexity.
          Hide
          Graeme Rocher added a comment -

          OSGi as a technology is going nowhere and introduces huge amounts of complexity, something which we do not need.

          There is a need to modularise applications, but that should be done in a micro-services approach, which is something we would like to support.

          Given that I'm closing this issue as "Won't fix"

          Show
          Graeme Rocher added a comment - OSGi as a technology is going nowhere and introduces huge amounts of complexity, something which we do not need. There is a need to modularise applications, but that should be done in a micro-services approach, which is something we would like to support. Given that I'm closing this issue as "Won't fix"
          Hide
          Sergei Rahouski added a comment -

          Grails application is a brick once it is built. It is really hard to add anything to it at runtime.

          Lots of applications that go beyond 15 minutes blog demo need some sort of extensibility platform. Examples of such:
          a) Multi-tenant SaaS deployment - adding per tenant extensions that would require redeploy the whole application is a pain
          b) Vendor made enterprise apps - once released these applications need to be enhanced by the customer application group. Grails doesn't have a good answer for this either - other than shipping the source code.
          c) Large applications - the build time grows as application grows. Modularizing larger application would improve productivity. Binary plugins sort of answer this problem but I feel like if there was a way to build and deploy a piece of the larger app at lower cost it would be better than recreating the whole thing.

          IMO OSGi as technology is dead is a bold statement so as the statement about increased complexity. In fact you guys @Grails decided to break your code in modules and seemingly increased the complexity of the whole thing.

          Hopefully you'll reconsider one day.

          Show
          Sergei Rahouski added a comment - Grails application is a brick once it is built. It is really hard to add anything to it at runtime. Lots of applications that go beyond 15 minutes blog demo need some sort of extensibility platform. Examples of such: a) Multi-tenant SaaS deployment - adding per tenant extensions that would require redeploy the whole application is a pain b) Vendor made enterprise apps - once released these applications need to be enhanced by the customer application group. Grails doesn't have a good answer for this either - other than shipping the source code. c) Large applications - the build time grows as application grows. Modularizing larger application would improve productivity. Binary plugins sort of answer this problem but I feel like if there was a way to build and deploy a piece of the larger app at lower cost it would be better than recreating the whole thing. IMO OSGi as technology is dead is a bold statement so as the statement about increased complexity. In fact you guys @Grails decided to break your code in modules and seemingly increased the complexity of the whole thing. Hopefully you'll reconsider one day.

            People

            • Assignee:
              Graeme Rocher
              Reporter:
              Daniel.Sun
            • Votes:
              76 Vote for this issue
              Watchers:
              63 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Last Reviewed:

                Development