"Homer J." wrote : What do you mean with explicit & implicit attributes? Is
it bad that the email tags are derived from the obfuscator tags?
The spec suggests
anonymous wrote : The render-independent characteristics of a user interface component are
represented as JavaBean component properties, following JavaBeans naming conventions .
Specifically, the method names of the getter and/or setter methods are determined using
standard JavaBeans component introspection rules,
- i.e. attributes should have getters and setters (this is a convention we follow with
other JSF components in Seam). It's fine to back the getters and setters with the
attributes map if you like.
anonymous wrote : Regarding the EL: if you do something like:
| <s:email value="#{user.email}" /> it will work so I'm not sure
what you mean.
Sorry, you are right, I'm not familiar with the attribute map - it's cleverer than
I thought!
anonymous wrote : Regarding nested tag support: while I theoretically agree with you there
is not much point in it because now both tags are derived from HtmlOutputText
I think the email one needs to be based conceptually on h:outputLink, which does allow
nested text
anonymous wrote : and therefore behave in a similar way. E.g.:
|
| So everything in the body is rendered before the tags - which can be done by simply
writing it before the tag too.
Yes, you are right. This is broken imo ;) - might be worth "fixing" it...
anonymous wrote : Last but not least you said that the default behavior of the email tag
should be to do no obfuscation.
Up to you :) - that was my initial reaction, but I really don't have strong feelings!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042354#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...