Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin<\/a>. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could have one or more blueprint files.<\/p>\n Blueprint files represent architecture of our bundle. Let’s visualize it using groovy script and graphviz available in my github repository<\/a> and analyze.<\/p>\n Pre: All you need is groovy and graphviz installed on your OS<\/strong><\/p>\n I am working mostly with bundles with generated blueprint, so I will use blueprint file generated from Blueprint Maven Plugin tests as example. All examples are included in github repository.<\/p>\n Generation could be invoked by running .\/run.sh target\/fullBlueprint fullBlueprint.xml<\/p>\n Visualization is available here<\/a>.<\/p>\n First if you look at the image, you see that some beans are grouped. You could easily extract such domains with tree roots: Now we have three, a bit cleaner, images: We also could generate image from more than one blueprint:<\/p>\n And the result is here<\/a>. The image contains beans grouped by file, but if you do not like it, you could force generation without such separation using option Example generation<\/h2>\n
run.sh<\/code> script with given destination file prefix (png extension will be added to it) and path to blueprint file:<\/p>\nmkdir -p target<\/pre>\n
Separating domains<\/h2>\n
beanWithConfigurationProperties<\/code> and beanWithCallbackMethods<\/code> to separate blueprint files and bundles in future and generate images from them:<\/p>\n.\/run.sh target\/beanWithCallbackMethods example\/firstCut\/beanWithCallbackMethods.xml\r\n.\/run.sh target\/beanWithConfigurationProperties example\/firstCut\/beanWithConfigurationProperties.xml\r\n.\/run.sh target\/otherStuff example\/firstCut\/otherStuff.xml<\/pre>\n
beanWithConfigurationProperties.png<\/code><\/a>, beanWithCallbackMethods.png<\/code><\/a> and otherStuff.png<\/code><\/a>.<\/p>\n.\/run.sh target\/joinFirstCut example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml<\/pre>\n
--no-group-by-file<\/code>:<\/p>\n.\/run.sh target\/joinFirstCutGrouped example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml --no-group-by-file<\/pre>\n
![here<\/a>.<\/p>\nSeparating domains<\/h2>\nFirst if you look at the image, you see that some beans are grouped. You could easily extract such domains with tree roots: beanWithConfigurationProperties<\/code> and beanWithCallbackMethods<\/code> to separate blueprint files and bundles in future and generate images from them:<\/p>\n.\/run.sh target\/beanWithCallbackMethods example\/firstCut\/beanWithCallbackMethods.xml\r\n.\/run.sh target\/beanWithConfigurationProperties example\/firstCut\/beanWithConfigurationProperties.xml\r\n.\/run.sh target\/otherStuff example\/firstCut\/otherStuff.xml<\/pre>\nNow we have three, a bit cleaner, images: beanWithConfigurationProperties.png<\/code><\/a>, beanWithCallbackMethods.png<\/code><\/a> and otherStuff.png<\/code><\/a>.<\/p>\nWe also could generate image from more than one blueprint:<\/p>\n.\/run.sh target\/joinFirstCut example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml<\/pre>\nAnd the result is here<\/a>. The image contains beans grouped by file, but if you do not like it, you could force generation without such separation using option --no-group-by-file<\/code>:<\/p>\n.\/run.sh target\/joinFirstCutGrouped example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml --no-group-by-file<\/pre>\nIt will generate image with all beans from all files<\/a>.<\/p>\nExclusion<\/h2>\nSometimes it is difficult to spot and extract other domains. It will be easier to do some experiments on blueprint. For example, bean my1<\/code> is a dependency for too many other beans. You could consider converting my1<\/code> bean to OSGi service and extracting it to another bundle.<\/p>\nLet’s exclude my1<\/code> bean from generation via -e<\/code> option and see what happens:<\/p>\n.\/run.sh target\/otherStuffWithoutMy example\/firstCut\/otherStuff.xml -e my1<\/pre>\nResult is available here<\/a>. Now we see, that tree with root bean myFactoryBeanAsService<\/code> could be separated and my1<\/code> could be inject to it as osgi service in another bundle.<\/p>\nYou could exclude more than one bean adding -e<\/code> switch for each of them, e. g. -e my1 -e m2 -e myBean123<\/code>.<\/p>\nConclusion<\/h2>\nBlueprint is great for dependency injection for OSGi bundles, but it is easy to create quite big context containing many domains. It is much easier to recognize or search for such domains using blueprint visualizer script.<\/p>\n <\/p>\nYOUR CODE HRER<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"What is blueprint?Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could hav…\n","protected":false},"author":54,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[606,50,44,608],"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026"}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=13026"}],"version-history":[{"count":14,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions"}],"predecessor-version":[{"id":14926,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions\/14926"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=13026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=13026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=13026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/gist.github.com\/alien11689\/560e189859107159126e71d45065ec51\/raw\/d2a8b16e5741a1debf36168953f5608ec91a1656\/fullBlueprint.png\"){kind=link}
![beanWithConfigurationProperties.png<\/code><\/a>, beanWithCallbackMethods.png<\/code><\/a> and otherStuff.png<\/code><\/a>.<\/p>\nWe also could generate image from more than one blueprint:<\/p>\n.\/run.sh target\/joinFirstCut example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml<\/pre>\nAnd the result is here<\/a>. The image contains beans grouped by file, but if you do not like it, you could force generation without such separation using option --no-group-by-file<\/code>:<\/p>\n.\/run.sh target\/joinFirstCutGrouped example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml --no-group-by-file<\/pre>\nIt will generate image with all beans from all files<\/a>.<\/p>\nExclusion<\/h2>\nSometimes it is difficult to spot and extract other domains. It will be easier to do some experiments on blueprint. For example, bean my1<\/code> is a dependency for too many other beans. You could consider converting my1<\/code> bean to OSGi service and extracting it to another bundle.<\/p>\nLet’s exclude my1<\/code> bean from generation via -e<\/code> option and see what happens:<\/p>\n.\/run.sh target\/otherStuffWithoutMy example\/firstCut\/otherStuff.xml -e my1<\/pre>\nResult is available here<\/a>. Now we see, that tree with root bean myFactoryBeanAsService<\/code> could be separated and my1<\/code> could be inject to it as osgi service in another bundle.<\/p>\nYou could exclude more than one bean adding -e<\/code> switch for each of them, e. g. -e my1 -e m2 -e myBean123<\/code>.<\/p>\nConclusion<\/h2>\nBlueprint is great for dependency injection for OSGi bundles, but it is easy to create quite big context containing many domains. It is much easier to recognize or search for such domains using blueprint visualizer script.<\/p>\n <\/p>\nYOUR CODE HRER<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"What is blueprint?Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could hav…\n","protected":false},"author":54,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[606,50,44,608],"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026"}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=13026"}],"version-history":[{"count":14,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions"}],"predecessor-version":[{"id":14926,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions\/14926"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=13026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=13026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=13026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/gist.github.com\/alien11689\/560e189859107159126e71d45065ec51\/raw\/d2a8b16e5741a1debf36168953f5608ec91a1656\/beanWithConfigurationProperties.png\"){kind=link}
![beanWithCallbackMethods.png<\/code><\/a> and otherStuff.png<\/code><\/a>.<\/p>\nWe also could generate image from more than one blueprint:<\/p>\n.\/run.sh target\/joinFirstCut example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml<\/pre>\nAnd the result is here<\/a>. The image contains beans grouped by file, but if you do not like it, you could force generation without such separation using option --no-group-by-file<\/code>:<\/p>\n.\/run.sh target\/joinFirstCutGrouped example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml --no-group-by-file<\/pre>\nIt will generate image with all beans from all files<\/a>.<\/p>\nExclusion<\/h2>\nSometimes it is difficult to spot and extract other domains. It will be easier to do some experiments on blueprint. For example, bean my1<\/code> is a dependency for too many other beans. You could consider converting my1<\/code> bean to OSGi service and extracting it to another bundle.<\/p>\nLet’s exclude my1<\/code> bean from generation via -e<\/code> option and see what happens:<\/p>\n.\/run.sh target\/otherStuffWithoutMy example\/firstCut\/otherStuff.xml -e my1<\/pre>\nResult is available here<\/a>. Now we see, that tree with root bean myFactoryBeanAsService<\/code> could be separated and my1<\/code> could be inject to it as osgi service in another bundle.<\/p>\nYou could exclude more than one bean adding -e<\/code> switch for each of them, e. g. -e my1 -e m2 -e myBean123<\/code>.<\/p>\nConclusion<\/h2>\nBlueprint is great for dependency injection for OSGi bundles, but it is easy to create quite big context containing many domains. It is much easier to recognize or search for such domains using blueprint visualizer script.<\/p>\n <\/p>\nYOUR CODE HRER<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"What is blueprint?Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could hav…\n","protected":false},"author":54,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[606,50,44,608],"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026"}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=13026"}],"version-history":[{"count":14,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions"}],"predecessor-version":[{"id":14926,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions\/14926"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=13026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=13026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=13026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/gist.github.com\/alien11689\/560e189859107159126e71d45065ec51\/raw\/d2a8b16e5741a1debf36168953f5608ec91a1656\/beanWithCallbackMethods.png\"){kind=link}
![otherStuff.png<\/code><\/a>.<\/p>\nWe also could generate image from more than one blueprint:<\/p>\n.\/run.sh target\/joinFirstCut example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml<\/pre>\nAnd the result is here<\/a>. The image contains beans grouped by file, but if you do not like it, you could force generation without such separation using option --no-group-by-file<\/code>:<\/p>\n.\/run.sh target\/joinFirstCutGrouped example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml --no-group-by-file<\/pre>\nIt will generate image with all beans from all files<\/a>.<\/p>\nExclusion<\/h2>\nSometimes it is difficult to spot and extract other domains. It will be easier to do some experiments on blueprint. For example, bean my1<\/code> is a dependency for too many other beans. You could consider converting my1<\/code> bean to OSGi service and extracting it to another bundle.<\/p>\nLet’s exclude my1<\/code> bean from generation via -e<\/code> option and see what happens:<\/p>\n.\/run.sh target\/otherStuffWithoutMy example\/firstCut\/otherStuff.xml -e my1<\/pre>\nResult is available here<\/a>. Now we see, that tree with root bean myFactoryBeanAsService<\/code> could be separated and my1<\/code> could be inject to it as osgi service in another bundle.<\/p>\nYou could exclude more than one bean adding -e<\/code> switch for each of them, e. g. -e my1 -e m2 -e myBean123<\/code>.<\/p>\nConclusion<\/h2>\nBlueprint is great for dependency injection for OSGi bundles, but it is easy to create quite big context containing many domains. It is much easier to recognize or search for such domains using blueprint visualizer script.<\/p>\n <\/p>\nYOUR CODE HRER<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"What is blueprint?Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could hav…\n","protected":false},"author":54,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[606,50,44,608],"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026"}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=13026"}],"version-history":[{"count":14,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions"}],"predecessor-version":[{"id":14926,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions\/14926"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=13026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=13026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=13026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/gist.github.com\/alien11689\/560e189859107159126e71d45065ec51\/raw\/d2a8b16e5741a1debf36168953f5608ec91a1656\/otherStuff.png\"){kind=link}
![here<\/a>. The image contains beans grouped by file, but if you do not like it, you could force generation without such separation using option --no-group-by-file<\/code>:<\/p>\n.\/run.sh target\/joinFirstCutGrouped example\/firstCut\/otherStuff.xml example\/firstCut\/beanWithConfigurationProperties.xml example\/firstCut\/beanWithCallbackMethods.xml --no-group-by-file<\/pre>\nIt will generate image with all beans from all files<\/a>.<\/p>\nExclusion<\/h2>\nSometimes it is difficult to spot and extract other domains. It will be easier to do some experiments on blueprint. For example, bean my1<\/code> is a dependency for too many other beans. You could consider converting my1<\/code> bean to OSGi service and extracting it to another bundle.<\/p>\nLet’s exclude my1<\/code> bean from generation via -e<\/code> option and see what happens:<\/p>\n.\/run.sh target\/otherStuffWithoutMy example\/firstCut\/otherStuff.xml -e my1<\/pre>\nResult is available here<\/a>. Now we see, that tree with root bean myFactoryBeanAsService<\/code> could be separated and my1<\/code> could be inject to it as osgi service in another bundle.<\/p>\nYou could exclude more than one bean adding -e<\/code> switch for each of them, e. g. -e my1 -e m2 -e myBean123<\/code>.<\/p>\nConclusion<\/h2>\nBlueprint is great for dependency injection for OSGi bundles, but it is easy to create quite big context containing many domains. It is much easier to recognize or search for such domains using blueprint visualizer script.<\/p>\n <\/p>\nYOUR CODE HRER<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"What is blueprint?Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could hav…\n","protected":false},"author":54,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[606,50,44,608],"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026"}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=13026"}],"version-history":[{"count":14,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions"}],"predecessor-version":[{"id":14926,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions\/14926"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=13026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=13026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=13026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/gist.github.com\/alien11689\/560e189859107159126e71d45065ec51\/raw\/d2a8b16e5741a1debf36168953f5608ec91a1656\/joinFirstCut.png\"){kind=link}
![image with all beans from all files<\/a>.<\/p>\nExclusion<\/h2>\nSometimes it is difficult to spot and extract other domains. It will be easier to do some experiments on blueprint. For example, bean my1<\/code> is a dependency for too many other beans. You could consider converting my1<\/code> bean to OSGi service and extracting it to another bundle.<\/p>\nLet’s exclude my1<\/code> bean from generation via -e<\/code> option and see what happens:<\/p>\n.\/run.sh target\/otherStuffWithoutMy example\/firstCut\/otherStuff.xml -e my1<\/pre>\nResult is available here<\/a>. Now we see, that tree with root bean myFactoryBeanAsService<\/code> could be separated and my1<\/code> could be inject to it as osgi service in another bundle.<\/p>\nYou could exclude more than one bean adding -e<\/code> switch for each of them, e. g. -e my1 -e m2 -e myBean123<\/code>.<\/p>\nConclusion<\/h2>\nBlueprint is great for dependency injection for OSGi bundles, but it is easy to create quite big context containing many domains. It is much easier to recognize or search for such domains using blueprint visualizer script.<\/p>\n <\/p>\nYOUR CODE HRER<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"What is blueprint?Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could hav…\n","protected":false},"author":54,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[606,50,44,608],"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026"}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=13026"}],"version-history":[{"count":14,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions"}],"predecessor-version":[{"id":14926,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions\/14926"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=13026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=13026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=13026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/gist.github.com\/alien11689\/560e189859107159126e71d45065ec51\/raw\/d2a8b16e5741a1debf36168953f5608ec91a1656\/joinFirstCutGrouped.png\"){kind=link}
![here<\/a>. Now we see, that tree with root bean myFactoryBeanAsService<\/code> could be separated and my1<\/code> could be inject to it as osgi service in another bundle.<\/p>\nYou could exclude more than one bean adding -e<\/code> switch for each of them, e. g. -e my1 -e m2 -e myBean123<\/code>.<\/p>\nConclusion<\/h2>\nBlueprint is great for dependency injection for OSGi bundles, but it is easy to create quite big context containing many domains. It is much easier to recognize or search for such domains using blueprint visualizer script.<\/p>\n <\/p>\nYOUR CODE HRER<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"What is blueprint?Blueprint is a dependency injection framework for OSGi bundles. It could be written by hand or generated using Blueprint Maven Plugin. Blueprint file is only an XML describing beans, services and references. Each OSGi bundle could hav…\n","protected":false},"author":54,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[606,50,44,608],"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026"}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=13026"}],"version-history":[{"count":14,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions"}],"predecessor-version":[{"id":14926,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/13026\/revisions\/14926"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=13026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=13026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=13026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"https:\/\/gist.github.com\/alien11689\/560e189859107159126e71d45065ec51\/raw\/d2a8b16e5741a1debf36168953f5608ec91a1656\/otherStuffWithoutMy.png\"){kind=link}