For example, if I want the benefits of OSGi (modularization, dependency injection, etc.) without the use of OSGi, which does not use OSG, which is
Will Design Pants Work?
The two that you mentioned are at the top of my list:
-
Modularity You do not have the advantage of square loader isolation, so you are going to use your own conventions to ensure that you have " If you think switching to OSGI is in the future of your project, then you definitely have a class. Forename, Thread.Tagentech First class loaders, etc., which do not work well in the OSG environment.
Services . You have a service registry There is no benefit, which allows for finding and registering different modules in the rest of the loose coupled, so that you want to use something similar. There is, but otherwise you can use the dependency injection frame for loose couple Can you Yes.
Most of the rest of the OSG are guaranteed that the specification guarantees what will be your framework (JVM Singletons, security, management, mobility, etc.) will be on. It's probably the easiest to see what you'll miss.
No comments:
Post a Comment