Thanks Pete... my Eclipse code completetion, combined with the default value
tripped me up a bit.
Thanks
L
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4094362#4094362
Reply to the post :
You were using unintentional behaviour in Seam. I fixed this properly a while
ago.
What you need to do is inject the values in the second bean:
@Stateful
| @Name(sectionManagementBean)
| public class SectionManagementBean implements SectionManagement {
| @In(#{sections.wrappedData})
Great stuff. Thanks Pete.
(I will have to update my code in a few places where I have used this behavior,
but not a big problem)
A quick test showed that it needs to be :
| @In(#{sections.wrappedData})
| private ListSection sections;
|
| @In(#{sections.rowData})
|
One question regarding:
| @In(#{sections.rowData})
| @Out(required = false, scope = ScopeType.CONVERSATION)
| private Section section;
|
Is there a way that one can say .. required=false using the above annotation.
At this point I get an exception when I try to use execute
@In(value=..., required=false) - value is the defualt attribute for an
annotation
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4094259#4094259
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094259
