On Tue, Apr 28, 2009 at 12:59 PM, David Geary <clarity.training@gmail.com> wrote:

I'm not seeing default values applied to composite component attributes when those attributes are not specified in the using page.

My experience was the same. I was really hoping that this would work to avoid having to use <c:set> tags inside of my composite component.

I'm also not seeing an difference in behavior in my app when I specify that an attribute is required and I don't supply it. The javadocs for the composite:attribute required attribute simply say:

"True if the page author must supply a value for this attribute."

But it gives no insight as to what should happen when the page author fails to supply a value. Do we throw an exception? The result of not providing a required attribute should be specified in the javadocs, IMO.

I believe this relates to the "strict" mode functionality we were discussing in a separate thread:

http://archives.java.sun.com/cgi-bin/wa?A2=ind0904&L=JSR-314-OPEN&P=170

But yes, it should be enforced, IMO.