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 into the create bean and call a method to set its query results to null, a new DataModel is not outjected. I figured by changing the outjection to page scope it would force the List to be pulled from the bean each time. At this point I'm programatically removing the DataModel from the conversation when a new object is created, but I don't like the fact that the create bean has to be aware of an outjected list that has nothing to do with its function. Any advice?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949965#3949965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949965 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
