Return-Path: 
 <axis-c-user-return-4154-apmail-ws-axis-c-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org
Received: (qmail 11851 invoked from network); 30 Jul 2007 05:33:30 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 30 Jul 2007 05:33:30 -0000
Received: (qmail 8540 invoked by uid 500); 30 Jul 2007 05:33:30 -0000
Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org
Received: (qmail 8249 invoked by uid 500); 30 Jul 2007 05:33:29 -0000
Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:axis-c-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-c-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-c-user@ws.apache.org>
List-Id: "Apache AXIS C User List" <axis-c-user.ws.apache.org>
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Delivered-To: mailing list axis-c-user@ws.apache.org
Received: (qmail 8233 invoked by uid 99); 30 Jul 2007 05:33:29 -0000
Received: from Unknown (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jul 2007 22:33:29 -0700
X-ASF-Spam-Status: No, hits=1.5 required=10.0
	tests=SPF_PASS,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [65.116.131.35] (HELO postal.aylus.com) (65.116.131.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2007 05:33:22 +0000
Received: from postal.aylus.com (localhost.localdomain [127.0.0.1])
	by postal.aylus.com (8.13.1/8.13.1) with ESMTP id l6U5cZSI022735
	for <axis-c-user@ws.apache.org>; Mon, 30 Jul 2007 01:38:35 -0400
Date: Mon, 30 Jul 2007 11:19:29 +0530
From: "Manoj Rao" <rmanoj@aylus.com>
To: axis-c-user@ws.apache.org
Message-ID: 
 <LF4BEE52C3CF246a292FF279A466927C8.1185774106.dakghar.aylus.com@MHS>
Subject: Re: Services.xml
x-scalix-Hops: 2
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Virus-Checked: Checked by ClamAV on apache.org

Hi Samisa,
The situation here is that the server receives the request from client=20
processes it and calls the correct functions and when the server=20
responds to=20
the client with a complextype xml, this XML doesn't reach the client. In=20
fact=20
the XML we have formed is syntactically correct but the client doesn't=20
receive xml. After calling this API=20
axiom_xml_writer_get_xml() the buffer obtained shows the correct=20
response xml=20
formed by the server.=20
the sample response xml is
<ns1:Result xmlns:ns1=3D"http://axis2c/services/<My Service=20
Name>/namespace1">
    <ns1:myReadResponse>
        <ErrorCode>0</ErrorCode>
        <ErrorMessage>SUCCESS</ErrorMessage>
        <myResponse>
            <param1>Default</param1>
            <param2>15</param2>
            <param3>home.net</param3>
            <param4>office.net</param4>
            <param5>1</param5>
            <param6>1024</param6>
            <param7>1024</param7>
            <param8>15</param8>
            <param9>-1</param9>
            <param10>-1</param10>
            <param11>1</param11>
        </myResponse>
        <myResponse>
            <param1>om</param1>
            <param2>5</param2>
            <param3>google.com:0</param3>
            <param4>yahoo.com:0</param4>
            <param5>2</param5>
            <param6>2400</param6>
            <param7>2400</param7>
            <param8>15</param8>
            <param9>3</param9>         =20
            <param10>-1</param10>
            <param11>1</param11>
        </myResponse>
        <myResponse>
            <param1>omnew123344</param1>
            <param2>5</param2>
            <param3>domain1.com:0</param3>
            <param4>domain2.com:0</param4>
            <param5>2</param5>
            <param6>2400</param6>
            <param7>2400</param7>
            <param8>15</param8>
            <param9>511</param9>
            <param10>255</param10>
            <param11>1</param11>
        </myResponse>
    </ns1:myReadResponse>
</ns1:Result>

The client doesn't receive any XML at all in this case. The rest of the=20
framework, if you can call it, for writing clients has been done and is=20
being used for some time now.

Thanks,
Manoj R


On Saturday 28 Jul 2007 11:34 am, Samisa Abeysinghe wrote:
> Raghavendra SM wrote:
> > Oh Sorry, "acc_invoke" was a typo error, and it actually is=20
"my_invoke".
> > Even then I face the same problem. Please take another look & let us
> > know if you need more information of any sort.
>
> Well, I fixed this typo, removed the func_array add statements form=20
init
> method and also fixed a typo on line 105 where the trailing double=20
quote
> of the string was missing and replaced echo with this service and
> everything worked fine. Of course, I also commented out your custom
> logging statements.
>
> How did you compile the service lib? What is the exact compiler=20
options
> used? I used the makefile form echo service. If you used command line=20
to
> compile, make sure you used "-lpthread -ldl" options when linking.
>
> Thanks,
> Samisa...
>
> > Regards,
> > ~raghav
> >
> >
> > -----Original Message-----
> > From: Samisa Abeysinghe [mailto:samisa@wso2.com]
> > Sent: Friday, July 27, 2007 6:53 AM
> > To: Apache AXIS C User List
> > Subject: Re: Services.xml
> >
> > Raghavendra SM wrote:
> >> Hi Samisa,
> >>
> >> Please find the server code below, which is causing the problems as
> >> described by Manoj Rao. Please let me know if need more information
> >
> > than
> >
> >> this.
> >>
> >> These are the skeleton functions of the server.
> >
> > I think I found the problem. In your my_svc_skeleton_ops_var=20
variable,
> > you have provided my_invoke as the invoke function. However, in your
> > source, there is no such function, rather a function named=20
acc_invoke. I
> >
> > think you have to rename acc_invoke to my_invoke and try.
> >
> > Also in the my_init function, you do not need to initialize
> > svc_skeleton->func_array. You can safely comment whole of my_init
> > function, leaving only the return AXIS2_SUCCESS; line in there.
> >
> > HTH.
> >
> > Thanks,
> > Samisa...




---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org