master-detail without SFSB or SLSB

[kevcpu411]

I must first point out that i am extremely new to seam.  With that said.
Here is the scenario:  I have one page that presents a list of widgets in a datatable with an edit link for each row.  When the user clicks on the edit link they should be redirected to another page where they can edit and save various properties of the wideget.  There is another link where a new widget can be added to the system.  Also, I have to accomplish this using conversations without SLSB or SFSB.  Here is my first problem:

1.  Should I have everything that pertains to the widget, datatable population, editWidget, newWidget, saveWidget, cancel in the same action or should this be divided across two beans one for the actions that pertain to the DataTable page and one that pertains to the edit page? 

2.  I am having a problem where the DataModelSelection is not working properly, it seems to continuously pull the first record.  I tried using DataModelSelection and specifying an argument for the action method of type Widget.  Neither seem to work. 

3.  In the conversation scenario, if I use multiple action classes, how would the actions share the Widget object(i.e. if the user select a Widget to edit from one action how would the action associated with edit page be aware of it)? 

4.  How is the Widget object associated with a particular conversation or should I even be worried about this? 

[swd847]

I think you should probably have a look at the seam application framework, it contains ready made classes to make crud situations like this easy. Basically you need to use a home object and a query object, the query object is responsible for generating the list of entries in the data table and the home object is responsible for the edit page. There are examples of how to do this in the docs and in the examples.

[kevcpu411]

Why is the DataModelSelection not working?  Also, since I am using neither SLSB nor SFSB.  Would the seam application framework examples above work?  The other thing is that I am using stored procedures so I created a Utility class for stored procedures.  In a nutshell, I am using my Utility class instead of EntityManager whenever I use a stored procedure.  Would thi cause a problem?

[swd847]

It will work fine with using ejb's. You are going to have to post some code if you want any help with your DataModelSelection problem. Your utility class could cause problems with the entityManager, simply because hibernate is not informed of the changes that are made to the database by your stored procedures, so your application may end up with an inconsistent view of the data, but this will depend on what the stored procedures are doing. 

[swd847]

Oops, I meant to say it will work fine without using ejbs.

[kevcpu411]

My specs require that I do this without using SLSB and SFSB.  Is this possible or am I stuck?

[swd847]

Yes it will work fine, my first post was a typo.

[kevcpu411]

Also, is there a way to deal with stored procedures without having to use named queries? 

[kevcpu411]

Do you know where I can find examples of CRUD without SLSB and SFSB?

[swd847]

The link I gave you up the top, and the examples in seam. The only difference is that there is no need for a Local interface and do not put an @Stateless or @Stateful annotation on your bean. I believe the seampay and quartz examples do this.