Laurent Trillaud wrote:
>
> It wasn't a so bad day because it works. :-) Thanks a lot.
You're welcome.
> But if, in the application, the pipeline associated to the load is
> started automatically at login, at logout the pipeline associated to the
> save isn't triggered.
Yes, currently. I'm +1 for adding this feature, but there is of course the
potential that the user never logs out and simply leaves the site (by
closing the browser).
> I guess that we need a loop, in [EMAIL PROTECTED],
> like this one:
> // And now save applications
> Iterator applications =
> handler.getHandlerConfiguration().getApplications().values().iterator();
> while ( applications.hasNext() ) {
> ApplicationConfiguration appHandler =
> (ApplicationConfiguration)applications.next();
> if ( !appHandler.getLoadOnDemand() ) {
> handler.getContext().saveApplicationXML( appHandler, this.resolver
> );
> }
> }
> But I don't know exactly where and if it's enough.
I think - not only to be compatible - we should make this configurable,
which means, like the loadOnDemand you can specify a "saveOnLogout"
attribute and then the application is saved on logout.
What do you think?
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
