>>>This also has the side effect that we now for the first time really use JSF2 functionality, and thus it would not be possible to use OWB with JSF-1 >>>applications anymore
Actually this is not correct observation. OWB does not depend on any JSF specific implementations. And you know that core OWB does not require any JSF library (Plugin model). You can use OWB with/without JSF. >From JSF Perspective ---------------------------------------- Currently we are providing CDI Conversation Context via our "webbeans-jsf" module. This module has a dependency on "MyFaces 2.0.0-alpha API" as an optional because JSF libraries are provided at runtime via containers/developers. As you see, even webbeans-jsf module does not depend on any JSF implementation or specific JSF 1.2/2.0 API etc. Therefore we can put any JSF 1.2/2.0 related code here, because this module uses 2.0 API and 2.0 API is backward compatible with 1.2 API (Means that 1.2 APIs are contained in 2.0 API). If anyone would like to use our JSF 2.0 functionality (like ViewScoped), then he requires to add JSF 2.0 implementation libraries into his application class path. In summary, OWB is not related with JSF implementations. It uses JSF2 API, that is all. If anyone wants to use our JSF2 funtions, he has to provide runtime JSF2 libraries. For example, some JSF samples are currently run with JSF 2.0 libraries while some of them uses JSF 1.2 libraries. Both of them uses webbeans-impl and webbeans-jsf modules. >From Extensions Perspective ------------------------------------------- But, it is reasonable for me that we can define "webbeans-extensions" module that is independent from CDI implementations. But I am not sure, whether ot not this module depend on any OWB specific code! Thanks; --Gurkan 2010/1/12 Mark Struberg <strub...@yahoo.de> > Hi! > > I have coded the javax.faces.bean.ViewScoped handling and it turned out > that I do not need anything OWB special. So this i a completely CDI > independent portable implementation, and as such I'm in favour to _not_ add > it to openwebbeans-jsf but to a new 'extensions' module. > > This also has the side effect that we now for the first time really use > JSF2 functionality, and thus it would not be possible to use OWB with JSF-1 > applications anymore! But since I consider OWB + JSF-1 a very important > scenario (for making migration easier and due to the fact that there is > still no JSF-2 component taglib on the market!), I don't like to add this to > openwebbeans-jsf. > > This opens the general question on how we cope with JSF-1 vs JSF-2 in the > future. > > LieGrue, > strub > > > > -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
