-
1. Re: Seam outjection problem, is this a bug?
gavin.king Apr 14, 2006 4:21 PM (in response to kh2ouija)You have to actually *call* the component for @DataModelSelection and @Out to have any effect.
-
2. Re: Seam outjection problem, is this a bug?
kh2ouija Apr 17, 2006 6:25 AM (in response to kh2ouija)Thanks for answering me.
Let me get this straight. @Out'd objects only become visible to a new view after a call to the component from that view? -
3. Re: Seam outjection problem, is this a bug?
kh2ouija Apr 17, 2006 6:31 AM (in response to kh2ouija)... that is, even if the component has already been used in a previous view? It is a SFSB with Seam session scope.
-
4. Re: Seam outjection problem, is this a bug?
gavin.king Apr 17, 2006 11:47 AM (in response to kh2ouija)No. Once the object is outjected to the session scope it is visible to all views.
-
5. Re: Seam outjection problem, is this a bug?
kh2ouija Apr 18, 2006 3:25 AM (in response to kh2ouija)I'm not sure I understand. The component has been used before, when displaying the DataModel. When the user clicks an item in that table, it is set as the selectedItem and the view is changed, but the selectedItem is not visible. It only becomes visible (outjected?) after a do-nothing call to the component from that view, or after referencing it directly from the component with a getter (which only needs to be done one time, as explained in my first post). What am I missing here?
-
6. Re: Seam outjection problem, is this a bug?
gavin.king Apr 18, 2006 10:39 AM (in response to kh2ouija)I'm not sure what you are missing. This stuff is exactly like the Seam message list example.
Perhaps you are outjecting to the EVENT scope, instead of the SESSION scope. -
7. Re: Seam outjection problem, is this a bug?
kh2ouija Apr 18, 2006 11:22 AM (in response to kh2ouija)I have list.jsf which contains the datatable. When the user clicks, an action method is called on the backing component which does nothing else than redirect to detail.jsf - the selectedItem is not visible here.
I changed the method to return null so that it returns to list.jsf - the selectedItem is visible here, yes, like in the messages list example. So this only happens when the view is changed. The component (equivalent of the MessageListBean from the example) has session scope.
case 1) list.jsf -> sfsb.select() -> list.jsf
#{selectedItem} visible
case 2) list.jsf -> sfsb.select() -> detail.jsf
#{selectedItem} not visible
If you say that's the intended behaviour, so be it, sorry for insisting. Thanks. -
8. Re: Seam outjection problem, is this a bug?
gavin.king Apr 18, 2006 11:25 AM (in response to kh2ouija)scope of component != scope of outjected object
try Out(scope=SESSION)
are you sure you don't have a <redirect/> in your navigation rule? -
9. Re: Seam outjection problem, is this a bug?
kh2ouija Apr 19, 2006 3:29 AM (in response to kh2ouija)Yes, there was a redirect tag there, got rid of it and now it works. I wouldn't have thought of that...
-
10. Re: Seam outjection problem, is this a bug?
kh2ouija Apr 19, 2006 3:29 AM (in response to kh2ouija)Thanks.