Return-Path: 
 <sandesha-dev-return-499-apmail-ws-sandesha-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-sandesha-dev-archive@www.apache.org
Received: (qmail 62367 invoked from network); 9 Jan 2006 10:42:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 9 Jan 2006 10:42:48 -0000
Received: (qmail 6318 invoked by uid 500); 9 Jan 2006 10:42:47 -0000
Delivered-To: apmail-ws-sandesha-dev-archive@ws.apache.org
Received: (qmail 6261 invoked by uid 500); 9 Jan 2006 10:42:46 -0000
Mailing-List: contact sandesha-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:sandesha-dev-help@ws.apache.org>
List-Unsubscribe: <mailto:sandesha-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:sandesha-dev@ws.apache.org>
List-Id: <sandesha-dev.ws.apache.org>
Delivered-To: mailing list sandesha-dev@ws.apache.org
Received: (qmail 6249 invoked by uid 99); 9 Jan 2006 10:42:46 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2006 02:42:46 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [140.117.11.4] (HELO mail.nsysu.edu.tw) (140.117.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2006 02:42:45 -0800
Received: from mail.nsysu.edu.tw (localhost.nsysu.edu.tw [127.0.0.1])
	by mail.nsysu.edu.tw (Postfix) with ESMTP id 442A75DFE0
	for <sandesha-dev@ws.apache.org>; Mon,  9 Jan 2006 18:46:05 +0800 (CST)
Received: from newyork (unknown [140.117.42.240])
	by mail.nsysu.edu.tw (Postfix) with ESMTP id D99F25DEFA
	for <sandesha-dev@ws.apache.org>; Mon,  9 Jan 2006 18:46:04 +0800 (CST)
Subject: Please help ... I'm afraid I am going to give up...
From: Ken Hu <ken@mmti.com.tw>
To: sandesha-dev@ws.apache.org
Content-Type: text/plain; charset=Big5
Date: Mon, 09 Jan 2006 18:42:21 +0800
Message-Id: <1136803341.16513.13.camel@newyork>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Dear All:

Sorry for disturbing all of you ... this is my third times in a week to
ask in this forum.
I think Sandesha could be great help for our project, but it's hard for
us to make it work.

We have made a axis ws, the deploy.wsdd is like the following:
=================================================================
<deployment xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
	<service name="TaskWS" provider="java:RPC">
		<parameter name="className" value="com.ctu.tm.ws.TaskWSIF"/>
		<parameter name="allowedMethods" value="*"/>
		<beanMapping qname="myNS:Forecast" xmlns:myNS="urn:BeanService"
languageSpecificType="java:com.ctu.tm.data.TaskBaseBean"/>
	</service>
</deployment>
=================================================================
It works fine on Jetty + axis .


Then we think we need some kind of messaging service , so we dicide to
give Sandesha a try.
Accroding to the sandesha's user guide talking about adding sandesha on
an existing ws, we modify the deploy.wsdd , so it looks like :
=================================================================
<deployment xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
	<service name="TaskWS" provider="java:RPC">
		<parameter name="className" value="com.ctu.tm.ws.TaskWSIF"/>
		<parameter name="allowedMethods" value="*"/>
		<beanMapping qname="myNS:Forecast" xmlns:myNS="urn:BeanService"
languageSpecificType="java:com.ctu.tm.data.TaskBaseBean"/>
	</service>

	<service name="RMService" provider="Handler">
         <requestFlow>
             <handler
type="java:org.apache.sandesha.ws.rm.handlers.RMServerRequestHandler"></handler>
             <handler
type="java:org.apache.axis.message.addressing.handler.AddressingHandler"></handler>
         </requestFlow>

         <parameter name="handlerClass"
value="org.apache.sandesha.ws.rm.providers.RMClientProvider"/>
         <parameter name="className"
value="org.apache.sandesha.client.RMService"/>
         <parameter name="allowedMethods" value="*"/>
         <parameter name="scope" value="request"/>
     </service>
</deployment>
=================================================================
It seems correct to me , I just copy the setting from document.

Then I modify the client code:
=================================================================
QName qn = new QName("urn:BeanService", "Forecast");
			Call call = (Call) service.createCall();
			SandeshaContext ctx = new SandeshaContext();

ctx.setAcksToURL("http://hamagawa.loc.net:8086/hg10/services/RMService"/*Constants.WSA.NS_ADDRESSING_ANONYMOUS*/);
ctx.setReplyToURL("http://hamagawa.loc.net:8086/hg10/services/RMService");
ctx.setFromURL("http://hamagawa.loc.net:8086/hg10/services/RMService");
ctx.initCall(call, WSUrl,
		"urn:wsrm:receiveTaskBean",Constants.ClientProperties.IN_OUT);
			
call.registerTypeMapping(TaskBaseBean.class, qn,
		new BeanSerializerFactory(TaskBaseBean.class, qn),
		new BeanDeserializerFactory(TaskBaseBean.class, qn));
call.setTargetEndpointAddress(new java.net.URL(WSUrl));
call.setOperationName("receiveTaskBean");
call.addParameter("taskbasebean", qn, ParameterMode.IN);
call.addParameter("domain_id", XMLType.XSD_STRING, ParameterMode.IN );
call.addParameter("comp_id", XMLType.XSD_STRING, ParameterMode.IN );
call.addParameter("user_id", XMLType.XSD_STRING, ParameterMode.IN );

call.setReturnType(XMLType.XSD_BOOLEAN);
ctx.setLastMessage(call);
reply = ((Boolean) call.invoke(new Object[] { domainID, compID, userID ,
taskBaseBeans })).booleanValue();
ctx.endSequence();
=================================================================
As you can see , I almost copy them all from the sample in the document.

Because my client code is a servlet , so I run the browser to test my
code.
(My servlet and my webservice are running on the same machine, in fact ,
they're in the same web application)

The situation is that the browser just keeping running and running and
nothing really happens until I must stop my browser's action.

There're a lot of messages occur in the log file , I notice one of them
saying:
=================================================================
Inactivity Timeout Reached, No Response from the Server
=================================================================

Can anyone one kindly help me to find out what's going wrong here ?
Really appreciate  ....

Ken

-- 
��o��             �J����             Ken Hu          ken@mmti.com.tw

�s�ج�ުѥ��������q
http://www.mmti.com.tw

�����]804���s�Ͻ�����70��
��ߤ��s�j�dzзs�|������511��

�q��      07-5253020
�ǯu      07-5252165
���      0937083880


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org