[
https://issues.apache.org/jira/browse/AXIS2C-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567627#action_12567627
]
Bill Mitchell commented on AXIS2C-966:
--------------------------------------
Senaka, here's another question, while we are both thinking about this. I
noticed in axis2_libcurl that it causes the xml declaration to be built, then
it determines the text encoding to be inserted in the http content-type header.
And I was wondering why this would not be done in the other order? As the http
content-type character encoding may be configurable, it would make sense,
absent other information, to identify the same character encoding in the http
content-type header and in the xml declaration.
> Guththila has no support for XML declarations
> ---------------------------------------------
>
> Key: AXIS2C-966
> URL: https://issues.apache.org/jira/browse/AXIS2C-966
> Project: Axis2-C
> Issue Type: Bug
> Components: guththila
> Affects Versions: 1.3.0
> Reporter: Senaka Fernando
> Assignee: Senaka Fernando
> Fix For: 1.3.0
>
>
> Guththila has no support for XML declarations. Bill, pointed this out in an
> e-mail sent to the AXIS2C-dev list. It is required that Guththila understands
> the XML declaration elements and simply do not treat it as an error.
> Regards,
> Senaka
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
