David Sharp wrote:
> I agree it *should* be called on every invocation, however it is not.
> From running my program through the debugger, on the first service
> call I'm seeing a PrefixNamespaceMappingCallback, then a
> UsernameCallback, and then a PasswordCallback. On subsequent service
> calls, I see only the PrefixNamespaceMappingCallback.
>
> Is this is an issue with jwsdp-1.5? I'm currently in a situation
> where upgrading to 1.6 is not an option because the environment is
> shared with other web applications that have not been tested with 1.6.
Is it not possible for you to just try and switch the XWSS jars to the
ones from JWSDP 1.6. It should work because the config files and
callbackhandler are backward compatible.
regards,
kumar
>
>
> Dave
>
> On 9/27/05, *V B Kumar Jayanti* <Vbkumar.Jayanti_at_sun.com
> <mailto:Vbkumar.Jayanti_at_sun.com>> wrote:
>
> If you have configured a <xwss:UsernameToken/> policy in the
> security
> configuration then the CallbackHandler should always be called on
> every
> invocation of the method servicePing.
>
>