October 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1820) Using JRE from vendors other than Sun the Remoting key store and trust store algorithms are not propagated

by Magesh Kumar B (JIRA)

Using JRE from vendors other than Sun the Remoting key store and trust store algorithms are not propagated ---------------------------------------------------------------------------------------------------------- Key: JBWS-1820 URL: http://jira.jboss.com/jira/browse/JBWS-1820 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Environment: IBM JRE 1.5 JBoss4.0.4.GA with JBossWS1.0.4 Reporter: Magesh Kumar B When we use JVMs other than Sun the Remoting properties are not reset from the default. For e.g., using IBM JRE and https SE URL the following exception is thrown. Currently there is no way to set the Remoting SSL Socket Factory parameter REMOTING_ALGORITHM or REMOTING_TRUST_ALGORITHM java.lang.RuntimeException: java.io.IOException: Error creating Remoting SSL Socket Factory:SunX509 KeyManagerFactory not available at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.getSupportedCipherSuites(RemotingSSLSocketFactory.java:657) at com.ibm.jsse2.ExportControl.checkCipherSuites(ExportControl.java:10) at com.ibm.net.ssl.www2.protocol.https.b.afterConnect(b.java:3) at com.ibm.net.ssl.www2.protocol.https.c.connect(c.java:62) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:866) at com.ibm.net.ssl.www2.protocol.https.a.getOutputStream(a.java:25) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:163) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:185) at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:689) at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:398) at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:164) at $Proxy57.vmsdkGetBrowseInfoFromHost(Unknown Source) ................. Caused by: java.io.IOException: Error creating Remoting SSL Socket Factory:SunX509 KeyManagerFactory not available at sun.security.jca.GetInstance.getInstance(GetInstance.java:158) at javax.net.ssl.KeyManagerFactory.getInstance(KeyManagerFactory.java:20) at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.loadKeyManagers(RemotingSSLSocketFactory.java:288) at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.init(RemotingSSLSocketFactory.java:177) at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.getSupportedCipherSuites(RemotingSSLSocketFactory.java:653) ... 65 more Please allow this and other properties to be set in SOAPConnectionImpl.java and CallProxy.java In newer Remoting version we have more properties that can make a difference: REMOTING_KEY_ALIAS REMOTING_CLIENT_AUTH_MODE REMOTING_SERVER_AUTH_MODE REMOTING_SSL_PROTOCOL REMOTING_SSL_PROVIDER_NAME REMOTING_SERVER_SOCKET_USE_CLIENT_MODE REMOTING_SOCKET_USE_CLIENT_MODE -- 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

16 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1502) wsdl-java in wstools-config.xml: location should be relative to config file

by David Robison (JIRA)

wsdl-java in wstools-config.xml: location should be relative to config file --------------------------------------------------------------------------- Key: JBWS-1502 URL: http://jira.jboss.com/jira/browse/JBWS-1502 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: David Robison Priority: Minor The wsdl location specified in the wstools-config.xml file should be relative to that file. This helps when building with ant. If I build with ant from the subproject, it builds well. If I build from the parent directory, it cannot find the location. I use "dir/file.wsdl" but that relative path does not work from the parent directory -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1874) Allow configuration of secret key wrap algorithm

by Alessio Soldano (JIRA)

Allow configuration of secret key wrap algorithm ------------------------------------------------ Key: JBWS-1874 URL: http://jira.jboss.com/jira/browse/JBWS-1874 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.1 Reporter: Alessio Soldano Assigned To: Alessio Soldano WCF wsse interoperability test 3.3 (November 2007) requires the mutual secret key to be wrapped with the RSA-OAEP algorithm. The current implementation always wraps the key with the RSA v1.5 algorithm (despite being able to unwrap using any algorithm). It should be possible to specify the key wrap algorithm in the wsse configuration files. -- 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

16 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-1381) Disable HTTP chunking for J2ME client s

by Thomas Diesler (JIRA)

Disable HTTP chunking for J2ME client s --------------------------------------- Key: JBWS-1381 URL: http://jira.jboss.com/jira/browse/JBWS-1381 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.5 How do I disable HTTP chunking for my EJB3 webservices? I am using @WebMethod etc. I need to disable HTTP chunking because my J2ME client (the wireless toolkit) can't handle chunking yet. -- 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

16 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-1730) Investigate WS-Security with .NET 3.0

by Thomas Diesler (JIRA)

Investigate WS-Security with .NET 3.0 ------------------------------------- Key: JBWS-1730 URL: http://jira.jboss.com/jira/browse/JBWS-1730 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Fix For: jbossws-2.1.1 -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1700) Provide a comprehensive test case for WS-RM

by Thomas Diesler (JIRA)

Provide a comprehensive test case for WS-RM ------------------------------------------- Key: JBWS-1700 URL: http://jira.jboss.com/jira/browse/JBWS-1700 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

16 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1734) Support for SOAP 1.2 in WSProvideTask and WSProvide

by Juergen Zimmermann (JIRA)

Support for SOAP 1.2 in WSProvideTask and WSProvide --------------------------------------------------- Key: JBWS-1734 URL: http://jira.jboss.com/jira/browse/JBWS-1734 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Reporter: Juergen Zimmermann Support the generation of a WSDL file using SOAP 1.2 binding. The JAX-WS RI already provides this possibility. See https://jax-ws.dev.java.net/nonav/2.1.2m1/docs/wsgenant.html -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1695) Use the ClientLauncher from the wsrunclient scripts in order to make @WebServiceRef work from standalone clients

by Heiko Braun (JIRA)

Use the ClientLauncher from the wsrunclient scripts in order to make @WebServiceRef work from standalone clients ----------------------------------------------------------------------------------------------------------------- Key: JBWS-1695 URL: http://jira.jboss.com/jira/browse/JBWS-1695 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: jbossws-2.1.0 -- 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

16 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1632) Read / write wsdl extensibility elements on portType/operation/input

by Alessio Soldano (JIRA)

Read / write wsdl extensibility elements on portType/operation/input --------------------------------------------------------------------- Key: JBWS-1632 URL: http://jira.jboss.com/jira/browse/JBWS-1632 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Priority: Minor Implementation of WS-Policy (issue http://jira.jboss.org/jira/browse/JBWS-856 ) is going to provide marshal and unmarshal mechanism of wsdl extensibility elements (including policies and policy references) to/from the unified wsdl structure. Extensibility elements on definitions/portType/operation/input are going to be ignored for now since processing them required some modifications to the unified wsdl structure; they are not to be ignored any more once this issue is solved. -- 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

16 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1728) Investigate embedded JBossWS

by Thomas Diesler (JIRA)

Investigate embedded JBossWS ---------------------------- Key: JBWS-1728 URL: http://jira.jboss.com/jira/browse/JBWS-1728 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Fix For: jbossws-2.1.1 Endpoint.deploy() should work with jdk1.6 and possibly Jetty -- 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

16 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2007