[jira] Created: (AXIS2C-319) Cannot pass an Object to the Callback function

Cannot pass an Object to the Callback function -- Key: AXIS2C-319 URL: http://issues.apache.org/jira/browse/AXIS2C-319 Project: Axis2-C Issue Type: Bug Components: core/clientapi

[jira] Commented: (AXIS2C-313) improve autoconf support

[ http://issues.apache.org/jira/browse/AXIS2C-313?page=comments#action_12439205 ] Samisa Abeysinghe commented on AXIS2C-313: -- I quite agree with some of your concerns and would like to let you know that there are major improvements bein

[jira] Assigned: (AXIS2C-316) We send action is content-type by deffault when using SOAP 1.2; this may lead to interop problems

[ http://issues.apache.org/jira/browse/AXIS2C-316?page=all ] Samisa Abeysinghe reassigned AXIS2C-316: Assignee: Samisa Abeysinghe > We send action is content-type by deffault when using SOAP 1.2; this may lead > to interop problems > ---

[jira] Assigned: (AXIS2C-317) Sending MIME headers when client did not use MIME haders

[ http://issues.apache.org/jira/browse/AXIS2C-317?page=all ] Samisa Abeysinghe reassigned AXIS2C-317: Assignee: Samisa Abeysinghe > Sending MIME headers when client did not use MIME haders > ---

[jira] Assigned: (AXIS2C-314) If there is a " in mime boundrary, the mime boundary location fails in MIME parser

[ http://issues.apache.org/jira/browse/AXIS2C-314?page=all ] Samisa Abeysinghe reassigned AXIS2C-314: Assignee: Samisa Abeysinghe > If there is a " in mime boundrary, the mime boundary location fails in MIME > parser > --

[jira] Assigned: (AXIS2C-318) xmlBufferPtr is used incorrectly in libxml2_writer_wrapper

[ http://issues.apache.org/jira/browse/AXIS2C-318?page=all ] Samisa Abeysinghe reassigned AXIS2C-318: Assignee: Samisa Abeysinghe > xmlBufferPtr is used incorrectly in libxml2_writer_wrapper > -

[jira] Assigned: (AXIS2C-315) content-id problems in MTOM

[ http://issues.apache.org/jira/browse/AXIS2C-315?page=all ] Samisa Abeysinghe reassigned AXIS2C-315: Assignee: Samisa Abeysinghe > content-id problems in MTOM > --- > > Key: AXIS2C-315 > UR

[jira] Commented: (AXIS2C-315) content-id problems in MTOM

[ http://issues.apache.org/jira/browse/AXIS2C-315?page=comments#action_12439202 ] Samisa Abeysinghe commented on AXIS2C-315: -- Oh, thanks for the tip - I looked into string.h at a glance and did not see this - did the wrong grep I guess

[jira] Commented: (AXIS2C-315) content-id problems in MTOM

[ http://issues.apache.org/jira/browse/AXIS2C-315?page=comments#action_12439192 ] Sahan Gamage commented on AXIS2C-315: - I believe both strcasecmp and strncasecmp is implemented in axis2 util. (in axis2_string.h) AXIS2_EXTERN int AXIS2_CALL

[jira] Commented: (AXIS2C-270) base64 encoding/decoding should be implemented as a stream

[ http://issues.apache.org/jira/browse/AXIS2C-270?page=comments#action_12439187 ] Samisa Abeysinghe commented on AXIS2C-270: -- +1. It would be really usefult to have base64 handling as a stream when it comes to handling non optimized bin

[jira] Created: (AXIS2C-318) xmlBufferPtr is used incorrectly in libxml2_writer_wrapper

xmlBufferPtr is used incorrectly in libxml2_writer_wrapper -- Key: AXIS2C-318 URL: http://issues.apache.org/jira/browse/AXIS2C-318 Project: Axis2-C Issue Type: Bug Components:

[jira] Created: (AXIS2C-317) Sending MIME headers when client did not use MIME haders

Sending MIME headers when client did not use MIME haders Key: AXIS2C-317 URL: http://issues.apache.org/jira/browse/AXIS2C-317 Project: Axis2-C Issue Type: Bug Components: xml

[jira] Created: (AXIS2C-316) We send action is content-type by deffault when using SOAP 1.2; this may lead to interop problems

We send action is content-type by deffault when using SOAP 1.2; this may lead to interop problems - Key: AXIS2C-316 URL: http://issues.apache.org/jira/browse/AXIS2C-31

[jira] Commented: (AXIS2C-315) content-id problems in MTOM

[ http://issues.apache.org/jira/browse/AXIS2C-315?page=comments#action_12439180 ] Samisa Abeysinghe commented on AXIS2C-315: -- We need to add, a strcasecmp wrapper to our string API (BTW strcasecmp is not ANSI) > content-id problems in

[jira] Created: (AXIS2C-315) content-id problems in MTOM

content-id problems in MTOM --- Key: AXIS2C-315 URL: http://issues.apache.org/jira/browse/AXIS2C-315 Project: Axis2-C Issue Type: Bug Components: xml/om Affects Versions: Current (Nightly) Re

[jira] Created: (AXIS2C-314) If there is a " in mime boundrary, the mime boundary location fails in MIME parser

If there is a " in mime boundrary, the mime boundary location fails in MIME parser -- Key: AXIS2C-314 URL: http://issues.apache.org/jira/browse/AXIS2C-314 Project: Axis2-

[jira] Updated: (AXIS2C-304) Compilation error of Axis2/C skeleton generated for complex datatypes by Axis2/Java WSDL2Code tool

[ http://issues.apache.org/jira/browse/AXIS2C-304?page=all ] Milinda Lakmal Pathirage updated AXIS2C-304: Attachment: codegen.patch This fixes the bug which generate compilation error [_skel_ComplexDataTypesDocLitWService.c: In function 'ax