RE: Question regarding removal of a node from its parent

in a debug version and see what is happening. Good luck, Bill Mitchell wtmitche...@acm.org -Original Message- From: Manjula Peiris [mailto:manj...@wso2.com] Sent: Thursday, December 18, 2008 9:16 AM To: Apache AXIS C Developers List Subject: Re: Question regarding removal of a node from its

RE: Multi-threading

to synchronous calls. Best regards, Bill Mitchell wtmitche...@acm.org -Original Message- From: Patrick van Beem [mailto:patrick.van.b...@quintiq.com] Sent: Tuesday, December 16, 2008 6:20 AM To: Apache AXIS C Developers List Subject: Re: RE : Multi-threading Hello Carl, What Axis

RE: Multi-threading

application, so I don't know if you might need a separate thread-pool for each created environment. Good luck, Bill Mitchell -Original Message- From: Lefrancois, Carl [mailto:carl.lefranc...@axa-canada.com] Sent: Thursday, December 11, 2008 9:56 AM To: Apache AXIS C Developers List

RE: Possible improvements to Axis2/C

of routines like axiom_element_force_ownership for each axiom structure? Axiom_node_detach could invoke these force_ownership routines on each element of the subtree to make sure that every unowned string is replaced. Regards, Bill Mitchell From: Supun Kamburugamuva [mailto:[EMAIL

RE: Multi threading in Axis2/C

Hello Rinil, I see two aspects to the multi-threading question, whether Axis2C runs in a multi-threaded environment, and whether Axis2C itself takes advantage of a multi-threading. My experience has been on the client side; it seems your question may be on the server side, with which I am much

RE: Novice questions regarding Axis2C client development.

, and find the Axis2C repo directory on the client, accessing the services after the first becomes fairly straightforward. Good luck, Bill Mitchell From: Mike Zhao [mailto:[EMAIL PROTECTED] Sent: Friday, May 02, 2008 4:44 PM To: Apache AXIS C Developers List Subject: RE: Novice questions

RE: Axiom

and one thread will process one child, then the other thread might process the next child. This is usually not what you want to do in a multi-threaded environment. Bill Mitchell -Original Message- From: Dinesh Premalal [mailto:[EMAIL PROTECTED] On Behalf Of Dinesh Premalal Sent

[jira] Commented: (AXIS2C-1046) mod_axis2.dll load fails on Win XP SP2 (Japanese edition)

[ https://issues.apache.org/jira/browse/AXIS2C-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576235#action_12576235 ] Bill Mitchell commented on AXIS2C-1046: --- Hi Senaka, I would hate for someone

[jira] Commented: (AXIS2C-1046) mod_axis2.dll load fails on Win XP SP2 (Japanese edition)

[ https://issues.apache.org/jira/browse/AXIS2C-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576288#action_12576288 ] Bill Mitchell commented on AXIS2C-1046: --- Exactly. A global fix will require

[jira] Commented: (AXIS2C-1040) Use of AXIS2_EXPORT instead of AXIS2_EXTERN in a few places causes errors in static build

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574719#action_12574719 ] Bill Mitchell commented on AXIS2C-1040: --- Agreed, Senaka, I'm easy. You're probably

RE: [Vote][Axis2]Axis2/C 1.3.0 Release Artifacts

In addition to the release Windows binary (libxml2), I built the Windows source using libcurl and guththila, and it worked fine. Here is my +1. Thanks, Bill Mitchell Dinesh Premalal wrote: Hi Devs, I have packaged and uploaded the Apache Axis2/C 1.3.0 release artifacts at [1]. The key

[jira] Commented: (AXIS2C-1040) Use of AXIS2_EXPORT instead of AXIS2_EXTERN in a few places causes errors in static build

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574045#action_12574045 ] Bill Mitchell commented on AXIS2C-1040: --- Looking at the exports from the Windows

[jira] Commented: (AXIS2C-1015) In axutil_uri, a reference is returned, where a duplicated string should be.

[ https://issues.apache.org/jira/browse/AXIS2C-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573357#action_12573357 ] Bill Mitchell commented on AXIS2C-1015: --- Although I've not researched exactly how

RE: [jira] Commented: (AXIS2C-675) Detach node does not handle namespaces

, to make the merge process later easier? Thanks, Bill Mitchell -Original Message- From: Dinesh Premalal (JIRA) [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 3:34 AM To: [EMAIL PROTECTED] Subject: [jira] Commented: (AXIS2C-675) Detach node does not handle namespaces [ https

[jira] Resolved: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-675. -- Resolution: Fixed Fix Version/s: 1.3.0 Detach node does not handle namespaces

RE: [Vote][Axis2]Axis2/C 1.3.0 Release Artifacts

, guththila actually received more use and testing than did the libxml interface. Bill Mitchell From: Dinesh Premalal [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 27, 2008 9:47 AM To: Apache AXIS C Developers List Subject: [Vote][Axis2]Axis2/C 1.3.0 Release Artifacts Hi Devs, I

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: diff.txt While working on the routine to copy a node tree, I found it needed

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: (was: diff.txt) Detach node does not handle namespaces

RE: Issue in using 'detach' for cloning

Sanjaya, you raise a question that I was going to ask Dinesh. In my mind, I see Jira 675 as a bug. For some xml document trees, detach generates a structure that is later unusable by the adb stubs that depend on it. As such, it could still be a candidate for inclusion in 1.3. And I see our

RE: Issue in using 'detach' for cloning

with the implementation of axiom_node_free_tree. Does this mean that all existing axiom_node_detach followed by axiom_node_free_tree have to change? Or is it an auxiliary fix? Regards, Senaka Bill Mitchell wrote: Sanjaya, you raise a question that I was going to ask Dinesh. In my mind, I see Jira 675 as a bug

RE: Issue in using 'detach' for cloning

Samisa, it looks to me as if the branch Sanjaya created so far has only my changes to AXIS2C-675. I think I misread this email the first time to say that you had already written the changes to implement a clone method. Were you intending that the source for axiom_node_clone that

RE: Issue in using 'detach' for cloning

? Or is it an auxiliary fix? Regards, Senaka Bill Mitchell wrote: Sanjaya, you raise a question that I was going to ask Dinesh. In my mind, I see Jira 675 as a bug. For some xml document trees, detach generates a structure that is later unusable by the adb stubs that depend on it. As such, it could still

[jira] Assigned: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell reassigned AXIS2C-675: Assignee: Bill Mitchell Detach node does not handle namespaces

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: (was: diff.txt) Detach node does not handle namespaces

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: diff.txt I've updated the attached diff to include two additional changes. (1

[jira] Issue Comment Edited: (AXIS2C-675) Detach node does not handle namespaces

-- Key: AXIS2C-675 URL: https://issues.apache.org/jira/browse/AXIS2C-675 Project: Axis2-C Issue Type: Bug Components: xml/om Reporter: Jamie Lyon Assignee: Bill Mitchell Attachments: diff.txt When

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: diff.txt Detach node does not handle namespaces

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: (was: diff.txt) Detach node does not handle namespaces

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: diff.txt Detach node does not handle namespaces

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: (was: diff.txt) Detach node does not handle namespaces

[jira] Updated: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-675: - Attachment: diff.txt The attached diff.txt implements a change to attach all the namespaces

[jira] Created: (AXIS2C-987) Generated adb stubs do not support attributes with namespaces

Components: code generation Affects Versions: 1.2.0 Environment: Windows XP, Visual Studio 2005, guththila, libcurl Reporter: Bill Mitchell For the attributes defined in the wsdl, the generated stub classes require that the namespace prefix be omitted from the attribute

[jira] Reopened: (AXIS2C-675) Detach node does not handle namespaces

[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell reopened AXIS2C-675: -- This problem has been encountered again recently, and it appears to me there is a real issue

[jira] Commented: (AXIS2C-791) On in-out message flow that fails with no response, no error code or misleading error code is returned, expected error number 3.

[ https://issues.apache.org/jira/browse/AXIS2C-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568414#action_12568414 ] Bill Mitchell commented on AXIS2C-791: -- Senaka, following your suggestion, I restored

[jira] Commented: (AXIS2C-963) Guththila neglects spacing and formatting between nodes whereas libxml2 preserves it.

[ https://issues.apache.org/jira/browse/AXIS2C-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568079#action_12568079 ] Bill Mitchell commented on AXIS2C-963: -- Senaka, it's a good question whether a better

[jira] Resolved: (AXIS2C-963) Guththila neglects spacing and formatting between nodes whereas libxml2 preserves it.

[ https://issues.apache.org/jira/browse/AXIS2C-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-963. -- Resolution: Fixed I modified om_stax_builder.c in rev 620703 to tolerate no text node being

[jira] Commented: (AXIS2C-959) Guththila parser can't handle comments.

[ https://issues.apache.org/jira/browse/AXIS2C-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567615#action_12567615 ] Bill Mitchell commented on AXIS2C-959: -- Senaka, I thought your changes looked right

[jira] Reopened: (AXIS2C-963) Guththila neglects spacing and formatting between nodes whereas libxml2 preserves it.

[ https://issues.apache.org/jira/browse/AXIS2C-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell reopened AXIS2C-963: -- This change has broken incoming SOAP messages that begin with an xml declaration. What

[jira] Commented: (AXIS2C-966) Guththila has no support for XML declarations

[ https://issues.apache.org/jira/browse/AXIS2C-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567627#action_12567627 ] Bill Mitchell commented on AXIS2C-966: -- Senaka, here's another question, while we

[jira] Commented: (AXIS2C-966) Guththila has no support for XML declarations

[ https://issues.apache.org/jira/browse/AXIS2C-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567620#action_12567620 ] Bill Mitchell commented on AXIS2C-966: -- Actually, Senaka, I think that guththila could

[jira] Commented: (AXIS2C-966) Guththila has no support for XML declarations

[ https://issues.apache.org/jira/browse/AXIS2C-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567513#action_12567513 ] Bill Mitchell commented on AXIS2C-966: -- Senaka, you fixed all the issues I observed

[jira] Updated: (AXIS2C-936) On incomplete response message, the client receives response data for the elements up to the error, but no indication of the error

[ https://issues.apache.org/jira/browse/AXIS2C-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-936: - Attachment: TemplateSource.diff Looking at the TemplateSource.xsl file, I think my suggested

[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

[ https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567024#action_12567024 ] Bill Mitchell commented on AXIS2C-884: -- You're very welcome. By the way

[jira] Commented: (AXIS2C-573) Fix warnings on windows

[ https://issues.apache.org/jira/browse/AXIS2C-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567252#action_12567252 ] Bill Mitchell commented on AXIS2C-573: -- I glad to see you are picking these up, Senaka

RE: [jira] Commented: (AXIS2C-967) libcurl interface assumes first response line is HTTP status, but it might be HTTP 100 Continue

Components: transport/http Environment: Windows XP, Visutal Studio 2005, libxml, libcurl Reporter: Bill Mitchell After receiving an HTTP response, the axis2_libcurl code assumes the first response line is the HTTP status line, and grabs the status code therein. While

RE: [jira] Commented: (AXIS2C-967) libcurl interface assumes first response line is HTTP status, but it might be HTTP 100 Continue

: Bill Mitchell After receiving an HTTP response, the axis2_libcurl code assumes the first response line is the HTTP status line, and grabs the status code therein. While watching this communicate to an IIS server, I noticed that the first response was an HTTP 1.1/100 Continue, and the real

[jira] Updated: (AXIS2C-791) On in-out message flow that fails with no response, no error code or misleading error code is returned, expected error number 3.

[ https://issues.apache.org/jira/browse/AXIS2C-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-791: - Attachment: diff.txt Senaka, I worried some about the changes to axis2_op_client_add_msg_ctx

RE: Cloning a portion of a XML tree using axiom

are going to a C environment, you will need to replace all the error handling and the C++ style comments; if you are in a C++ environment, replacing the exceptions with something from your environment will be straightforward. Bill Mitchell [EMAIL PROTECTED] From: Kasun Indrasiri [mailto

[jira] Commented: (AXIS2C-791) On in-out message flow that fails with no response, no error code or misleading error code is returned, expected error number 3.

[ https://issues.apache.org/jira/browse/AXIS2C-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565776#action_12565776 ] Bill Mitchell commented on AXIS2C-791: -- Okay, Senaka, you may indeed have run across

[jira] Resolved: (AXIS2C-791) On in-out message flow that fails with no response, no error code or misleading error code is returned, expected error number 3.

[ https://issues.apache.org/jira/browse/AXIS2C-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-791. -- Resolution: Fixed Fix Version/s: 1.3.0 Fix incorporated in svn rev 618845. To get

RE: Applying Patch Fixes to Guththila in 1.3.0

of the new release, I take it that this is a bug in guththila that needs to be written up? This might prevent the adoption of guththila as the default parser if it omits support needed for a feature in the new release. Bill Mitchell [EMAIL PROTECTED] From: Dinesh Premalal [mailto:[EMAIL

[jira] Created: (AXIS2C-967) libcurl interface assumes first response line is HTTP status, but it might be HTTP 100 Continue

Project: Axis2-C Issue Type: Bug Components: transport/http Environment: Windows XP, Visutal Studio 2005, libxml, libcurl Reporter: Bill Mitchell After receiving an HTTP response, the axis2_libcurl code assumes the first response line

[jira] Commented: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565466#action_12565466 ] Bill Mitchell commented on AXIS2C-933: -- Fix included in svn rev 618364. guththila

[jira] Resolved: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[ https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-859. -- Resolution: Fixed Assignee: Bill Mitchell I checked in Lahiru and my fixes

[jira] Resolved: (AXIS2C-812) guththila parser fails attempting to deallocate unallocated cell if xml message contains more than one namespace

[ https://issues.apache.org/jira/browse/AXIS2C-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-812. -- Resolution: Fixed Fix Version/s: 1.3.0 guththila parser fails attempting to deallocate

[jira] Updated: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-933: - Attachment: guththila_xml_parser.diff For reference, in the attached guththila_xml_parser.diff

[jira] Updated: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-933: - Attachment: (was: diff2.txt) guththila parser does not handle incomplete messages well

[jira] Resolved: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-933. -- Resolution: Fixed Assignee: Bill Mitchell guththila parser does not handle incomplete

[jira] Resolved: (AXIS2C-944) guththila parser ignores XML scope rules on namespace declarations with the same prefix

[ https://issues.apache.org/jira/browse/AXIS2C-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-944. -- Resolution: Fixed Assignee: Bill Mitchell This fix has been applied as svn rev 618521

[jira] Updated: (AXIS2C-944) guththila parser ignores XML scope rules on namespace declarations with the same prefix

[ https://issues.apache.org/jira/browse/AXIS2C-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-944: - Attachment: diff.txt The attached diff contains changes to conform to the XML namespace scope

[jira] Updated: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[ https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-859: - Attachment: guththila_xml_writer.diff diff_2.txt Lahiru, looking at the code

[jira] Updated: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[ https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-859: - Attachment: (was: diff_2.txt) guththila parser fails to handle escape sequences

[jira] Updated: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[ https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-859: - Attachment: diff_2.txt guththila parser fails to handle escape sequences for ampersand, less

[jira] Resolved: (AXIS2C-818) If the returned message read fills the buffer, http_transport_utils.c clobbers the byte past the end of the buffer

[ https://issues.apache.org/jira/browse/AXIS2C-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-818. -- Resolution: Fixed Fix Version/s: Current (Nightly) This fix has been applied as svn

[jira] Resolved: (AXIS2C-834) guththila_xml_writer has problems with default namespace

[ https://issues.apache.org/jira/browse/AXIS2C-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-834. -- Resolution: Fixed Fix Version/s: Current (Nightly) This fix has been incorporated

[jira] Resolved: (AXIS2C-830) libcurl interface not multithreaded

[ https://issues.apache.org/jira/browse/AXIS2C-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell resolved AXIS2C-830. -- Resolution: Fixed Fix Version/s: Current (Nightly) This fix to this problem has been

[jira] Commented: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

[ https://issues.apache.org/jira/browse/AXIS2C-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12564962#action_12564962 ] Bill Mitchell commented on AXIS2C-857: -- I noticed that along the way a change

[jira] Commented: (AXIS2C-944) guththila parser ignores XML scope rules on namespace declarations with the same prefix

[ https://issues.apache.org/jira/browse/AXIS2C-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1256#action_1256 ] Bill Mitchell commented on AXIS2C-944: -- Looking at the code in more detail, I see

RE: [jira] Commented: (AXIS2C-861) Enable client session management through http cookies in libcurl

on the first file I checked, I couldn't see that the eol-style property was set. So, what is the convention here? Do we not worry about this? Or should we run dos2unix to clean up files before checking them in from Windows? Thanks, Bill Mitchell -Original Message- From: Dinesh Premalal

[jira] Commented: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[ https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12564199#action_12564199 ] Bill Mitchell commented on AXIS2C-859: -- Lahira, after yesterday I researched again

[jira] Reopened: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

[ https://issues.apache.org/jira/browse/AXIS2C-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell reopened AXIS2C-857: -- Probably thanks to Lahira and I cooperating to work on the patch, we ended up with a version

[jira] Created: (AXIS2C-944) guththila parser ignores XML scope rules on namespace declarations with the same prefix

Project: Axis2-C Issue Type: Bug Components: guththila Affects Versions: Current (Nightly) Environment: Windows XP, Visual Studio 2005, guththila, libcurl Reporter: Bill Mitchell The guththila parser looks for a match on the namespace prefix/URI from

[jira] Commented: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[ https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563745#action_12563745 ] Bill Mitchell commented on AXIS2C-859: -- Thanks for picking up this issue, Lahiru. I

[jira] Created: (AXIS2C-936) On incomplete response message, the client receives response data for the elements up to the error, but no indication of the error

Reporter: Bill Mitchell If the SOAP response message to the client is incomplete, i.e., there is an EOF indication in the middle of the message, the client receives an object containing the elements that could be deserialized from the message, with no indication that the message is incomplete

[jira] Commented: (AXIS2C-936) On incomplete response message, the client receives response data for the elements up to the error, but no indication of the error

[ https://issues.apache.org/jira/browse/AXIS2C-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563044#action_12563044 ] Bill Mitchell commented on AXIS2C-936: -- Looking at this again in the log, it would

[jira] Updated: (AXIS2C-933) guththila parser fails when incoming message longer than 16984 characters

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-933: - Attachment: diff2.txt I agree, Supun, that I misunderstood the buffs variable as accumulating

[jira] Updated: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-933: - Summary: guththila parser does not handle incomplete messages well, leading to an infinite loop

[jira] Created: (AXIS2C-933) guththila parser fails when incoming message longer than 16984 characters

Type: Bug Components: guththila Affects Versions: Current (Nightly) Environment: Windows XP, Visual Studio 2005, guththila, libcurl Reporter: Bill Mitchell The code in the guththila parser has a couple of problems when the first allocated buffer fills up

[jira] Updated: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

[ https://issues.apache.org/jira/browse/AXIS2C-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-857: - Attachment: diff2.txt Lahira, it's a nice start on a patch; it's certainly in the right

[jira] Created: (AXIS2C-927) axiom_element_declare_default_namespace fails when no namespace already declared

Issue Type: Bug Environment: Windows XP, Visual Studio 2005, guththila, libcurl Reporter: Bill Mitchell If axiom_element_declare_default_namespace() is called before any named namespace is declared, it fails to perform the axutil_hash_make and as a result

[jira] Updated: (AXIS2C-927) axiom_element_declare_default_namespace fails when no namespace already declared

[ https://issues.apache.org/jira/browse/AXIS2C-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-927: - Attachment: om_element_diff axiom_element_declare_default_namespace fails when no namespace

[jira] Commented: (AXIS2C-834) guththila_xml_writer has problems with default namespace

[ https://issues.apache.org/jira/browse/AXIS2C-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561179#action_12561179 ] Bill Mitchell commented on AXIS2C-834: -- Lahiru, AXIS2C-891 identified a guththila

[jira] Created: (AXIS2C-925) seg fault in axiom_soap_fault_get_text if SOAP 1.1

Affects Versions: Current (Nightly) Environment: Windows XP, Visual Studio 2005, libxml2, libcurl Reporter: Bill Mitchell If a SOAP 1.1 server returns a SOAP fault, a seg fault can happen if the client calls axiom_soap_fault_get_text. At the time of the crash, using

[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

[ https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12558762#action_12558762 ] Bill Mitchell commented on AXIS2C-884: -- One reason it is difficult to isolate exactly

[jira] Issue Comment Edited: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

: Windows XP, Visual Studio 2005, libxml 2.6.25 and libxml 2.6.30, libcurl Reporter: Bill Mitchell Attachments: axis2.trace, desc_builder_diff.txt In a multithreaded application, if the stub/svc client is freed in a thread different from that used when the svc client was built

[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

[ https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556935#action_12556935 ] Bill Mitchell commented on AXIS2C-884: -- Upon re-examining the code in op_client.c, I

[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

[ https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556569#action_12556569 ] Bill Mitchell commented on AXIS2C-884: -- To isolate what kind of fix might work

[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

[ https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556568#action_12556568 ] Bill Mitchell commented on AXIS2C-884: -- I modified my client application to create

[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

[ https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556572#action_12556572 ] Bill Mitchell commented on AXIS2C-884: -- To handle the multithreaded case, clearly

[jira] Created: (AXIS2C-889) misleading error message from generated stub deserialize routine when SOAP fault received

Project: Axis2-C Issue Type: Bug Components: code generation Affects Versions: Current (Nightly) Environment: Windows XP, Visual Studio 2005, libxml, libcurl Reporter: Bill Mitchell Priority: Trivial As you can see from the following line

[jira] Commented: (AXIS2C-860) generated message stubs omit code for attributes in a named attribute group

[ https://issues.apache.org/jira/browse/AXIS2C-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556262#action_12556262 ] Bill Mitchell commented on AXIS2C-860: -- I downloaded the nightly build of 04/Jan/08

[jira] Created: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

Type: Bug Components: core/deployment Affects Versions: Current (Nightly) Environment: Windows XP, Visual Studio 2005, libxml 2.6.25 and libxml 2.6.30, libcurl Reporter: Bill Mitchell In a multithreaded application, if the stub/svc client is freed in a thread

[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client

[ https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556180#action_12556180 ] Bill Mitchell commented on AXIS2C-884: -- Much as I like the source fix in my

[jira] Commented: (AXIS2C-849) Generated stub for SimpleType List of String returns no contents

[ https://issues.apache.org/jira/browse/AXIS2C-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12555246#action_12555246 ] Bill Mitchell commented on AXIS2C-849: -- Great, Dimuthu. I rebuilt the stubs, adapted

[jira] Commented: (AXIS2C-855) Generated stubs leak memory associated with string/array properties

[ https://issues.apache.org/jira/browse/AXIS2C-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555011 ] Bill Mitchell commented on AXIS2C-855: -- I regenerated with a new build and verified that the reset code is now

[jira] Reopened: (AXIS2C-848) Generated stub for unbounded sequence of type any does not pass any elements to client

[ https://issues.apache.org/jira/browse/AXIS2C-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell reopened AXIS2C-848: -- On a more recent build, I have verified that there is no compilation error in the generated stub

[jira] Updated: (AXIS2C-848) Generated stub for unbounded sequence of type any does not pass any elements to client

[ https://issues.apache.org/jira/browse/AXIS2C-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-848: - Attachment: service.wsdl Generated stub for unbounded sequence of type any does not pass any

[jira] Created: (AXIS2C-860) generated message stubs omit code for attributes in a named attribute group

Issue Type: Bug Components: code generation Affects Versions: Current (Nightly) Environment: Windows XP, Visual Studio 2005, libxml, libcurl Reporter: Bill Mitchell Priority: Minor Attachments: service.wsdl, unrolled_attrgrp.wsdl When a message

[jira] Updated: (AXIS2C-860) generated message stubs omit code for attributes in a named attribute group

[ https://issues.apache.org/jira/browse/AXIS2C-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-860: - Attachment: unrolled_attrgrp.wsdl service.wsdl For the attached service.wsdl

[jira] Created: (AXIS2C-861) Enable client session management through http cookies in libcurl

Components: transport/http Affects Versions: Current (Nightly) Environment: Windows XP, Visual Studio 2005, libxml, libcurl Reporter: Bill Mitchell Many existing SOAP services maintain session context through HTTP cookies. This can be seen in the prevalence

  1   2   >