...
Brent : Yes. Three ways (1) MVC RequestDispatcherServlet, (2) non-MVC RequestContextListener, (3) older Servlets use a Filter. Maybe need to wire bean in as a proxy rather than FactoryBean. However, Web Flow has multiple requests and responses, so Spring ... uses a proxy , not might work better vs a FactoryBean because that won't work.
Scott : Thought it worked if we use prototype scoped beans.
Brent : ExactlyUnclear on the bean life cycle in Webflow. FactoryBean might work.
Scott : Actions get created when flow is about to run the action. The flow requests the bean. The FlowExecutor does this.
...
Brent: Collaborator components should be wired with Spring. Runtime state needs to be transferred in Context. Gray area ... requests and responses are kinda gray, since they are known to Spring container maybe . Maybe are a 3rd distinct type. Maybe we should use injection as collaborators.
...
Brent: Threadlocals can be dangerous if used improperly. Especially if buried in an undocumented library. But ok if used carefully and consciously.
Scott: Threadlocals have flavor of global variables.
...
Scott: Feel good that we can replace Web Flow if we need to.
Brent: True. Attractiveness of Webflow was: 1) Built-in conversation support , use2) people's existing familiarity with it, books, documentation for it, etc.
Scott: Subflow is attractive. Conversation state will need to be overriden, so we might lose benefits of using built-in mechanism. Like to use Web Flow but it could be swapped out.
...
Brent: Not really suggesting annotations for the IdP, just auto-wiring via XML config.
Scott: Want auto-wiring of boilerplate.
...
Will spend today sketching out ideas for context objects to use for some of the important system components like authentication and sessions so Brent and I can review next week.
Scott: Playing with coding of stateful beans. Looking at (1) Spring Web Flow does not handle exceptions as transition points ?
Marvin: Yes, an onException clause can be added.
Scott: Should systematically map Exceptions into Events...could automate by catching exceptions and morph into Events. Less comfortable with RuntimeException handling, could be done similarly, if we want to. Probably a premature optimization to implicitly return "proceed". Will go undo.
Scott: Talking with Brent, already not totally happy with ProfileRequestContext as a baked in context, will talk with Brent next week. We do have some ProfileActions that will become MessageHandlers, need a consistent execution model, pre|postExec consistency. If we have MessageHandlers, we will need Actions to wrap them.
Scott: Will spend time thinking about context tree for authn etc., talk with Brent.
Tom: I2 ?
Scott: Board meeting will be open for first hour at 2.
Paul
Still seeing session bug with one particular clustered customer, 2x or 100x per day.
Tom
Worked through some installation, configuration, and upgrade ideas.
Topics
Decisions
Guava Optional vs @null
Tom AI : look at second Storage API try.
Scott: Leaning to @null. Didn't see lots of support for Optional. Consider multiple methods vs Optional parameters.
Coding convention : getLdapUrl or getLDAPURL
...