View source for Examples/Eclipse Business Expense Reporting Tool/User State Service

{{warning2|text=This page is under development}}
Managing the user state in a standalone application is relatively easy. EBERT runs as both a standalone application (RCP, ERCP) and as a multiple-user application (RAP). To support both environments, we have to be careful how we store user state.

EBERT defines an Equinox/OSGi Service of type [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.examples/ebert/org.eclipse.examples.expenses.views/src/org/eclipse/examples/expenses/context/IUserContextService.java?root=Technology_Project&view=markup org.eclipse.examples.expenses.context.IUserContextService.java]&mdash;defined in the <code>org.eclipse.examples.expenses.views</code> project&mdash;along with two different implementations. Implementations of this type are responsible for one thing: answer, when asked, the user state (an instance of [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.examples/ebert/org.eclipse.examples.expenses.views/src/org/eclipse/examples/expenses/context/IUserContext.java?root=Technology_Project&view=markuporg.eclipse.examples.expenses.context.IUserContext]) for the current user.

The notion of "current user" is pretty simple in the standalone case: there is only one user.