Werner Punz wrote:
That framework looks really interesting...
Especially the conversational stuff, which solves
many issues many of the dialog systems have.
I agree it looks very interesting. I have not taken it out for a spin
yet (other than the demo) but I have read the docs a couple of times. My
notes:
1. I also like the conversational model. It will help tremedously with
issues like the back button, two browser windows and garbage collection.
The ability to extend the framework (e.g. @LoggedIn) is also nice.
2. I am not so happy about the mixing of control statements with context
statements (i.e. @if types vs @stateless).
3. I think the choice of @In and @Out was not the best. While I can see
@In being a reference for 'inject', I have trouble with the creation of
a new verb 'outject' to address the other condition. Wouldn't the
antonym for inject be eject? At any rate, I see these directives are
more import and export concepts.
4. I would really like to see what is being proposed for the business
workflow aspect of this. The document makes many references to jBPM, so
I would assume that that is where they are going to start, but it would
be interesting to see more details on this.
5. Its a really nice idea to offer other contexts support via
annotations. (e.g. hibernate context)
6. I wonder how long it will be before different annotations namespaces
collide and we start to go to a more explicite naming scheme such as
@seam.In to help resolve it.
-david-
