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
My applications is still running on jboss 4.0.5, which means that I can't test
the new Seam (as Seam is now dependent on jboss 4.2.0).
I have been trying to port my app to run with the new jboss and seam.
Unfortunately I am struggling a bit (the move from myfaces to jsf-ri appears to
be
I have managed to get the relevant part of my app running under the new
jb4.2.0. Seems the fix has done the trick !
Great stuff.
Thanks.
L
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038459#4038459
Reply to the post :
In Bean B try sharing with
@In @Out DataModel sections;
If you're trying to manipulate the DataModel in B. Otherwise your
investigation seems to show that Seam isolates the @DataModel data binding on a
per bean basis. Not sure why. Gavin is around here somewhere, try adding a
post to the
Louis, post your source for Bean A and Bean B.
@DataModel does a conversion to a DataModel and then outjects the result - it
doesn't do a subsequent injection. Based on your description above I wouldn't
expect sections, created in A, to be available in B if annotated with
@DataModel (you
anonymous wrote : ...it doesn't do a subsequent injection
Really? Although I only outject in my code, I thought DataBinders performed
bidirectional binding. Why else implement a getWrappedData() DataBinder
method?
View the original post :
Hmm, looks like you are right, but injection will only occur if
null != null
http://fisheye.jboss.com/browse/JBoss/jboss-seam/src/main/org/jboss/seam/Component.java?r1=1.232r2=1.233
I'll fix it :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038064#4038064
Ok, there is a fix in CVS for this.
Could you test it? Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038073#4038073
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038073
12 matches
Mail list logo
