Setting the "class" Attribute for Custom Tags

For native JSF tags, setting the "class" attribute performs as you'd expect; however, in user-defined tags, setting the "class" attribute results in the exception java.lang.IllegalArgumentException: Component property class is not writable Which is how we've behaved traditionally; using the "st

Packaging Flows in Directories Convention

I'm a bit unsure about the validity of a particular flow packaging convention. Consider that we have a flow defined with the following structure: /WEB-INF/flowname/flowname-flow.xml /flowname/flowname.xhtml /flowname/flowname-2.xhtml /flowname/ Assuming that no start node is specified in flowna

Re: EL 3.0 Static Field References

ver class and > ExpressionFactory.getStreamELResolver(...) method before > add both EL resolvers. > > If MyFaces jars cannot locate these classes, the EL resolvers > are not loaded (because it assumes EL < 3.0), and the > described behavior will happen. > > regards, > >

EL 3.0 Static Field References

Hi All, I'm running into some issues trying to test the EL 3.0 functionality on MyFaces 2.2.7 + Tomcat 8.0.16. My understanding is that we should be able to reference static fields/methods directly from facelets, eg. Boolean.TRUE test: [] should return "Boolean.TRUE test: [true]". This

Re: Issue with javax.faces.SEPARATOR_CHAR and commandLink

ion > Date: 08/20/2014 01:15 PM > Subject: Re: Issue with javax.faces.SEPARATOR_CHAR and commandLink > > Hi > > 2014-08-20 6:36 GMT-05:00 William Lucy : > > > > > > Hello all, > > > > We've come across an issue while trying to modify the > > j

Issue with javax.faces.SEPARATOR_CHAR and commandLink

Hello all, We've come across an issue while trying to modify the javax.faces.SEPARATOR_CHAR - changing it to a non-colon character seems to break h:commandLink actions. For example, with the separator character set to a hyphen "-", the following navigation does not work (the output link just tr