[appserver-io/appserver] Allow re-attaching of SFSBs to current user sessions

[wick-ed]

SFSBs are mapped to known user sessions. Using DI in a webapp simplifies the usage of SFSBs and other beans. Problem is, that if one does something involving changes to the user session within a webapp, the SFSB previously injected does not match that changed session. Considering a login where a new session is started, this will result in "loss" of all data stored in the SFSB currently used as it is bound to any previously present session. An (active) re-attaching of currently present SFSB instances to the current session can help the bean manager to keep track of session changes without loss of beans.

UAC:

• SFSB-to-session mapping MUST be updateable/updated on session changes

[smolinari]

Thinking "immutable objects", how about expecting the app to just build a new SFSB and void/ delete the old one? Not sure if that makes sense, but it seems the kind of place to do it.

http://blog.joefallon.net/2015/08/immutable-objects-in-php/

Scott

[smolinari]

Out of curiosity, what was changed in the code?

Edit: Never mind. I found it.

Scott

[wagnert]

@smolinari It's not too much, but efficient ;)

[smolinari]

Simple and efficient are almost in all cases the best solutions! 😄

Scott