Hi Hannes,
You' re right.
The problem is:
I'm trying to integrate sandesha and kandula on axis 1.3,
Here is a snipplet of the code that I wrote for the client :
String endpoint = new
String("http://localhost:8080/axis/services/Servizio1";);
Service service = new Service();
Call call = null;
SandeshaContext ctx = new SandeshaContext(true);
ctx.setAcksToURL("http://localhost:8080/axis/services/RMService";);
ctx.setReplyToURL("http://localhost:8080/axis/services/RMService";);
ctx.setSourceURL("http://localhost:8080/axis/services/RMService";);
try {
call = (Call) service.createCall();
} catch(javax.xml.rpc.ServiceException e) {
System.out.println("problemi create call");
}
ctx.initCall(call, endpoint, "urn:wsrm:somma",
Constants.ClientProperties.IN_OUT);
call.setOperationName("somma");
call.setSOAPActionURI("http://localhost:8080/axis/services/kandulaServizio1#somma";);
<==
call.addParameter( "op1", XMLType.XSD_INT, ParameterMode.IN);
call.addParameter( "op2", XMLType.XSD_INT, ParameterMode.IN);
call.setReturnType( XMLType.XSD_INT );
try {
ctx.setLastMessage(call);
ris = (Integer) call.invoke( new Object [] {op1,op2});
System.out.println("ris = " + ris.intValue());
RMReport report = ctx.endSequence();
System.out.println("Is all messages acked - " +
report.isAllAcked());
}
........................
As you can see I called the metod setSoapActionURI.
Then I changed sandesha released as suggested by sandesha developer Jaliya.
and the eroor is changed from
org.apache.axis.types.URI$MalformedURIException: Cannot initialize URI with
empty parameters in the follow:
[CallbackRegistry] registerCallback: timeout= 180000
[ATCoordinatorImpl] timeout ACTIVE
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.ATCoordinatorImpl.timeout(ATCoordinatorImpl.java:626)
at
org.apache.kandula.coordinator.CallbackRegistry$1.run(CallbackRegistry.java:62)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
catch CoordinatoreInvoke-> Inactivity Timeout Reached, No Response from the
Server
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: Inactivity Timeout Reached, No Response from the Server
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:Inactivity Timeout Reached, No
Response from the Server
at org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
.....
Thanks Valerio.
----- Original Message -----
From: "Hannes Erven" <[EMAIL PROTECTED]>
To: "Valerio Vianello" <[EMAIL PROTECTED]>
Cc: "Dasarath Weeratunge" <[EMAIL PROTECTED]>; <[email protected]>
Sent: Saturday, July 15, 2006 6:12 PM
Subject: Re: kandula and sandesha
Hi Valerio,
My problem is that I don't use WSDL2Java but I writing my java file by
hand, for this reason I modified the field soapAction in the wsdd file.
It is very difficult for us to help if you don't tell us details on what
you actually do and use.
Do you use axis for your client side? Do you write each byte of the SOAP
message "by hand" to the wire? Something in between? :-)
If you use axis call objects, you need to set the call's SOAPAction
property like this:
_call.setSOAPActionURI("http://big.tuwien.ac.at/xxx/#getCoordinationContextWithMatchcode";);
(This is taken from an WSDL2Java generated stub.)
Can you please send me a wsdl file that I could take as example for my
wsdl file?
I posted an example with the relavant sections a few days ago.
Of course, if you don't use the WSDL to generate the web service client,
it won't change anything if you add the soap actions there. ;-)
-hannes
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
