May 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2596) Resource injection in jaxws endpoints and handlers

by Richard Opalka (JIRA)

Resource injection in jaxws endpoints and handlers -------------------------------------------------- Key: JBWS-2596 URL: https://jira.jboss.org/jira/browse/JBWS-2596 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Richard Opalka Fix For: jbossws-cxf-3.2.0, jbossws-metro-3.2.0 -- 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

14 years, 4 months

3
14
0 / 0

[JBoss JIRA] Created: (JBWS-3001) Verify @PostConstruct and @Predestroy annotations support for POJO based endpoints

by Alessio Soldano (JIRA)

Verify @PostConstruct and @Predestroy annotations support for POJO based endpoints ---------------------------------------------------------------------------------- Key: JBWS-3001 URL: https://jira.jboss.org/jira/browse/JBWS-3001 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0 -- 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

14 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2987) Review JMS integration

by Alessio Soldano (JIRA)

Review JMS integration ---------------------- Key: JBWS-2987 URL: https://jira.jboss.org/jira/browse/JBWS-2987 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0 Properly fix the JMS integration of CXF stack in JBoss. This include completely removing the need for a servlet for a jms endpoint. Related discussions: http://community.jboss.org/thread/89624?tstart=0 http://community.jboss.org/thread/89622?tstart=0 -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2637) incorrect namespace for fault messages

by Bart Vanhaute (JIRA)

incorrect namespace for fault messages -------------------------------------- Key: JBWS-2637 URL: https://jira.jboss.org/jira/browse/JBWS-2637 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.1 Environment: JBossAS-4.2.3.GA Reporter: Bart Vanhaute There is a problem with the namespace for web faults when this namespace is not the same as the namespace of the service. The type definition of the web faults has the correct namespace, but the reference to the type from the message part elements uses the name space qualifier (tns) of the service instead. See the jboss forum for an example. Note: I now tested this again with the 3.1.1 version, and the problem is still the same. -- 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

14 years, 4 months

3
2
0 / 0

[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

14 years, 4 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

14 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-3006) Review jbossws maven dependencies

by Alessio Soldano (JIRA)

Review jbossws maven dependencies --------------------------------- Key: JBWS-3006 URL: https://jira.jboss.org/jira/browse/JBWS-3006 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native, productization Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0, jbossws-metro-4.0, jbossws-native-4.0 Ideally, on trunk we should be able to replace all the deprecated maven dependencies with the new ones. Basically, we should try not to depend on the jboss deprecated maven repository (https://repository.jboss.org/nexus/content/repositories/deprecated/) Also evaluate if the org.jboss.jbossas:jboss-as-depchain can be used to further simplify the maven dependencies we need for running the testsuites. -- 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

14 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-3002) Verify POJO endpoints are shared

by Alessio Soldano (JIRA)

Verify POJO endpoints are shared -------------------------------- Key: JBWS-3002 URL: https://jira.jboss.org/jira/browse/JBWS-3002 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0 This is basically to verify we have the same behaviour as in Native, considering the performance implications this has. See https://jira.jboss.org/jira/browse/JBWS-2486 Ideally, we should have a test in framework for this. -- 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

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2990) Evaluate default enabling soap address rewrite in wsdl with request address

by Alessio Soldano (JIRA)

Evaluate default enabling soap address rewrite in wsdl with request address --------------------------------------------------------------------------- Key: JBWS-2990 URL: https://jira.jboss.org/jira/browse/JBWS-2990 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0, jbossws-native-4.0 -- 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

14 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-3014) JBossWS does not decode Nonce

by Romano Silva (JIRA)

JBossWS does not decode Nonce ----------------------------- Key: JBWS-3014 URL: https://jira.jboss.org/jira/browse/JBWS-3014 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.2.2, jbossws-native-3.2.0, jbossws-native-3.1.2 Environment: JDK 6 JBoss 5.1.0 jdk 6 Windows XP Reporter: Romano Silva I am filing this bug after discussing http://community.jboss.org/message/540669 Nonce is not decoded when encoding type is Base64. UsernameToken has this piece of code: String encodingType = elem.getAttribute("EncodingType"); if (encodingType != null && encodingType.length() > 0 && !Constants.BASE64_ENCODING_TYPE.equalsIgnoreCase(encodingType)) throw new WSSecurityException("Unsupported nonce encoding type: " + encodingType); encodingType is not used anywhere else. In UsernameTokenCallback.java there is the need to decode nonce, so, something like: String nonce = (String)info.getInfo(NONCE); if (nonce != null) { try { digest.update(new BASE64Decoder().decodeBuffer(nonce)); } catch (IOException e) { // ignore exceptions } } need to be added to UsernameTokenCallback.java -- 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

14 years, 6 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2010