Good thoughts on the idMethod and valueMethod.
What I meant by "entities generating selectable lists" is that in the entity
could be defined as @Selectable (therefore invoking the generation of a
converter (for the object type) and attaching it to the jsf implementation).
so you would have:
@Entity
| @Name("customer")
| @Selectable(idMethod="...", valueMethod="...")
| public class Customer{
| ....
| }
this would then mean that any location you have a list of customers you could
have you own method to create the list of customers (perhaps passing them
through a Seam converter to SelectItem's), and the converting would be handled
automatically.
But as I said this could be tying view functionality into the object model?
Hope this explains that.
If you don't have anything pre creating the converters on the fly (annotating
entities) then the developer would still have to do this manually which is
extra labour that could be automated.
Interesting.
James
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927171#3927171
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927171
-------------------------------------------------------
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
