Thanks for your prompt response. I'm looking forward to giving this a shot, and I appreciate your assistance.
In the hotel example, there's only one action that can be performed over the hotel list, and there's only one "termination" point of the conversation (the confirm() method).
If I have methods for add, change, and delete all within the same action,
1) can I specify multiple methods with the @End annotation
2) Is it good design to do so?
Yes, multiple @End used is appropriate.
The conversation scope is defined by a series of contigous HTTP Posts, which may involve searching, selection, etc-- collecting data as you go, then allowing you to use the @End to finish the currently active conversation. It doesn't even have to be on the same Object.
Have I mentioned that Seam is sweet?
It seems so simple, I thought I just *had* to be misunderstanding something.
Thanks again for the response.