axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimuthu Gamage (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2C-863) Non-blocking code generation and forwarding a context code not supported
Date Wed, 09 Jan 2008 04:15:34 GMT

    [ https://issues.apache.org/jira/browse/AXIS2C-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557126#action_12557126
] 

Dimuthu Gamage commented on AXIS2C-863:
---------------------------------------

Hi Frank,

As you may have noticed for all the elements in the XML there is a file generated with "adb_"
prefix with a structure to store the data and set of setters and getters associated with it.


In each file there are two function for serialize and deserialize.

serialize - Writes the XML through a stream writer
deserialize - Parse the XML (XML is in the form of AXIOM) and fill the structure..


So in your case since if want to find where "urn:common.MyCompany.com" is writing you should
check 'deserialize' method most probably in a file like adb_LoginRequest.c. (But there may
be cases that the code that write these namespace  can be in another file which is called
by adb_LoginRequest.c)

Hope this will give you some idea..

Thanks
Dimuthu

> Non-blocking code generation and forwarding a context code not supported
> ------------------------------------------------------------------------
>
>                 Key: AXIS2C-863
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-863
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: wsdl2c tool
>    Affects Versions: Current (Nightly)
>            Reporter: Frank Huebbers
>         Attachments: case21.tar.gz
>
>
> I am using the non-blocking web service calls as they are generated by the wsdl2c codegen
tool. What I am missing in the codegeneration, however, is the context that I would like to
forward as well to the non-blocking call. Specifically, what I am currently getting is the
following (for the prototype in the header):
> void axis2_stub_start_op_MyService_getProperties( axis2_stub_t *stub, const axutil_env_t
*env,
>                                                      adb_getProperties_t* _getProperties,
>                                                    axis2_status_t ( AXIS2_CALL *on_complete
) (struct axis2_callback *, const axutil_env_t *) ,
>                                                    axis2_status_t ( AXIS2_CALL *on_error
) (struct axis2_callback *, const axutil_env_t *, int ) )
> What would be more useful, however, is the following in the prototype:
> void axis2_stub_start_op_MyService_getProperties( axis2_stub_t *stub, const axutil_env_t
*env,
>                                                      adb_getProperties_t* _getProperties,
>                                                      void *data,
>                                                     axis2_status_t ( AXIS2_CALL *on_complete
) (struct axis2_callback *, const axutil_env_t *) ,
>                                                     axis2_status_t ( AXIS2_CALL *on_error
) (struct axis2_callback *, const axutil_env_t *, int ) )
> With the following addition in the implementation:
> /* Set data object */
> axis2_callback_set_data(callback, data);
> This would allow users to store a context with their non-blocking call, as is customary
in other languages, without having to manually change the stub after it was generated.
> I generated the client stub with the following options on the wsdl2c tool: -uri myWSDL.wsdl
-d adb -u

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message