I would also suggest to use OSGi DS and not Spring DM. Spring surely also has its advantages. But if you want to go the OSGi way, Spring does not sound to be a good partner anymore. IIRC Spring even removed the OSGi meta-data from their releases.
@Toni The introduction is only posted on the vogella blog, but it is not written by him. But thanks that you like it. ☺ Mit freundlichen Grüßen / Best regards Dirk Fauth Automotive Service Solutions, ESI application (AA-AS/EIS2-EU) Robert Bosch GmbH | Postfach 11 29 | 73201 Plochingen | GERMANY | www.bosch.com<http://www.bosch.com> Tel. +49 7153 666-1155 | dirk.fa...@de.bosch.com<mailto:dirk.fa...@de.bosch.com> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, Dr. Markus Heyn, Dr. Dirk Hoheisel, Christoph Kübel, Uwe Raschke, Peter Tyroller Von: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org] Im Auftrag von Toni Menzel Gesendet: Mittwoch, 19. Juli 2017 12:13 An: osgi-dev@mail.osgi.org; OSGi Developer Mail List <osgi-dev@mail.osgi.org> Betreff: Re: [osgi-dev] Spring Dynamic Modules is the solution to access bean from a bundle configured in a different bundle? Hey Raffaele, the question is, do you want to keep using Spring as your DI container. Spring DM is (at least the original one) long dead. SpringSource (at the time) lost faith in OSGi (i’d blame Springs horrendous internals). The Spring-DM idea, having a spring compatible “API” playing nicely inside OSGi got “standardised” in the for of OSGI Blueprint [1]. You may look into those instead. But, if you are getting started with OSGi and can rework many parts of your platform (how you do the refactoring is a very different thing to talk about), you may want to have a look at Declarative Services, as it is probably the most OSGi-native way of doing dependency injection in OSGi [2]. [1] Blueprint is part of the OSGi Compendium specification. Just check chapter 121. Aries Docs about Blueprint (implementation): http://aries.apache.org/modules/blueprint.html. [2] Declarative Services is part of the OSGi Compendium specification. Just check chapter 112. Lars Vogel also has a very good intro incl. well linked further references: http://blog.vogella.com/2016/06/21/getting-started-with-osgi-declarative-services/ @All, can’t the OSGi specs be web-pages, so we can link them like anything else on the web? Or is it just me? Toni [Das Bild wurde vom Absender entfernt.] www.rebaze.de<http://www.rebaze.de/> | www.rebaze.com<http://www.rebaze.com/> | @rebazeio<https://twitter.com/rebazeio> On 19. Jul 2017, 11:52 +0200, Raffaele Gambelli <r.gambe...@hitachi-systems-cbt.com>, wrote: Sorry, I submit again the same question because in the previous one I forgot the subject Hi all, this is my first question in this list. I'm trying to adjust a quite complex system, made with OSGI but which was made quite badly, in addition I have to say that I have no so much experience with OSGI. Briefly, I have four webapps on jetty which should live inside the same Equinox runtime, till today they and their needed bundles have been deployed in a such a way that quite all bundles embedded all their dependencies, so there is a huge confusion.... while I'm hardly working to create very smaller bundles, emptying them from the embedded dependencies and making them work together in what I believe be the OSGI paradygm. Just to let you know some other elements helping to understand my problems and knowledge here it is a question posted some weeks ago https://stackoverflow.com/questions/44897956/deploy-webapp-in-jetty-in-osgi where a very kind person exhaustively answered. Now i explain my current problem, I'm finally arrived to have a running webapplication, but as soon as it accesses Spring bean, it is not found, so for example I have a NPE in a row like this: SessionDao sessionDao = (SessionDao) SpringContextProvider.getApplicationContext().getBean("sessionDao"); That bean is configured in a different bundle and for what I'm undestanding that is the matter, so after some research I arrived to "Spring Dynamic Modules", so I'm reading this http://docs.spring.io/osgi/docs/current/reference/html-single/#why-Spring DM so my question is, am I on the right path? Should I go deeply with Spring DM to configure bean in bundle A and make it available on bundle B? Thanks very much, bye Raffaele Gambelli element Font font-family font-size font-style font-variant font-weight letter-spacing line-height text-decoration text-align text-indent text-transform white-space word-spacing color Background bg-attachment bg-color bg-image bg-position bg-repeat Box width height border-top border-right border-bottom border-left margin padding max-height min-height max-width min-width outline-color outline-style outline-width Positioning position top bottom right left float display clear z-index List list-style-image list-style-type list-style-position Table vertical-align border-collapse border-spacing caption-side empty-cells table-layout Effects text-shadow -webkit-box-shadow border-radius Other overflow cursor visibility _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
