hi ron, first of all: great news & thx!
@window-scope: e.g. menu-state per window or if you need to support one user per window, you can store the active user in a window-scoped holder. @view-controller: e.g. @PreRenderView to load data before the rendering-process,... you could have a look e.g. at [1] regards, gerhard [1] https://github.com/os890/tomee_mf_stack_001/tree/codi2ds 2014-06-06 19:14 GMT+02:00 Ron Smeral <[email protected]>: > Hi, > > a small team in JBoss QE has started covering DeltaSpike with examples. > We've identified ~30 features/use-cases and come up with ~10 ideas for > examples that could demonstrate those features. We plan to implement this > during the summer. > > However, we had a hard time thinking of real world use cases for certain > features, like: > * multi-window handling, i.e. the window scope: What are the real uses for > this, where the conversation scope doesn't suffice? > * view-controller callbacks: I understand that it allows e.g. to have a > shared controller for multiple views (right?), which implements a common > aspect, or just to easily perform operations at certain JSF phases. But > what would that shared aspect or those operations be, in a real > application? Maybe except for the classics that are logging and security. > > I'm writing this to the dev list, as I assume that most DS committers use > DS in production and can provide some insight into how DeltaSpike is > commonly used. > > Thanks! > > Regards, > Ron > > -- > Ron Smeral > JBoss Quality Engineer > Brno > >
