December 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2715) JAXBIntroductions support

by Alessio Soldano (JIRA)

JAXBIntroductions support ------------------------- Key: JBWS-2715 URL: https://jira.jboss.org/jira/browse/JBWS-2715 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Fix For: community contributions JAXBIntros are currrently supported on Native stack only. We should investigate whether adding support for that in JBossWS-Metro is useful and how to do that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1716) Erroneous UTF-8 character encoding when marshalling on machines with non-UTF-8 default encoding

by floe fliep (JIRA)

Erroneous UTF-8 character encoding when marshalling on machines with non-UTF-8 default encoding ----------------------------------------------------------------------------------------------- Key: JBWS-1716 URL: http://jira.jboss.com/jira/browse/JBWS-1716 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: floe fliep When sending a client request which includes a non-ASCII UTF-8 character such as the "ç" in "Français" on a machine which has the default character encoding set to something different than UTF-8, the encoding is erroneous. For example, the "ç" in the example above is marshalled on the network stream as 0xC3 0x83 0xC2 0xA7 instead of the legal UTF-8 sequence being 0xC3 0xA7, when the machine's default character set is set to MS1252 in this case (Windows). A fix for this is setting the system property file.encoding=utf-8, but this causes as many problems elsewhere as it fixes (especially in the case of legacy platform-specific file reading) ... . A forum post is highly likely to expose the same phenomenon: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030510#4030510 After some good hours of stepping through the JBossWS code, I discovered what I guess must be the culprit in the method XMLFragment.writeSourceInternal(Writer writer): .... if (reader == null) reader = new InputStreamReader(streamSource.getInputStream()); Here streamSource.getInputStream() is an already UTF-8 encoded stream. However, when a new instance of InputStreamReader is created around it, it will be set to the machine's default character encoding, thus effectively interpreting bytes from the UTF-8 stream in a different encoding scheme, resulting in corrupted data. Each time data passes through the marschalling corruption is added, effectively worsening wrong character count when data is passed back and forth. I would suggest attaching a reader to the StreamSource source instance var so that it keeps track of its encoding, but that might break things elsewhere ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-2592) javax.xml.rpc.encoding.XMLType QName constants have wrong namespace URIs

by Dmitriy Kuznetsov (JIRA)

javax.xml.rpc.encoding.XMLType QName constants have wrong namespace URIs ------------------------------------------------------------------------ Key: JBWS-2592 URL: https://jira.jboss.org/jira/browse/JBWS-2592 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.0 Environment: JBoss 4.2 or later Reporter: Dmitriy Kuznetsov The javax.xml.rpc.encoding.XMLType class in JBossWS incorrectly defines the QName constants. For example SOAP_STRING is defined as: public static final QName SOAP_STRING = QName.valueOf("{SOAP-ENC}string"); It must be defined as public static final QName SOAP_STRING = QName.valueOf("{http://schemas.xmlsoap.org/soap/encoding/}string"); or public static final QName SOAP_STRING = new QName("http://schemas.xmlsoap.org/soap/encoding/", "string"); Generally, the namespace URI must be http://schemas.xmlsoap.org/soap/encoding/ for the SOAP_xxx constants and http://www.w3.org/2001/XMLSchema for the XSD_xxx constants. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1763) Specified charset type not used when parsing request

by Darran Lofthouse (JIRA)

Specified charset type not used when parsing request ---------------------------------------------------- Key: JBWS-1763 URL: http://jira.jboss.com/jira/browse/JBWS-1763 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.0.SP1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.1 Specified charset type not used when parsing request message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2294) Verify compliance with WSI profiles

by Alessio Soldano (JIRA)

Verify compliance with WSI profiles ----------------------------------- Key: JBWS-2294 URL: https://jira.jboss.org/jira/browse/JBWS-2294 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Mark says: Hi Alessio. Do you know if we can claim compliance with the WSI Basic Security Profile? We should first run the Compliance Tool for the BP, then we should verify if we comply to the BSP assertion related to the specs implemented in Native. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-2458) Support UseAddressing in wsdl

by Alessio Soldano (JIRA)

Support UseAddressing in wsdl ----------------------------- Key: JBWS-2458 URL: https://jira.jboss.org/jira/browse/JBWS-2458 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native, ws-addressing Reporter: Alessio Soldano We should support the UseAddressing wsdl binding extension for enabling WS-Addressing, like Metro does. This could be achieved in the WSDL11Reader by adding the AddressingFeature to the metadata. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2788) Our JBossWS native client is not able to process MIME multipart HTTP responses that are not chunked

by Richard Opalka (JIRA)

Our JBossWS native client is not able to process MIME multipart HTTP responses that are not chunked --------------------------------------------------------------------------------------------------- Key: JBWS-2788 URL: https://jira.jboss.org/jira/browse/JBWS-2788 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1 Reporter: Richard Opalka Fix For: jbossws-native-3.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2679) Add support for compression for endpoints and clients

by Darran Lofthouse (JIRA)

Add support for compression for endpoints and clients ----------------------------------------------------- Key: JBWS-2679 URL: https://jira.jboss.org/jira/browse/JBWS-2679 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Darran Lofthouse Fix For: jbossws-native-3.2.0 Add support for compression for endpoints and clients. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2778) java.net.HttpRetryException: cannot retry due to server authentication, in streaming mode

by Richard Opalka (JIRA)

java.net.HttpRetryException: cannot retry due to server authentication, in streaming mode ------------------------------------------------------------------------------------------ Key: JBWS-2778 URL: https://jira.jboss.org/jira/browse/JBWS-2778 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.2.1 Reporter: Richard Opalka Fix For: jbossws-cxf-3.3 WS-RM resending capability fails on this exception on server side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
12
0 / 0

[JBoss JIRA] Created: (JBWS-2844) The deploy script does not endorse the cxf and metro jaxws implementation

by Jim Ma (JIRA)

The deploy script does not endorse the cxf and metro jaxws implementation -------------------------------------------------------------------------- Key: JBWS-2844 URL: https://jira.jboss.org/jira/browse/JBWS-2844 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-metro-3.2.2, jbossws-cxf-3.2.2 There is no endorsed jars for metro and native stack under $JBOSS_HOME/lib/endorsed, this will cause ServiceObjectFactory uses sun's RI class in JDK. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2009