Adrian, you're right. WAS v8.5 is JSF 2.0 only. My error Having said that I'm quite sure that MyFaces v2.0.5 is not bundle "vnilla", without any modifications. IBM backports bug fixes when necessary (ie to address customers PMRs) Current version of WAS v7.0 includes a a JSF RI v1.2_07 (display "1.2_07-b03-FCS" on startup) with many many bugs that have been fixed in newer versions of JSF RI v1.2 (I know it for sure because I personally opened many PMRs that were addressed in JSF RI and have been delivered as WAS fixpacks) So I would not be surprised that the JSF v2.0 MyFaces implementation included in WAS v8.5 includes bug fixed in newer version of MyFaces v2.0, but It doesn't seem to be at the v2.1 level tough
2012/12/20 Adrian Gonzalez <adr_gonza...@yahoo.fr>: > Sorry, on another topic : > * titou10 can you confirm me that WAS 8.5 bundle a JSF 2.1 implementation ? > > I'm with WAS 8.5.0.1 and it provides MyFaces 2.0.5-SNAPSHOT : > * see websphere bundled jars [1] > * see websphere infocenter they mention only JSF 2.0 and JSF 1.2. > > Thanks and sorry for deviating > > [1] Look at > <WAS_HOME>/plugins/com.ibm.ws.jsf.myfaces.jar#META-INF/DEPENDENCIES file, you > should see Apache MyFaces JSF Core-2.0 API > (http://myfaces.apache.org/core20/myfaces-api) > org.apache.myfaces.core:myfaces-api:jar:2.0.5-SNAPSHOT > > [2] > http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.base.doc/ae/container_webapp_rrd_jsfimplementation.html > > ________________________________ > De : titou10 titou10 <titou10.tito...@gmail.com> > À : deltaspike-users@incubator.apache.org > Envoyé le : Jeudi 20 décembre 2012 16h00 > Objet : Moving from Seam 2: CDI + DeltaSpike : With EJBs or without EJBs? > > We are in the process of redefining our development stack and we need > to do it ASAP as we have a new big project (1 year+) starting very > soon > The current dev stack is (Used in more than a dozen application > currently in production) : > - WebSphere v7.0 (+JPA2 fp) > - JSF v1.2 (JSF RI from WAS) > - JPA2 (Hibernate v3.6) > - EJB v3.0 > - Seam v2 > Our projects are split into a WAR, a JPA module, an EJB module and > sometimes a "batch" module for nightly process outside WAS (it usess > the JPA and the EJB module) > > The target is : > - WebSphere v8.5 > - JSF 2.1 (MyFaces from WAS) > - JPA2 (OpenJPA from WAS or Hibernate v4) > - CDI (OWB from WAS) > - DeltaSpike > - ? EJB v3.1 > > For starting we'll use CODI instead of DeltaSpike and update to > DeltaSpike when a stable release will be available. It seems it should > not be a big problem as DeltaSpike seems very "close" to CODI > > Now the question: EJBs or no EJBs? this is the question... > With CDI + CODI/DS extensions, the benefit of using EJBs are not > obvious and we think about not using them anymore. Here are some > points > - EJB transaction managment: @Transactional annotations seems to solve this > - EJB security : our EJB are not called remotely and we don't puts > security on EJB methods anynway > - EJB pooling: not a real arguments as our applications are not *that* > in need of very high performance > - StateFul vs Stateless : use CDI/CODI scopes instead > - Stateful timeout: CDI/CODI ConversationScoped has timeouts > - Stateful+Stateless serialisation access: Don't know if CDI is handling this > - Resources injections (@Resources..) can be easily solved > I would like to know your opinions on this. > Thx > (I hope this is the good place to ask this kind of question, this post > could have been posted to the CODI or Seam 3 mailing lists too..)
