You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Liu Cong (JIRA)" <ji...@apache.org> on 2009/05/06 21:54:30 UTC
[jira] Created: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
-------------------------------------------------------------------------------
Key: CXF-2207
URL: https://issues.apache.org/jira/browse/CXF-2207
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.2
Environment: Windowns XP2, JDK1.6.0_11
Reporter: Liu Cong
Fix For: 2.2
MTOM over SOAP/JMS doesn't work.
Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
I have compared the two messages. And I have used several kinds of attatchment for it.
1) Text File. The result is right.
2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
According to the analysis above, reason may be as follows:
1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
2) The server doesn't know the encoding, and just get the text message.
The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated CXF-2207:
------------------------------
Affects Version/s: 2.2
2.0.11
2.1.5
2.2.1
Fix Version/s: 2.2.2
2.1.6
2.0.12
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2, 2.0.11, 2.1.5, 2.2.1, 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Assignee: Willem Jiang
> Fix For: 2.0.12, 2.1.6, 2.2.2
>
> Attachments: patches.rar
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CXF-2207.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.2.2
2.1.6
2.0.12
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2, 2.0.11, 2.1.5, 2.2.1, 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Assignee: Willem Jiang
> Fix For: 2.0.12, 2.1.6, 2.2.2
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706915#action_12706915 ]
Willem Jiang commented on CXF-2207:
-----------------------------------
We can add a check point in the JMSConduit.sendExchange() to show some
warning or throw the exception if the user forget to add the messageType
configuration or set the wrong messageType.
Add the link of the mail thread[1] which discusses this issue.
[1] http://www.nabble.com/How-to-determine-whether-a-soap-message-have-an-attachment-tt23381010.html
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Assignee: Willem Jiang
> Attachments: patches.rar
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CXF-2207) JMS Transport send MTOM
message as a TextMessage. The attachment becomes wrong.
Posted by "Liu Cong (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706577#action_12706577 ]
Liu Cong edited comment on CXF-2207 at 5/6/09 1:18 PM:
-------------------------------------------------------
patches.rar is a serial of patches(git) for this bug.
The source code is the current cxf trunk.
How to fix:
1) If the MTOM is enabled, the JMS message type is ByteMessage.
2) In the client, if the MTOM is enabled, but the client config is not
configed to "byte", an configuration exception will be raised.
3) If the MTOM is not enabled, the JMS message type is the client
config's messageType.
was (Author: liucong):
This is a serial of patches(git) for this bug.
The source code is the current cxf trunk.
How to fix:
1) If the MTOM is enabled, the JMS message type is ByteMessage.
2) In the client, if the MTOM is enabled, but the client config is not
configed to "byte", an configuration exception will be raised.
3) If the MTOM is not enabled, the JMS message type is the client
config's messageType.
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Attachments: patches.rar
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Liu Cong (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liu Cong updated CXF-2207:
--------------------------
Remaining Estimate: (was: 72h)
Original Estimate: (was: 72h)
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Fix For: 2.2
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Liu Cong (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liu Cong updated CXF-2207:
--------------------------
Attachment: (was: patches.rar)
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2, 2.0.11, 2.1.5, 2.2.1, 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Assignee: Willem Jiang
> Fix For: 2.0.12, 2.1.6, 2.2.2
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CXF-2207:
---------------------------------
Assignee: Willem Jiang
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Assignee: Willem Jiang
> Attachments: patches.rar
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Liu Cong (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liu Cong updated CXF-2207:
--------------------------
Affects Version/s: (was: 2.2)
2.2.2
Fix Version/s: (was: 2.2)
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710650#action_12710650 ]
Willem Jiang commented on CXF-2207:
-----------------------------------
LiuCong submitted a patch for it in CXF-1760.
Please check my comments there.
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2, 2.0.11, 2.1.5, 2.2.1, 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Assignee: Willem Jiang
> Fix For: 2.0.12, 2.1.6, 2.2.2
>
> Attachments: patches.rar
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2207) JMS Transport send MTOM message as a
TextMessage. The attachment becomes wrong.
Posted by "Liu Cong (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liu Cong updated CXF-2207:
--------------------------
Attachment: patches.rar
This is a serial of patches(git) for this bug.
The source code is the current cxf trunk.
How to fix:
1) If the MTOM is enabled, the JMS message type is ByteMessage.
2) In the client, if the MTOM is enabled, but the client config is not
configed to "byte", an configuration exception will be raised.
3) If the MTOM is not enabled, the JMS message type is the client
config's messageType.
> JMS Transport send MTOM message as a TextMessage. The attachment becomes wrong.
> -------------------------------------------------------------------------------
>
> Key: CXF-2207
> URL: https://issues.apache.org/jira/browse/CXF-2207
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.2
> Environment: Windowns XP2, JDK1.6.0_11
> Reporter: Liu Cong
> Attachments: patches.rar
>
>
> MTOM over SOAP/JMS doesn't work.
> Thought the client send attachement information and the server get the attachment information, the attachment which is got by the server is not the same with the attachment information which is sent by the client.
> I have compared the two messages. And I have used several kinds of attatchment for it.
> 1) Text File. The result is right.
> 2) WinRaR File. The file that is received by the server is larger than the file that is sent by the client.
> 3) BitMap file. The size of attachment that is sent by the client is 163166, but the size of attachment that is received is 485947, which is 167% more than the original binary data. (http://www.w3.org/TR/2008/WD-soapjms-20081121/#binding-message-body)
> According to the analysis above, reason may be as follows:
> 1) In the client, the attachment is encoded as base64 encoding, and transfer as TextMessage in JMS.
> 2) The server doesn't know the encoding, and just get the text message.
> The current implementation send all the messages as TextMessage because jmsConfig variable in JMSConduit is not initialized according to the MessageType of SOAPMessage. jmsConfig is just configed in wsdl. If the wsdl doesn't have messagetype information, it goes wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.