Hi Dasarath,
Let's try to fix this without changing much. I need to know a way to inform
call object not to use the client-config.wsdd.
Thanks,
Jaliya
----- Original Message -----
From: "Dasarath Weeratunge" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, July 14, 2006 12:57 AM
Subject: Re: kandula and sandesha
Quoting Benjamin Schmeling <[EMAIL PROTECTED]>:
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
at
org.apache.sandesha.server.RMMessageProcessorIdentifier.getMessageProcessor(RMMessageProcessorIdentifier.java:53)
at
Please post this to sandesha-dev and get their feedback. This is a
different
problem. The earlier issue was WS-AddressingHandler used the URI class to
internally store the SOAP action which did not accept NULL strings-- so
you
got a MalformedURIException. Kandula does not make any use of SOAP action.
Still it needs WS-Addressing since it uses reference properties. If we
really
cannot use Sandesha with Kandula in the present arrangement we should be
able
scrap the use of WS-Addressing inside Kandula without lot of trouble.
thanks,
--dasarath
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
