[jira] Commented: (AXIS2-4733) Incorrect content-type used in serialized SOAP message for an XML document attachment

[ https://issues.apache.org/jira/browse/AXIS2-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876547#action_12876547 ] Phil Adams commented on AXIS2-4733: --- Rich, I don't quite understand the need for the extr

[jira] Commented: (AXIS2-4733) Incorrect content-type used in serialized SOAP message for an XML document attachment

[ https://issues.apache.org/jira/browse/AXIS2-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876516#action_12876516 ] Rich Scheuerle commented on AXIS2-4733: --- Hi Phil, I inspected the patch, and I unde

[jira] Assigned: (AXIS2-4733) Incorrect content-type used in serialized SOAP message for an XML document attachment

[ https://issues.apache.org/jira/browse/AXIS2-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle reassigned AXIS2-4733: - Assignee: Rich Scheuerle > Incorrect content-type used in serialized SOAP message for an

[jira] Updated: (AXIS2-4733) Incorrect content-type used in serialized SOAP message for an XML document attachment

[ https://issues.apache.org/jira/browse/AXIS2-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Adams updated AXIS2-4733: -- Attachment: patch.txt Attaching patch.txt which contains the "svn diff" of my changes... > Incorrect c

[jira] Created: (AXIS2-4733) Incorrect content-type used in serialized SOAP message for an XML document attachment

Incorrect content-type used in serialized SOAP message for an XML document attachment - Key: AXIS2-4733 URL: https://issues.apache.org/jira/browse/AXIS2-4733 Project:

Hudson build became unstable: axis2-transports-trunk #84

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Hudson build became unstable: axis2-transports- trunk » Apache Axis2 - Transport - HTTP Tests #84

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: java-dev-h..

[jira] Closed: (AXIS2-4732) Operation invocation failed when using partial WSDL.

[ https://issues.apache.org/jira/browse/AXIS2-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker closed AXIS2-4732. > Operation invocation failed when using partial WSDL. > --

[jira] Resolved: (AXIS2-4732) Operation invocation failed when using partial WSDL.

[ https://issues.apache.org/jira/browse/AXIS2-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-4732. -- Resolution: Fixed Issue resolved with revision 952358 > Operation invocation failed when using

[jira] Created: (AXIS2-4732) Operation invocation failed when using partial WSDL.

Operation invocation failed when using partial WSDL. Key: AXIS2-4732 URL: https://issues.apache.org/jira/browse/AXIS2-4732 Project: Axis2 Issue Type: Bug Components: jaxws

[jira] Updated: (AXIS2-4732) Operation invocation failed when using partial WSDL.

[ https://issues.apache.org/jira/browse/AXIS2-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker updated AXIS2-4732: - Attachment: patch_os.txt Attached is the fix for this issue. > Operation invocation failed when

[jira] Assigned: (AXIS2-4732) Operation invocation failed when using partial WSDL.

[ https://issues.apache.org/jira/browse/AXIS2-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker reassigned AXIS2-4732: Assignee: Nikhil Thaker > Operation invocation failed when using partial WSDL. > --

[jira] Commented: (AXIS2-4610) ServiceLifeCycle shutDown() doesn't fire upon hot update

[ https://issues.apache.org/jira/browse/AXIS2-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876287#action_12876287 ] Scott Pelton commented on AXIS2-4610: - I am experiencing the same problem. Thought shut

Re: WSDL for 1 and 2d string array

So Axis2 does not support 2d arrays? On Mon, Jun 7, 2010 at 2:41 PM, WJ Krpelan wrote: > Hi, > a 2d string is no XML-Schema-standard type and because of this you would > have to do your own serialization, as for all home-grown-datastructures > likewise. > Anyway, every 2d string is made up of

Re: WSDL for 1 and 2d string array

Hi, a 2d string is no XML-Schema-standard type and because of this you would have to do your own serialization, as for all home-grown-datastructures likewise. Anyway, every 2d string is made up of some number of ordinary strings, isnt it? Cheers Wolfgang --- On Sun, 6/6/10, Chinmoy Chakraborty