May 2010 - jbossws-issues - Jboss List Archives

[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

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

14 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-3028) Complete UsernameToken JAAS integration

by Alessio Soldano (JIRA)

Complete UsernameToken JAAS integration --------------------------------------- Key: JBWS-3028 URL: https://jira.jboss.org/jira/browse/JBWS-3028 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0 The current jaas integration in org.jboss.wsf.stack.cxf.security.authentication.SubjectCreatingInterceptor still need support for digests, nonces, etc. We might also evaluate using the PicketBox API. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBWS-3023) Windows issue in URLLoaderAdapter.getChildren()

by Jim Ma (JIRA)

Windows issue in URLLoaderAdapter.getChildren() ----------------------------------------------- Key: JBWS-3023 URL: https://jira.jboss.org/jira/browse/JBWS-3023 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Environment: Windows Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0, jbossws-metro-4.0, jbossws-native-4.0 common tests are failed on windows platform : java.lang.StringIndexOutOfBoundsException: String index out of range: -6 at java.lang.String.substring(String.java:1937) at org.jboss.wsf.common.URLLoaderAdapter.getChildren(URLLoaderAdapter.java:157) at org.jboss.test.ws.common.URLLoaderAdapterTestCase.testWithJar(URLLoaderAdapterTestCase.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec <<< FAILURE! Results : Failed tests: testWithJar(org.jboss.test.ws.common.ResourceLoaderAdapterTestCase) testWithDir(org.jboss.test.ws.common.ResourceLoaderAdapterTestCase) testWithJar(org.jboss.test.ws.common.URLLoaderAdapterTestCase) -- 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

[JBoss JIRA] Created: (JBWS-2945) JAX-WS 2.2 implementation not yet available for CXF stack

by Richard Opalka (JIRA)

JAX-WS 2.2 implementation not yet available for CXF stack --------------------------------------------------------- Key: JBWS-2945 URL: https://jira.jboss.org/jira/browse/JBWS-2945 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-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

14 years, 6 months

2
1
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

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

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

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

14 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-3045) Create errata report for JBossWS-Metro 3.3.0.GA

by Alessio Soldano (JIRA)

Create errata report for JBossWS-Metro 3.3.0.GA ----------------------------------------------- Key: JBWS-3045 URL: https://jira.jboss.org/browse/JBWS-3045 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Assignee: Richard Opalka Fix For: jbossws-metro-3.3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
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