[jsr-314-open] default values for composite component attributes

[Dan Allen]

On Tue, Apr 28, 2009 at 12:59 PM, David Geary <clarity.training at 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.

-Dan

-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jsr-314-open-mirror/attachments/20090428/65a96db9/attachment.html