You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Gee Chia (JIRA)" <ji...@apache.org> on 2007/03/27 15:16:32 UTC
[jira] Created: (AXIS2-2409) SOAP 1.2 contentType problem for
Response
SOAP 1.2 contentType problem for Response
------------------------------------------
Key: AXIS2-2409
URL: https://issues.apache.org/jira/browse/AXIS2-2409
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.2
Reporter: Gee Chia
Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem.
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8
Transfer-Encoding: chunked
Observation:
As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType,
(like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;".
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-2409) SOAP 1.2 contentType problem for
Response
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas reassigned AXIS2-2409:
---------------------------------------
Assignee: Thilina Gunarathne
> SOAP 1.2 contentType problem for Response
> ------------------------------------------
>
> Key: AXIS2-2409
> URL: https://issues.apache.org/jira/browse/AXIS2-2409
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Reporter: Gee Chia
> Assigned To: Thilina Gunarathne
>
> Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem.
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8
> Transfer-Encoding: chunked
> Observation:
> As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType,
> (like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;".
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-2409) SOAP 1.2 contentType problem for
Response
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Daniels reassigned AXIS2-2409:
-----------------------------------
Assignee: Eran Chinthaka (was: Thilina Gunarathne)
> SOAP 1.2 contentType problem for Response
> ------------------------------------------
>
> Key: AXIS2-2409
> URL: https://issues.apache.org/jira/browse/AXIS2-2409
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Reporter: Gee Chia
> Assignee: Eran Chinthaka
> Priority: Blocker
>
> Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem.
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8
> Transfer-Encoding: chunked
> Observation:
> As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType,
> (like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;".
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2409) SOAP 1.2 contentType problem for
Response
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-2409.
-------------------------------------
Resolution: Incomplete
> SOAP 1.2 contentType problem for Response
> ------------------------------------------
>
> Key: AXIS2-2409
> URL: https://issues.apache.org/jira/browse/AXIS2-2409
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Reporter: Gee Chia
> Assignee: Eran Chinthaka
> Priority: Blocker
> Fix For: 1.3
>
>
> Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem.
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8
> Transfer-Encoding: chunked
> Observation:
> As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType,
> (like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;".
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2409) SOAP 1.2 contentType problem for
Response
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-2409:
-------------------------------------
Priority: Blocker (was: Major)
> SOAP 1.2 contentType problem for Response
> ------------------------------------------
>
> Key: AXIS2-2409
> URL: https://issues.apache.org/jira/browse/AXIS2-2409
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Reporter: Gee Chia
> Assignee: Thilina Gunarathne
> Priority: Blocker
>
> Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem.
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8
> Transfer-Encoding: chunked
> Observation:
> As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType,
> (like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;".
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2409) SOAP 1.2 contentType problem for
Response
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504504 ]
Srinath Perera commented on AXIS2-2409:
---------------------------------------
Hi Gee;
If you can recreate the problem that would be very helpful. I tried with normal SOAP messages and it was working fine. Does it happen with MTOM? Please provide more details about the issue.
Thanks
Srinath
> SOAP 1.2 contentType problem for Response
> ------------------------------------------
>
> Key: AXIS2-2409
> URL: https://issues.apache.org/jira/browse/AXIS2-2409
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Reporter: Gee Chia
> Assignee: Thilina Gunarathne
> Priority: Blocker
>
> Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem.
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8
> Transfer-Encoding: chunked
> Observation:
> As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType,
> (like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;".
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2409) SOAP 1.2 contentType problem for
Response
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509338 ]
Davanum Srinivas commented on AXIS2-2409:
-----------------------------------------
We can't figure out the scenario, please help recreate it with some sample.
thanks,
dims
> SOAP 1.2 contentType problem for Response
> ------------------------------------------
>
> Key: AXIS2-2409
> URL: https://issues.apache.org/jira/browse/AXIS2-2409
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Reporter: Gee Chia
> Assignee: Eran Chinthaka
> Priority: Blocker
> Fix For: 1.3
>
>
> Following was captured in TCPMon for a response message for SOAP 1.2. The problem is the ";;" before the charset= attribute in the Content-Type, it actually caused parsing problem.
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml;action="http://services.example.org/startResponse";;charset=UTF-8
> Transfer-Encoding: chunked
> Observation:
> As I traced the code, I observed org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() returns a correct contentType,
> (like application/soap+xml;charset=UTF-8;action="http://services.example.org/startResponse";), Then in SOAPMessageFormatter::writeTo method, once it called OMElement.serializeAndConsume(out, format), the TCPMon displays shows the content type with ";;".
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org