You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by ji...@apache.org on 2004/04/27 12:20:56 UTC
[jira] Created: (WSFX-1) WsDoAllSender does not correctly handles international characters
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-1
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-1
Summary: WsDoAllSender does not correctly handles international characters
Type: Bug
Status: Unassigned
Priority: Major
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Rodrigo Ruiz
Created: Tue, 27 Apr 2004 3:18 AM
Updated: Tue, 27 Apr 2004 3:18 AM
Environment: Any platform
JDK 1.4
file.encoding != UTF-8 (client-side)
Description:
The request is corrupted when it contains international characters.
I have no access to the CVS, so it's difficult to me to provide a patch as I would like, but I have tracked the bug down to the following code in WSDoAllSender class:
public void invoke(MessageContext mc) throws AxisFault {
...
ByteArrayOutputStream os = new ByteArrayOutputStream();
XMLUtils.outputDOM(doc, os, true);
String osStr = os.toString();
...
}
The outputDOM seems to generate the XML string in UTF-8, but if file.encoding has another value, the os.toString() call obtains a corrupted string.
The following replacement works for me:
String osStr = null;
try {
osStr = os.toString("UTF-8");
}
catch (UnsupportedEncodingException e) {
osStr = os.toString();
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (WSFX-1) WsDoAllSender does not correctly handles international characters
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Wed, 5 May 2004 6:15 AM
Fixed the bug. please try latest cvs. make sure you use the axis jar in the lib directory.
-- dims
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-1
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-1
Summary: WsDoAllSender does not correctly handles international characters
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Rodrigo Ruiz
Created: Tue, 27 Apr 2004 3:18 AM
Updated: Wed, 5 May 2004 6:15 AM
Environment: Any platform
JDK 1.4
file.encoding != UTF-8 (client-side)
Description:
The request is corrupted when it contains international characters.
I have no access to the CVS, so it's difficult to me to provide a patch as I would like, but I have tracked the bug down to the following code in WSDoAllSender class:
public void invoke(MessageContext mc) throws AxisFault {
...
ByteArrayOutputStream os = new ByteArrayOutputStream();
XMLUtils.outputDOM(doc, os, true);
String osStr = os.toString();
...
}
The outputDOM seems to generate the XML string in UTF-8, but if file.encoding has another value, the os.toString() call obtains a corrupted string.
The following replacement works for me:
String osStr = null;
try {
osStr = os.toString("UTF-8");
}
catch (UnsupportedEncodingException e) {
osStr = os.toString();
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (WSFX-1) WsDoAllSender does not correctly handles international characters
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Christof Soehngen
Created: Wed, 5 May 2004 2:23 AM
Body:
IMHO, the patch has to be applied in WSDoAllReceiver, too (like in WSDoAllSender, the same conversion into a string takes place in WSDoAllReceiver).
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/WSFX-1?page=comments#action_35407
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-1
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-1
Summary: WsDoAllSender does not correctly handles international characters
Type: Bug
Status: Unassigned
Priority: Major
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Rodrigo Ruiz
Created: Tue, 27 Apr 2004 3:18 AM
Updated: Wed, 5 May 2004 2:23 AM
Environment: Any platform
JDK 1.4
file.encoding != UTF-8 (client-side)
Description:
The request is corrupted when it contains international characters.
I have no access to the CVS, so it's difficult to me to provide a patch as I would like, but I have tracked the bug down to the following code in WSDoAllSender class:
public void invoke(MessageContext mc) throws AxisFault {
...
ByteArrayOutputStream os = new ByteArrayOutputStream();
XMLUtils.outputDOM(doc, os, true);
String osStr = os.toString();
...
}
The outputDOM seems to generate the XML string in UTF-8, but if file.encoding has another value, the os.toString() call obtains a corrupted string.
The following replacement works for me:
String osStr = null;
try {
osStr = os.toString("UTF-8");
}
catch (UnsupportedEncodingException e) {
osStr = os.toString();
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (WSFX-1) WsDoAllSender does not correctly handles international characters
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Christof Soehngen
Created: Wed, 5 May 2004 2:05 AM
Body:
I can reproduce the behaviour.
I put some logs before and after the WSDoAllSender activity (serverside, only signature):
Begin of WSDoAllSender, SOAP Message is:
<Geschlecht>männlich</Geschlecht>
End of WSDoAllSender, SOAP Message is:
<Geschlecht>männlich</Geschlecht>
I applied the suggested patch and it now works fine.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/WSFX-1?page=comments#action_35406
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-1
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-1
Summary: WsDoAllSender does not correctly handles international characters
Type: Bug
Status: Unassigned
Priority: Major
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Rodrigo Ruiz
Created: Tue, 27 Apr 2004 3:18 AM
Updated: Wed, 5 May 2004 2:05 AM
Environment: Any platform
JDK 1.4
file.encoding != UTF-8 (client-side)
Description:
The request is corrupted when it contains international characters.
I have no access to the CVS, so it's difficult to me to provide a patch as I would like, but I have tracked the bug down to the following code in WSDoAllSender class:
public void invoke(MessageContext mc) throws AxisFault {
...
ByteArrayOutputStream os = new ByteArrayOutputStream();
XMLUtils.outputDOM(doc, os, true);
String osStr = os.toString();
...
}
The outputDOM seems to generate the XML string in UTF-8, but if file.encoding has another value, the os.toString() call obtains a corrupted string.
The following replacement works for me:
String osStr = null;
try {
osStr = os.toString("UTF-8");
}
catch (UnsupportedEncodingException e) {
osStr = os.toString();
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [jira] Created: (WSFX-1) WsDoAllSender does not correctly handles international characters
Posted by Davanum Srinivas <di...@yahoo.com>.
Werner,
added you as an admin to ws-fx in jira. can u please take care of this?
thanks,
dims
--- jira@apache.org wrote:
> Message:
>
> A new issue has been created in JIRA.
>
> ---------------------------------------------------------------------
> View the issue:
> http://issues.apache.org/jira/browse/WSFX-1
>
> Here is an overview of the issue:
> ---------------------------------------------------------------------
> Key: WSFX-1
> Summary: WsDoAllSender does not correctly handles international characters
> Type: Bug
>
> Status: Unassigned
> Priority: Major
>
> Project: WSFX
> Components:
> WSS4J
>
> Assignee:
> Reporter: Rodrigo Ruiz
>
> Created: Tue, 27 Apr 2004 3:18 AM
> Updated: Tue, 27 Apr 2004 3:18 AM
> Environment: Any platform
> JDK 1.4
> file.encoding != UTF-8 (client-side)
>
> Description:
> The request is corrupted when it contains international characters.
>
> I have no access to the CVS, so it's difficult to me to provide a patch as I would like, but I
> have tracked the bug down to the following code in WSDoAllSender class:
>
>
> public void invoke(MessageContext mc) throws AxisFault {
>
> ...
>
> ByteArrayOutputStream os = new ByteArrayOutputStream();
> XMLUtils.outputDOM(doc, os, true);
> String osStr = os.toString();
>
> ...
>
> }
>
> The outputDOM seems to generate the XML string in UTF-8, but if file.encoding has another value,
> the os.toString() call obtains a corrupted string.
>
> The following replacement works for me:
>
> String osStr = null;
> try {
> osStr = os.toString("UTF-8");
> }
> catch (UnsupportedEncodingException e) {
> osStr = os.toString();
> }
>
>
>
>
> ---------------------------------------------------------------------
> JIRA INFORMATION:
> This message is automatically generated by JIRA.
>
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
>
> If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
[jira] Commented: (WSFX-1) WsDoAllSender does not correctly handles international characters
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Rodrigo Ruiz
Created: Wed, 5 May 2004 4:23 AM
Body:
I agree with you. At last, I had to apply the patch to both handlers yesterday. Applying it only on the sender was not enough.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/WSFX-1?page=comments#action_35408
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-1
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-1
Summary: WsDoAllSender does not correctly handles international characters
Type: Bug
Status: Unassigned
Priority: Major
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Rodrigo Ruiz
Created: Tue, 27 Apr 2004 3:18 AM
Updated: Wed, 5 May 2004 4:23 AM
Environment: Any platform
JDK 1.4
file.encoding != UTF-8 (client-side)
Description:
The request is corrupted when it contains international characters.
I have no access to the CVS, so it's difficult to me to provide a patch as I would like, but I have tracked the bug down to the following code in WSDoAllSender class:
public void invoke(MessageContext mc) throws AxisFault {
...
ByteArrayOutputStream os = new ByteArrayOutputStream();
XMLUtils.outputDOM(doc, os, true);
String osStr = os.toString();
...
}
The outputDOM seems to generate the XML string in UTF-8, but if file.encoding has another value, the os.toString() call obtains a corrupted string.
The following replacement works for me:
String osStr = null;
try {
osStr = os.toString("UTF-8");
}
catch (UnsupportedEncodingException e) {
osStr = os.toString();
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira