Ok, my brain was elsewhere while writing my previous post... Now I got your
point.
I think there shouldn't be any difference in grabbing an attr at context or
from component level: after all, in any case there is an underlying faces
context triggering the (in my case cascaded) bijections...
Also, Seam doesn't have to adhere to any (more or less silly) standard, so,
taken I'm not the only dumb here to feel a feature like this useful, I wouldn't
say that we "misunderstood the concept of seam component". Maybe that seam
developers relied too much on the example Hotel app?
Also, calling the idCat property means I have to trash the Factory-based
design, which I don't dislike at all. I would need to wrap my attrs within
| if(attr == null) {
| // Build attr
| }
|
| return(attr);
|
constructs. Not a big problem, but... oh my!
There is probably another way to let this work, which is to retrieve the idCat
attribute in initCurrentCategory from a FacesContext. But, again, it's right
few lines above! Why one would need to do that? Anyway, I'm going to try it...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936010#3936010
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936010
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
