Re: Axis2C generated code Documentation

Tue, 08 Jan 2008 17:45:14 -0800

WSDL2C tutorial is something that we are missing. We used to have a calculator sample. However, we have not been able to keep phase with the improvements we have been doing to WSDL2C when it comes to samples and tutorials. The fact of the matter is, we initially expected for users to use the OM model more, but it has proven over the past year or so that users are more interested in using the WSDL tool.
Dimuthu has been doing a great job, maintaining the WSDL tool, I have been doing some fixes some time back but haven't had time to keep up. Looks like we need some more devs to support Dimuthu in this front. 

Samisa...

Dimuthu Gamage wrote:

Hi Virgil,

Actually I dont think there are some other documentation are there for
the tool except the samples. In fact I'm working on some which to be
published on at least in two weeks hopefully.

For now, I 've uploaded my test cases to this url[1].  Hope you can
get some idea, how different cases (specially in XML-schema) are
handled.

[1] http://people.apache.org/~dimuthu/leisure/9_jan_08/wsdl2ctests.zip

Thanks
Dimuthu

On Jan 9, 2008 1:40 AM, Trasca Virgil <[EMAIL PROTECTED]> wrote:

  

Hi,

   Is there some kind of documentation/tutorial on how to use the code 
generated by wsdl2c? I am trying for couple of days to use such code without 
much luck. Axis2C samples are simple and are not with code generated by wsdl2C. 
Using such a sample I was able to call a very simple service but when I come to 
more realistic services generated with wsld2c I was not able to handle.

Thank you,
Virgil

----- Original Message ----
From: Trasca Virgil <[EMAIL PROTECTED]>
To: Apache AXIS C User List <[email protected]>
Sent: Tuesday, January 8, 2008 9:05:12 PM
Subject: Re: Axis2C generated client issue (please see atached code for details)


Hi Dimuthu,

      I tried what you said but without success. Result is NULL again.
 But I tried also something else. Please check the attached pictures.
 First picture is the list of services exposed, second is a very simple
 service which I am able to call it also from C client , and third one
 should returns some values from an XML config files but is returning NULL
 from c. Please see my atached picture.

Thank you,
Virgil



----- Original Message ----
From: Trasca Virgil <[EMAIL PROTECTED]>
To: Apache AXIS C User List <[email protected]>
Sent: Tuesday, January 8, 2008 9:20:36 AM
Subject: Re: Axis2C generated client issue (please see atached code for
 details)


Hi,

    I will try that. BTW this is how I generated my c client code

<target name="generate.service.c.client"
 depends="generate.service.wsdl">
        <java classname="org.apache.axis2.wsdl.WSDL2C" fork="true">
                    <arg value="-uri"/>
                    <arg
 file="${resources.dir}/wsdl/BursterPublic.wsdl"/>
                    <arg value="-d"/>
                    <arg value="adb"/>
                    <arg value="-u"/>
                    <arg value="-o"/>
                    <arg value="${src.generated.dir}/axis2/c"/>
                    <classpath refid="axis2.classpath"/>
                </java>

    </target>

Thank you,
Virgil

----- Original Message ----
From: Dimuthu Gamage <[EMAIL PROTECTED]>
To: Apache AXIS C User List <[email protected]>
Sent: Tuesday, January 8, 2008 8:45:46 AM
Subject: Re: Axis2C generated client issue (please see atached code for
 details)


Actually Payload can be null, in a case of an empty request (If the
WSDL says your request message is empty). There have been places where
users meet simmilar situations[1]. There the user could solved his
problem using the changed endpoint. That should be the solution for
this case as well.


[1]


 
http://www.nabble.com/codegeneration-and-service-with-no-parameters-td14338901.html#a14374273

Thanks
Dimuthu

On Jan 8, 2008 11:57 AM, Trasca Virgil <[EMAIL PROTECTED]> wrote:

    

Hi,

       Thank you for helping.
       I attached also the wsdl file. Regarding compiling you can

      

 easily remove 1 wxWidgets stuff and it will compile. What I observed
 debugging and is strange is that generated line code

    

ret_node =  axis2_svc_client_send_receive_with_op_qname(
 svc_client, env, op_qname, payload);

comes to execute with payload = NULL and I think this is incorrect.

      

 But this is generated code so because of that I don't know what to do.

    

I am calling my webservice which is up from Settings.cpp.

Thank you,
Virgil


----- Original Message ----
From: Dimuthu Gamage <[EMAIL PROTECTED]>
To: Apache AXIS C User List <[email protected]>
Sent: Tuesday, January 8, 2008 3:52:40 AM
Subject: Re: Axis2C generated client issue (please see atached code

      

 for details)

    

On Jan 8, 2008 7:18 AM, Dimuthu Gamage <[EMAIL PROTECTED]> wrote:

      

Yea, It s better we have the WSDL file to figure out what has
happened.  I cant compile the code since I dont have installed
wxWidget. :(

I assume this is a problem of dispatching the request with empty

        

 body.

      

( I noticed that your soap action is not the way Axis2 expected to
dispatch).


So can you try out setting the endpoint uri to.



        

 "http://your_actual_endpoint/axis2/services/BursterPublic/getStting";

    

Correction: this should be
"http://your_actual_endpoint/axis2/services/BursterPublic/getSetting";

      

(notice the end it is the operation name)


Thanks
Dimuthu



On Jan 8, 2008 4:01 AM, Mark Nüßler <[EMAIL PROTECTED]>

        

 wrote:

      

Hello Trasca,

[sry last mail i said Virgil not Trasca]

can you please send the wsdl-file and the command
you use to generate you code ?

i think you have to you tcpmon, otherwise
you wouldn't see what was transmitted - if
something was really transmitted.

mfg derMark


Trasca Virgil schrieb:


          

Hi,

    I am a newbie to Axis2C client and I have an issue. My

            

 server

    

 is Axis2 Java 1.3 and is up with a service getSettings() which is
 correct (I am 100% about that).

      

The client is C and is generated with wsdl2c codegent. The

            

 issue

    

 is than when I call getSettings from C I got NULL all the time even

      

 is

    

 the service is working.

      

I tried to use tcpmon but with not success.

in Settings.cpp
I have function getSettings() which is returning all the time

            

 NULL even if I consider that I did all the pre-requites correctly.

      

 This

    

 function should not return NULL but a corect value.

      

adb_getSettingsResponse_t* Settings::getSettings()
{
   return axis2_stub_BursterPublic_getSettings(stub,env);
}


What I observed by debugging and is strange is that in

            

 generated

    

 code

      

axis2_stub_BursterPublic_getSettings

there is a call to

ret_node =  axis2_svc_client_send_receive_with_op_qname(

            

 svc_client, env, op_qname, payload); and here payload comes all the

      

 time NULL

    

 as it is initialized

      

earlier in the function with NULL and is not changed before

            

 calling axis2_svc_client_send_receive_with_op_qname.

      

I thing payload should not be null at this point . Please

            

 assist

    

 me.

      

Thank you,
Virgil.





            

  ------------------------------------------------------------------------

    

            

  ---------------------------------------------------------------------

    

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




            

  ------------------------------------------------------------------------

    

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.13/1213 - Release

            

 Date:

    

 07.01.2008 09:14

      

          

  ---------------------------------------------------------------------

    

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]




---------------------------------------------------------------------
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]





---------------------------------------------------------------------
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]



---------------------------------------------------------------------
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]




  



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]























					Reply via email to