Hi; Every framework has a some sorts of configuration to use :). OWB is targeted for Java EE 6 servers that provides all Java EE defined requirements that one of is that injecting Java EE resources into managed beans. Therefore our SPI is provided to container vendors implementing Java EE 6 servers that want to use our OWB core. If anyone wants to use OWB core in its environment, he has to provide its own SPI implementations.
Plugins are much more coarse grained than SPIs and they are totally different usage then SPIs. For example, we mainly use plugins for supporting some technologies that may not be included in lightweight containers for example, Tomcat, Jetty etc. In other words,they are mainly implemented for extending the OWB core. They may not be related with Java EE Requirements or TCK etc. On the other hand, SPIs are required by Java EE/JSR-299 specifications. Every container vendor must provide those services. Currently we have three plugins 1* JMS Plugin --> For JMS support 2* EJB PLugin --> For embedded OpenEJB in Tomcat support 3* JSF PLugin --> JSF support on conversations.(Maybe this may not be a plugin) SPIs are different from plugins. OWB core requires to use SPI implementation to do its job but it is not dependent on any plugin. Therefore, we provide Default Services. For resource injections, OWB requires to use "Resource Injection Service" for Java EE requirements. Lastly, OWB is part of the Java EE 6. Please do not swallow this. For configuration issues, as I said in the beginning every framework/server has some own configuration files. It provides default configurations as builtin. If user do not happy with defaults, it has to write its own and obey the rules of the OWB. >>>Otoh our plugin mechanism is pretty old, and possibly can get replaced via the standard extension mechanisms? wdyt? I do not support to change it. As I said, plugins are mainly used for extending the OWB core. For example, if we wish to write something that is not necessary to implement regarding to Java EE/JSR-299 we could write plugin for it and anyone use it with dropping it into classpath. 2010/2/19 Mark Struberg <[email protected]> > Hi! > > I know it doesn't make that much difference from a technical perspective, > but having > > > org.apache.webbeans.spi.ResourceInjectionService=org.apache.webbeans.se.DefaultResourceInjectionService > > as a default means that the simple dropping your plugin in the classpath > and all 'just works' (tm) doesn't work anymore. > > instead each user has to manually create an openwebbeans.properties file > and maintain all changes we run through. > > Think this is not really an increase of user-friendlyness. > > Otoh our plugin mechanism is pretty old, and possibly can get replaced via > the standard extension mechanisms? wdyt? > > LieGrue, > strub > > __________________________________________________ > Do You Yahoo!? > Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz > gegen Massenmails. > http://mail.yahoo.com > -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
