Many of the concepts of Seam, for example the contexts and bidirectional dependency management, would also apply to a different client. I think this is a natural direction for Seam to grow, but there are no plans at this time.
Right now Seam 1.0 is very much tied into the JSF processing phases. I think this phase model makes sense for a rich client. However, I'm not sure it makes much sense for a desktop application (two tier).
When you say desktop - I wouldn't assume its two-tier. What I have in mind is still multi-tier, just using a different means of getting data to and from. It could be a voice activated front end, could be xml, could be UI, could be web.
What I'm looking to re-use is the controller and model elements of my MVC app. Workflow would push along the controller(s) where needed.
I hear what you saying about where Seam is now, and will proceed with expectations set to the appropriate level.
Well, I use the term "desktop app" to differentiate two tiers from a three tier architecture. Yes, it was me who posted as the wrong guy.
I can see where this generalization helps, although we could go on all day about it, frankly you've fully answered my question.
Thanks Christian, and since I'm just off for my long deserved Christmas break - happy holidays, and all the best for the New Year !!