February 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3445) Client hangs when service container requires client-cert and no certificate is specified.

by Alex O (JIRA)

Alex O created JBWS-3445: ---------------------------- Summary: Client hangs when service container requires client-cert and no certificate is specified. Key: JBWS-3445 URL: https://issues.jboss.org/browse/JBWS-3445 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: Alex O If a web service client attempts to access an endpoint that requires HTTP CLIENT-CERT authentication, and no certificate is provided by the client through the javax.net.ssl settings, then the client hangs indefinitely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-3019) Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings

by David Waters (JIRA)

Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings ------------------------------------------------------------------------------ Key: JBWS-3019 URL: https://jira.jboss.org/jira/browse/JBWS-3019 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Environment: jboss-5.1.0.GA, Sun java 1.6.0_14, Window XP 64bit, Intel Core2 Reporter: David Waters In order to talk to a NTLM secured webservice I go through a NTLM Http proxy (ntlmaps). I configure this proxy through a java.net.ProxySelector (ProxySelector.setDefault(aCustomProxySelector)). This was working (with issues) with the version of jbossws that ships with jboss 5.1.0GA (jbossws version 3.1.2.GA). I was required to turn off chunking so I updated to jbossws 3.2.2GA and used ChunkedEncodingFeature to disable chunking. The installation of jbossws 3.2.2 stopped the webservice calls calling my proxy selector and did not use my configured proxy. I have tried to find any way to reinstate the proxy but have been unsuccessful. -- 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

12 years, 9 months

3
2
0 / 0

[JBoss JIRA] (JBWS-3435) Enable appclient based tests

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3435: ------------------------------------ Summary: Enable appclient based tests Key: JBWS-3435 URL: https://issues.jboss.org/browse/JBWS-3435 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-4.0.2, jbossws-native-4.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2302) Verify dependencies on outstanding Metro issues

by Alessio Soldano (JIRA)

Verify dependencies on outstanding Metro issues ----------------------------------------------- Key: JBWS-2302 URL: https://jira.jboss.org/jira/browse/JBWS-2302 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.4 Before releasing we should check if some of the Metro issue we created have been solved, so that the corresponding JBossWS issue can be solved. -- 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

12 years, 9 months

3
22
0 / 0

[JBoss JIRA] (JBWS-3439) Upgrade to Apache WSS4J 1.6.5 and Santuario 1.5

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3439: ------------------------------------- Summary: Upgrade to Apache WSS4J 1.6.5 and Santuario 1.5 Key: JBWS-3439 URL: https://issues.jboss.org/browse/JBWS-3439 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] (JBWS-3444) Review and enable appclient tests

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3444: ------------------------------------ Summary: Review and enable appclient tests Key: JBWS-3444 URL: https://issues.jboss.org/browse/JBWS-3444 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-4.0.2, jbossws-native-4.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2930) IllegalArgumentException: Illegal null argument:ns - Raised initialising Service referencing a WSDL which imports a xsd with no namespace

by Darran Lofthouse (JIRA)

IllegalArgumentException: Illegal null argument:ns - Raised initialising Service referencing a WSDL which imports a xsd with no namespace ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2930 URL: https://jira.jboss.org/jira/browse/JBWS-2930 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.0 The following exception is thrown when a Service is initialised using a WSDL that imports a schema with no namespace: - java.lang.IllegalArgumentException: Illegal null argument:ns at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.createNamespaceItemIfNotExistent(JBossXSModel.java:511) at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.addXSElementDeclaration(JBossXSModel.java:351) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.copyXSModel(WSSchemaUtils.java:707) at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:202) -- 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

12 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBWS-3055) SOAPElementImpl.getElementsByTagName does not return correct results.

by Marek Baluch (JIRA)

SOAPElementImpl.getElementsByTagName does not return correct results. --------------------------------------------------------------------- Key: JBWS-3055 URL: https://jira.jboss.org/browse/JBWS-3055 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Environment: jbossws version: JBossWS-native 3.1.2.SP3_CP01 Reporter: Marek Baluch If SOAPElementImpl.getElementsByTagName(String str) method is called on an element which has a child element with a tag name <ns4:RequestedSecurityToken>...</ns4:RequestedSecurityToken> and the input parameter is only the name without namespace ("RequestedSecurityToken") then the element will not be found. -- 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

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2843) wsprovide tool does not check the annotation and method signature

by Jim Ma (JIRA)

wsprovide tool does not check the annotation and method signature ----------------------------------------------------------------- Key: JBWS-2843 URL: https://jira.jboss.org/jira/browse/JBWS-2843 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Jim Ma wsprovide tool will generate wrong wsdl for this wrong jaxws annotated add method (the parameter style should be wrapped: @SOAPBinding(parameterStyle = ParameterStyle.BARE) public class Test { @WebMethod public int add(int a, int b) { return(a + b); } We should validate this method and it's annotation before generate wsdl . -- 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

12 years, 9 months

3
10
0 / 0

[JBoss JIRA] (JBWS-3447) Properly set classpath for valid JAXWS Provider resolution in binary distro testsuite

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3447: ------------------------------------- Summary: Properly set classpath for valid JAXWS Provider resolution in binary distro testsuite Key: JBWS-3447 URL: https://issues.jboss.org/browse/JBWS-3447 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.2 The binary distro testsuite is run through Ant and relies on the configured java.endorsed.dirs + classpath for correctly selecting the JAXWS Provider impl. On JBossWS-CXF, the javax.xml.ws.spi.provider service is configured both in cxf-rt-frontend-jaxws.jar and jbossws-cxf-factories.jar. The latter (jbossws conf) needs to either come first in the classpath or be in java.endorsed.dirs. Given AS7 does not come with an explicit folder for endorsing, properly set java.endorsed.dirs env implies the same knowledge as sorting the entries in the Ant classpath (AS7 relies on modules for preventing this; but users can use that for in-container clients only). Hence we should sort the classpath in the jbossws-cxf binary testsuite so that jbossws-cxf-factories.jar comes before cxf-rt-frontend-jaxws.jar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 February 2012