Re: setting value of attributes like binding, value, validator, converter, and required in java

I recommend asking this on the facelets list. All you do is pass your binding/value/validator/converter/required values into your composition template. You can pass them either as attributes or as body text (for validators and converters, this often makes more sense).The only tricky part

Re: setting value of attributes like binding, value, validator, converter, and required in java

Clay makes easy work of reusing a view fragment with what it calls symbols. Symbols are a substitution layer before the EL becomes a binding object (http://struts.apache.org/struts-shale/features-reusable-views.html). For example: span jsfid=/widgets.html label=submit bean=mybean action="">

setting value of attributes like binding, value, validator, converter, and required in java

I have parts of forms I would like to reuse from page to page but because binding, value, validator, converter, and required are all specified in the XML code I can't reuse the code. I have been playing with the idea of removing these settings from my XML code completely and instead setting