1 2 Previous Next 17 Replies Latest reply on Jul 9, 2006 11:58 PM by gavin.king Go to original post
      • 15. Re: 'edit' object through datatable page
        gavin.king

        Yes but note that the only reason that the blog example uses a page action instead of pull-style MVC is that we wanted to throw a Http 404 response code when the item was not found - which we cannot do once we start rendering the page.

        If it was not for this, then I would have used pull MVC, and interrogated the request parameter from an @Factory or @Unwrap method, just like I do with the seach screen in the blog example.

        • 16. Re: 'edit' object through datatable page
          trouby

          Hey,

          back to this, I still confused a little bit,


          Using pull MVC style, th search screen in the blog example use @CREATE/@UNWRAP annotations in order to set the result and outject the blogEntry list,

          This fits when you have such a 'search service' which is dedicated for the 'search action'

          What if I have one EJB for all actions? I can't use @CREATE, since I call this EJB for many porpuses,

          I'd really like to itterogate the request parameter and outject the corresponding entity to the next 'edit' page -only- for a specific case where the next page is the 'edit' page for the selected DataModelSelection(i.e, the specific selected object ID)

          as always, many thanks.

          • 17. Re: 'edit' object through datatable page
            gavin.king

            Then use @Factory instead, I suppose. That way you can outject to conversation context.

            1 2 Previous Next