Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openwebbeans.apache.org/openwebbeans-impl.mdtext
Karl Kildén Index: trunk/content/openwebbeans-impl.mdtext =================================================================== --- trunk/content/openwebbeans-impl.mdtext (revision 1528692) +++ trunk/content/openwebbeans-impl.mdtext (working copy) @@ -18,5 +18,20 @@ # OpenWebBeans Core -Coming soon... +**Hint:** The actual jar is called impl and is the implementation of OpenWebBeans core. +OpenWebBeans follows the design principle low coupling and high cohesion. Everything needed to actually be a working CDI-container makes up +OpenWebBeans core. All the logical parts in core have high cohesion with each other and will age in approximately the same rate. +To conclude impl is the CDI-container as such and nothing more nothing less. This way core is completely unaffected by the release cycles of other frameworks and the coupling is not only low, it's virtually nonexistent. + + + +Ignoring this design principle is no joke all though the result would probably feel like one. Imagine for example if the power outlets in your house was tightly coupled to your various devices. +The newest and coolest smartphone or what have you would probably not be as tempting if it required you hiring an electrician to rewire your entire house. To make it more ridiculous the new wiring would be non compatible with your TV because it's two years old. + +So if OpenWebBeans was built the other way around with tight coupling and low cohesion the newest version would have to drop support for everything but the newest frameworks or be a hot mess with version checks and endless if - else cases between all the framework +combinations. Naturally it would only get worse and worse over time. + +Puh... Glad we avoided all that and have the exact opposite result, the latest OpenWebBeans still support JSF 1.2 no trouble at all. +Likewise there's still full support for Tomcat 6 and so on. The end users get to combine their own mix och plugins and can include +exactly what they want (including custom plugins) yet nothing they don't need. The committers behind OpenWebBeans also have a much easier maintenance process and can focus on features, speed and robustness rather then the compatibility matrix. \ No newline at end of file
