Hans-Peter Maurer schrieb: Hello,
> discription: (everything is inside of an protected-pipeline of the > authentication-framework) > 1. i set session fields via setxml-statement (session transformer) > > 2. i checked it by using getxml-statement, result: previous setxml ok! > > 3. after setting session fields i used the session-context input module to > get the new values of the session-fields by parameter statement > result: i got the old values not the updated values set by setxml-statement > in the step before > > does the authentication framework the "commit" of the > "session-setxml-update" > after finishing the protected-pipeline or is this a bug of the > authentication framework or > session-context-input-module? I presume your using the session-context-input-module in your sitemap in a matcher? The matchers are evaluated before the rest of the sitemap is processed if i remember that correctly. So first your sitemap is processed (your input-module) then your setxml is executed. Of course you get the "old" Value then in the sitemap. HTH Christoph PS: If this is completely wrong, please correct me. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
