Red Hat

Natural Conversations in Seam

Posted by Pete Muir    |       |    Tagged as Seam

One of the features I am most pleased to see in Seam 2.0.1 is Natural Conversations. Why?

Easy redirect to existing conversations

It can be useful to redirect to an existing conversation if the user requests the same operation twice.

Take this example:

You are on ebay, half way through paying for an item you just won as a Christmas present for your parents. Lets say you're sending it straight to them - you enter your payment details but you can't remember their address. You accidentally reuse the same browser window finding out their address. Now you need to return to the payment for the item.

With a natural conversation its really easy to have the user rejoin the existing conversation, and pick up where they left off - just have them to rejoin the payForItem conversation with the itemId as the conversation id.

User friendly URLs

I've always been a strong believer in the use of user friendly, descriptive, URLs. For some applications this is of less import, of course - the largest (pre Seam) application I wrote was really bad at this as it used frames ;-) . For me this consists of:

  • a navigable hierarchy - I can navigate by editing the url
  • a meaningful URL (like this Wiki uses -- so don't identify things by random ids)

The first of these is certainly possible in Seam with the use of URLRewrite (I'm also looking forward to seeing stronger integration between URLRewrite and Seam's pages.xml), but the second was harder until now.

Now, with natural conversations, when you are building your hotel booking system (or, of course, whatever your app is) you can generate a URL like http://seam-hotels/book.seam?hotel=BestWesternAntwerpen (of course, whatever parameter hotel maps to on your domain model must be unique) and with URLRewrite easily transfor this to http://seam-hotels/book/BestWesternAntwerpen.

Much better!

Deprecates explicit synthetic conversation ids

I really didn't like the use of explicit synthetic conversation id - they just feel really ugly to me. You know that gut feeling you get about some things? Explicit synthetic conversaton ids are like that for me.

This is available in the recently released 2.0.1.CR1.

I hope this inspires you to go out and think about how you can incorporate natural conversations into your application.

back to top