Cross bundle communication should happen via the service registry. So bundle A should register the SessionDao bean as a service and bundle B should use that service using something like a service tracker instead of from the spring context.
Sincerely, - Ray On Wed, Jul 19, 2017 at 5:50 AM, Raffaele Gambelli < r.gambe...@hitachi-systems-cbt.com> wrote: > 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 > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
