January 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2671) org.jboss.ws.core.soap.SOAPMessageImpl does not implement setProperty and getProperty methods

by Edward Pilipczuk (JIRA)

org.jboss.ws.core.soap.SOAPMessageImpl does not implement setProperty and getProperty methods ---------------------------------------------------------------------------------------------- Key: JBWS-2671 URL: https://jira.jboss.org/jira/browse/JBWS-2671 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.1 Environment: Windows XP, JBoss AS 4.2.3GA (JBossWS upgraded to 3.1.1GA), JDK 1.6.0_14 Reporter: Edward Pilipczuk Priority: Critical I am trying to implement SOAPClient that invokes WebService by use of Dispatch<Object> interface with JAXB. When trying to write the code like in the following tutorial --> http://www.omii.ac.uk/wiki/JaxWsTutorial#section-JaxWsTutorial-Example6.J... I got an exception as below: 13:55:58,453 ERROR [DispatchImpl] Cannot dispatch message java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage at javax.xml.soap.SOAPMessage.setProperty(Unknown Source) at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:87) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:169) at org.jboss.ws.core.jaxws.client.DispatchSOAPBinding.getRequestMessage(DispatchSOAPBinding.java:121) at org.jboss.ws.core.jaxws.client.DispatchImpl.getRequestMessage(DispatchImpl.java:450) at org.jboss.ws.core.jaxws.client.DispatchImpl.invokeInternalSOAP(DispatchImpl.java:183) at org.jboss.ws.core.jaxws.client.DispatchImpl.invokeInternal(DispatchImpl.java:170) at org.jboss.ws.core.jaxws.client.DispatchImpl.invoke(DispatchImpl.java:133) at application.package.SOAPClient.process(SOAPClient.java:254) Looking into the source of the classes listed in stacktrace I found that SOAPMessageImpl class does not implement required setProperty() and getProperty() methods. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1439) Jdk 1.6.0 Requests get the error "setProperty must be overridden by all subclasses of SOAPMessage"

by Denis Angleton (JIRA)

Jdk 1.6.0 Requests get the error "setProperty must be overridden by all subclasses of SOAPMessage" -------------------------------------------------------------------------------------------------- Key: JBWS-1439 URL: http://jira.jboss.com/jira/browse/JBWS-1439 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Environment: Jboss 4.0.5.GA Java 1.6.0 Reporter: Denis Angleton Requests get the error "setProperty must be overridden by all subclasses of SOAPMessage" In the abstract class javax.xml.soap.SOAPMessage which is now shipped with the jdk, the implementation of setProperty is as follows: public void setProperty(String property, Object value) throws SOAPException { throw new UnsupportedOperationException("setProperty must be overridden by all subclasses of SOAPMessage"); } in the constructor of org.jboss.ws.soap.SOAPMessageImpl it calls the super methods setProperty(CHARACTER_SET_ENCODING, "UTF-8"); setProperty(WRITE_XML_DECLARATION, false); This results in the exception being thrown. -- 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

12 years, 2 months

19
33
0 / 0

[JBoss JIRA] Created: (JBWS-3166) Review the code which enable the mtom threshold configuration from DDEndpoint in both spring and without spring stack

by Jim Ma (JIRA)

Review the code which enable the mtom threshold configuration from DDEndpoint in both spring and without spring stack ---------------------------------------------------------------------------------------------------------------------- Key: JBWS-3166 URL: https://jira.jboss.org/browse/JBWS-3166 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-native-3.4.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 We can probably add some more convenient APIs in cxf to configure the MTOMFeature easily. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-3172) SpringBusHolder.createBus(URL location) does not support the bean class annotated with @PostConstruct

by Jim Ma (JIRA)

SpringBusHolder.createBus(URL location) does not support the bean class annotated with @PostConstruct ------------------------------------------------------------------------------------------------------ Key: JBWS-3172 URL: https://jira.jboss.org/browse/JBWS-3172 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-native-3.4.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 SpringBusHolder has the same issue with https://issues.apache.org/jira/browse/CXF-3157. Look at if load the jbossws-cxf.xml with FileSystemXmlApplicationContext can fix this issue. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2710) Provide testcase for WS-Trust (server side) and WS-SecureConversation

by Alessio Soldano (JIRA)

Provide testcase for WS-Trust (server side) and WS-SecureConversation --------------------------------------------------------------------- Key: JBWS-2710 URL: https://jira.jboss.org/jira/browse/JBWS-2710 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano http://cwiki.apache.org/CXF20DOC/ws-trust.html http://cwiki.apache.org/CXF20DOC/ws-secureconversation.html -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2932) Support for HTTP Digest authentication, when acting as a client to an external web service

by Ian (JIRA)

Support for HTTP Digest authentication, when acting as a client to an external web service ------------------------------------------------------------------------------------------ Key: JBWS-2932 URL: https://jira.jboss.org/jira/browse/JBWS-2932 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-metro-3.2.1, jbossws-native-3.2.1, jbossws-cxf-3.2.1 Reporter: Ian Please implement HTTP Digest Authentication when acting as a client to an external web service. I don't mean using WS-Security, just using HTTP authentication in a similar that Basic Authentication is used - using JAX-WS code similar to this: String url = configuration.getString(CONFIG_URL); BindingProvider provider = (BindingProvider)requestInvoker; provider.getRequestContext().put(BindingProvider.USERNAME_PROPERTY, username); provider.getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, password); This code works if run as a standalone java client (probably because Metro supports it). However it doesn't work with JBossWS: * Native implementation simply doesn't work at all * Metro implementation has classloading issues when web service calls are made (to do with WS-Addressing I think, I've seen other posts about it). * CXF has the same issues as Metro Given from my reading that the WS-Security work supports Digest authentication, it doesn't seem a difficult task. I'd suggest one of two ways to fix it: 1. Implement it in JBossWS native, OR 2. Fix the classloading issues in Metro and/or CXF so those stacks can be used (given they already support it). -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2569) Soap over TCP/IP Transport for Jboss WS

by Bryan Kearney (JIRA)

Soap over TCP/IP Transport for Jboss WS --------------------------------------- Key: JBWS-2569 URL: https://jira.jboss.org/jira/browse/JBWS-2569 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Jboss 5.0.X, any WS stack, running on Fedora Reporter: Bryan Kearney I would like to see one of the supported WS stackes support SOAP over a TCP/IP transport instead of http. I have 2 main drivers for this: 1) Performance (http://blogs.sun.com/oleksiys/entry/soap_tcp_makes_web_services). 2) Interoperability with the M$ stack, specifically the WCF classes. -- bk -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1814) Dynamic Encryption based on clients input

by Magesh Kumar B (JIRA)

Dynamic Encryption based on clients input ----------------------------------------- Key: JBWS-1814 URL: http://jira.jboss.com/jira/browse/JBWS-1814 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.1, jbossws-1.2.1 Reporter: Magesh Kumar B Let's say that Bob runs the web service and Alice has a client that uses the web service. Now John would also like to use the web service. John would create: johns.keystore ---------------- john - keyPair (pub+priv) bob - trustedCertEntry (pub) johns.truststore ---------------- john - trustedCertEntry (just john's public key) In addition, Bob's keystore would be updated to: bobs.keystore ---------------- bob - keyPair (public + private key) alice - trustedCertEntry (just alice's public key) john - trustedCertEntry (just john's public key) This does not pose a problem for encrypting the request from the client side since both Alice and John use Bob's public key to encrypt the message, and Bob of course uses his pirvate key to decrypt the message. But how is the response message encrypted? JBossWS apparently does not support multiple clients because the certificate used by the server to encrypt the response is specified statically in jboss-wsse-server.xml. -- 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

12 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-2535) Multiple security domain check is too overzealous

by Galder Zamarreno (JIRA)

Multiple security domain check is too overzealous ------------------------------------------------- Key: JBWS-2535 URL: https://jira.jboss.org/jira/browse/JBWS-2535 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assignee: Darran Lofthouse If you mix up EJB3 SLSBs without security domains and SLSBs with SecurityDomain("other"), and you add an EJB3 WS endpoint to the deployment archive, the deployment would fail with an exception similar to this: Caused by: java.lang.IllegalStateException: Multiple security domains not supported at org.jboss.wsf.container.jboss50.deployment.tomcat.SecurityHandlerEJB3.addSecurityDomain(SecurityHandlerEJB3.java:58) at org.jboss.wsf.container.jboss50.transport.WebAppGenerator.createJBossWebAppDescriptor(WebAppGenerator.java:268) at org.jboss.wsf.container.jboss50.transport.WebAppGenerator.generatWebDeployment(WebAppGenerator.java:101) at org.jboss.wsf.container.jboss50.transport.WebAppGenerator.create(WebAppGenerator.java:85) at org.jboss.wsf.container.jboss50.transport.EJBHttpTransportManager.createListener(EJBHttpTransportManager.java:78) at org.jboss.wsf.framework.deployment.HttpTransportDeploymentAspect.create(HttpTransportDeploymentAspect.java:76) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.create(DeploymentAspectManagerImpl.java:121) at org.jboss.wsf.container.jboss50.BareWSFRuntime.create(BareWSFRuntime.java:61) at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:84) at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHookEJB.deploy(AbstractDeployerHookEJB.java:43) at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60) at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:112) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) ... 18 more The validation seems to be a bit too overzealous. -- 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, 5 months

8
10
0 / 0

[JBoss JIRA] Created: (JBWS-3109) Global handler to intercept/observe inbound/outbound messages

by Gary Brown (JIRA)

Global handler to intercept/observe inbound/outbound messages ------------------------------------------------------------- Key: JBWS-3109 URL: https://jira.jboss.org/browse/JBWS-3109 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Gary Brown Although individual web services can be configured to use JAX-WS handlers to intercept messages, it would be useful to be able to define a 'global' (server wide) handler that could intercept messages inbound and outbound from any deployed web services, regardless of the web service stack in use. -- 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, 6 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2011