That's actually how I had it. The reason I made the change is that I have CRUD
type functionality broken up over two SFSB components. One of them handles new
object creation and the other handles list/update/delete. When I create a new
object however, even if I inject the list/update bean int
It is designed so that you can have an event-scoped bean that has a page-scoped
datamodel.
If you have a conversation scoped bean, it does not really make sense to have a
page-scoped datamodel. Just use a conversation-scoped datamodel (the default).
View the original post :
http://www.jboss.co
Right, but as I understand the @DataModel annotation it doesn't outject the
actual annotated List into PAGE scope, it outjects a DataModel that wraps the
List, so why then when the DataModel is reconstituted is it overwriting the
perfectly good version of the wrapped List that is still containe
This is how page scope works. If you declare that the list if kept in PAGE
scope, that means it is serialized to the client.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949905#3949905
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
Ok, I'm obviously not being very clear.
I have a conversation scoped bean which contains a List. The List is outjected
using @DataModel(value="model", scope = ScopeType.PAGE). The DataModel is then
used in the normal way:
...
Now when the response is submitted I understand that a serialized
huh? its necessary since it is going to the client and back.
if you want some other behavior use conversation or session scope.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949890#3949890
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=pos
I see your point, but this seems to be mostly related to the @DataModel
annotation and it's implementation. What worries me more than the fact that my
@DataModelSelection is serialized and becomes a detached object is that every
object in the List that was outjected using @DataModel becomes det
Storing page-scoped state on the server would be very memory hungry.
All you need to do is merge() before remove().
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949882#3949882
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=re
I realized that shortly after I sent the post. Turns out serialization is
occuring because I had my @DataModel outjected to the page scope. I can see
why some type of storage within the component tree would be necessary between
requests, but couldn't the value binding be stored instead and the
In principle this would work, but you havn't shown any code, so we can't tell
you what you are doing wrong.
Make sure you are not serializing the entity instance.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949753#3949753
Reply to the post :
http://www.j
10 matches
Mail list logo
