Hi Mark, I myself did not write this code, but I think it was written because it was/is not known if all things will work with Java EE6's EL. So I guess it's a kind of a reminder.
Furthermore I don't think that there are any web.xml parameters to change this behavior. Can you or someone else confirm the backwards compatibility? If yes, we could remove this code! Regards, Jakob 2010/2/18 Mark Struberg <[email protected]> > Hi! > > Currently the BeanValidator has the following code: > > if (_ExternalSpecifications.isUnifiedELAvailable()) > { > //TODO: Implement when Unified EL for Java EE6 is available. > throw new FacesException("Unified EL for Java EE6 support is not yet > implemented"); > } > > I'm using EL-2.2 in MyFaces-2.0.0 and now switched from using > facelets-1.1.15.B1 to the built-in facelets-2. > > After that I get this rather unfunny Exception in the code above. > > I tried to remove this clause in BeanValidator and so far all works well. > Afaik the new EL-2.1 interface should be backward compatible to the EL of > JSF-2.1, isn't? Is this Exception only meant as a 'reminder' to check it's > compatibility, or is there any already known problems? > > Maybe there are any hidden web.xml settings treasures I could try? > > Oh, and please excuse my failing to not dig into the whole depth of the > code on this topic this time, because I'm currently pretty short on time :( > > txs and LieGrue, > strub > > __________________________________________________ > Do You Yahoo!? > Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz > gegen Massenmails. > http://mail.yahoo.com >
