We use the begin-conversation-on-GET pattern extensively in our app -- typically when starting a conversation about a specific database object.
The problem with this model is that we're effectively creating far too many unnecessary conversations as a user bounces around freeform in the web application UI. For example, there's no reason to have multiple conversations in a session ABOUT "editing product 123" (in our application). Besides making our UI flow terribly strict to cut down on conversation creation, are there any other solutions (current or planned)? Ryan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950528#3950528 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950528 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
