Yves,
Thanks for the confirmation. I will cetainly file the
necessary report with details -- however, in the
meantime:
Problem-1 (primary concern):
* What would be the recommended workaround? Anyone has
nay other way in which we can achieve this without
having to invoke the XMLSignature-generating method
from every piece of client code explicitly?
Problem-2:
* As to the problem itself, I noticed that
AxisClient.java (Client Engine) source invokes the
handlers via:
SOAPService service =
msgContext.getService();
if ( service != null ) {
h = service.getRequestHandler();
if ( h != null )
h.invoke( msgContext );
}
msgContext.getService() appears to be null which is
causing the problem. Any ideas as to who is supposed
to set it (as read from client-config.wsdd)?
TIA,
SS.
--- Yves Langisch <[EMAIL PROTECTED]> wrote:
> Can you file a bug report with a test case? We just
> have the same issue.
>
> Yves
>
> On Mon, 2005-02-21 at 21:38 -0800, SS wrote:
> > Hi,
> > We need to consume web-services from different
> sources
> > - some of which need XMLSignatures, some dont.
> >
> > We thought that the best way to handle this would
> be
> > to have service-specific handlers on client side
> which
> > introduce the signature. But Axis doesnt seem to
> > respect such configuration (although
> global-handlers
> > work!). Any thoughts on what could be wrong / how
> else
> > to achieve this?
> >
> > TIA....
> > SS
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
