We're still trying to feel that out ourselves. We are getting prepared to have some community design discussions. Stay tuned.
I'd really love that for Seam 3 it were possible to do anything in 3 different ways:
- Programmatically in a typesafe way, with a comfortable api.
- Declaratively (with annotations)
- Using XML configuration files
with exactly that priority. Two examples where this is particularly lacking is for navigation, currently the only way to control it is with XML configuration files which make it really hard to deal with complex cases, and the fact that there is still no debugging support available makes it even harder.
Conversation management is another area where a comfortable api could make it a lot easier to deal with nested/recursive stuff.
this JIRA brings up a generic problem with using XML
code. If it was possible to refactor pages.xml content into an API/module/class, etc., then perhaps we could debug...