Having considered all the replies, the following changes will sort out
most of the concerns.
writer
==
new attributes to impl struct:
int type;
xmlDocPtr *docp;
Original:
AXIS2_DECLARE(axis2_xml_writer_t *)
axis2_xml_writer_create_for_memory(axis2_env_t **env,
it is appropriate to change axis2_xml_reader_create_for_buffer
function name to axis2_xml_reader_create_for_memory since we use a
memory buffer . Then we need to change the name of the existing
axis2_xml_reader_create_for_memory function name.
I think we should name it as
Hi, Nadir,
I've just taken a look at the various places the engine uses this, and
agree these parameters are now redundant. Also, as you point out, removing
these will greatly simplify the generated code, and in turn the WSDL2Ws
code.
+1 from me.
Regards,
Adrian
Forwarding with correct prefix
---BeginMessage---
it is appropriate to change axis2_xml_reader_create_for_buffer
function name to axis2_xml_reader_create_for_memory since we use a
memory buffer . Then we need to change the name of the existing
axis2_xml_reader_create_for_memory function name.
I
In line with the Java implementation, I have added the functionality to
validate the processing of must understand headers.
Now, on engine receieve, if there are headers that must be understoob
but not processed the engine would throw a fault.
Samisa...
Hi,
I'm moving axis2_url.c into utils folder, so that I can use it in Axis2
Woden C.
thanks
damitha
Samisa Abeysinghe wrote:
Forwarding with correct prefix
Damitha Kumarage wrote:
Hi,
I'm moving axis2_url.c into utils folder, so that I can use it in
Axis2 Woden C.
+1
Samisa...
thanks
damitha
