March 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3778) WS-Discovery and IPv6

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3778?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3778: ---------------------------------- Description: Apache CXF WSDiscoveryServiceImpl does {code} udpEndpoint.publish("soap.udp://239.255.255.250:3702"); {code} which is fine as long as an IPv4 network is available. This can lead to the following exception when on a pure IPv6 network: {noformat} [0m[33m06:25:53,342 WARNING [org.apache.cxf.ws.discovery.WSDiscoveryService] (MSC service thread 1-2) Could not start WS-Discovery Service.: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.SocketException: No such device at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.client.ProviderImpl$DelegateEndpointImpl.publish(ProviderImpl.java:421) [jbossws-cxf-client-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.startup(WSDiscoveryServiceImpl.java:247) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.serverStarted(WSDiscoveryServiceImpl.java:153) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.ws.discovery.listeners.WSDiscoveryServerListener.startServer(WSDiscoveryServerListener.java:73) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.bus.managers.ServerLifeCycleManagerImpl.startServer(ServerLifeCycleManagerImpl.java:61) [cxf-rt-core-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:146) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:118) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:137) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:69) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74) [jboss-as-webservices-server-integration-7.4.0.Final-redhat-6.jar:7.4.0.Final-redhat-6] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] Caused by: java.lang.RuntimeException: java.net.SocketException: No such device at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:201) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:893) [cxf-rt-bindings-soap-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] ... 21 more Caused by: java.net.SocketException: No such device at java.net.PlainDatagramSocketImpl.join(Native Method) [rt.jar:1.8.0] at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) [rt.jar:1.8.0] at java.net.MulticastSocket.joinGroup(MulticastSocket.java:323) [rt.jar:1.8.0] at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:185) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] ... 26 more {noformat} was: Apache CXF WSDiscoveryServiceImpl does {code} udpEndpoint.publish("soap.udp://239.255.255.250:3702"); {code} which is fine as long as an IPv4 network is available. This can lead to the following exception when on a pure IPv6 network: {code} [0m[33m06:25:53,342 WARNING [org.apache.cxf.ws.discovery.WSDiscoveryService] (MSC service thread 1-2) Could not start WS-Discovery Service.: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.SocketException: No such device at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.client.ProviderImpl$DelegateEndpointImpl.publish(ProviderImpl.java:421) [jbossws-cxf-client-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.startup(WSDiscoveryServiceImpl.java:247) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.serverStarted(WSDiscoveryServiceImpl.java:153) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.ws.discovery.listeners.WSDiscoveryServerListener.startServer(WSDiscoveryServerListener.java:73) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.bus.managers.ServerLifeCycleManagerImpl.startServer(ServerLifeCycleManagerImpl.java:61) [cxf-rt-core-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:146) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:118) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:137) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:69) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74) [jboss-as-webservices-server-integration-7.4.0.Final-redhat-6.jar:7.4.0.Final-redhat-6] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] Caused by: java.lang.RuntimeException: java.net.SocketException: No such device at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:201) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:893) [cxf-rt-bindings-soap-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] ... 21 more Caused by: java.net.SocketException: No such device at java.net.PlainDatagramSocketImpl.join(Native Method) [rt.jar:1.8.0] at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) [rt.jar:1.8.0] at java.net.MulticastSocket.joinGroup(MulticastSocket.java:323) [rt.jar:1.8.0] at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:185) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] ... 26 more {code} > WS-Discovery and IPv6 > --------------------- > > Key: JBWS-3778 > URL: https://issues.jboss.org/browse/JBWS-3778 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.4 > > > Apache CXF WSDiscoveryServiceImpl does > {code} > udpEndpoint.publish("soap.udp://239.255.255.250:3702"); > {code} > which is fine as long as an IPv4 network is available. > This can lead to the following exception when on a pure IPv6 network: > {noformat} > [0m[33m06:25:53,342 WARNING [org.apache.cxf.ws.discovery.WSDiscoveryService] (MSC service thread 1-2) Could not start WS-Discovery Service.: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.SocketException: No such device > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.jboss.wsf.stack.cxf.client.ProviderImpl$DelegateEndpointImpl.publish(ProviderImpl.java:421) [jbossws-cxf-client-4.3.0.Final.jar:4.3.0.Final] > at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.startup(WSDiscoveryServiceImpl.java:247) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.serverStarted(WSDiscoveryServiceImpl.java:153) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.ws.discovery.listeners.WSDiscoveryServerListener.startServer(WSDiscoveryServerListener.java:73) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.bus.managers.ServerLifeCycleManagerImpl.startServer(ServerLifeCycleManagerImpl.java:61) [cxf-rt-core-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:146) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:118) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:137) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:69) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] > at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74) [jboss-as-webservices-server-integration-7.4.0.Final-redhat-6.jar:7.4.0.Final-redhat-6] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > Caused by: java.lang.RuntimeException: java.net.SocketException: No such device > at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:201) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] > at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:893) [cxf-rt-bindings-soap-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] > ... 21 more > Caused by: java.net.SocketException: No such device > at java.net.PlainDatagramSocketImpl.join(Native Method) [rt.jar:1.8.0] > at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) [rt.jar:1.8.0] > at java.net.MulticastSocket.joinGroup(MulticastSocket.java:323) [rt.jar:1.8.0] > at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:185) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] > ... 26 more > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3778) WS-Discovery and IPv6

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3778: ------------------------------------- Summary: WS-Discovery and IPv6 Key: JBWS-3778 URL: https://issues.jboss.org/browse/JBWS-3778 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.4 Apache CXF WSDiscoveryServiceImpl does {code} udpEndpoint.publish("soap.udp://239.255.255.250:3702"); {code} which is fine as long as an IPv4 network is available. This can lead to the following exception when on a pure IPv6 network: {code} [0m[33m06:25:53,342 WARNING [org.apache.cxf.ws.discovery.WSDiscoveryService] (MSC service thread 1-2) Could not start WS-Discovery Service.: javax.xml.ws.WebServiceException: java.lang.RuntimeException: java.net.SocketException: No such device at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.client.ProviderImpl$DelegateEndpointImpl.publish(ProviderImpl.java:421) [jbossws-cxf-client-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.startup(WSDiscoveryServiceImpl.java:247) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.ws.discovery.internal.WSDiscoveryServiceImpl.serverStarted(WSDiscoveryServiceImpl.java:153) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.ws.discovery.listeners.WSDiscoveryServerListener.startServer(WSDiscoveryServerListener.java:73) [cxf-services-ws-discovery-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.bus.managers.ServerLifeCycleManagerImpl.startServer(ServerLifeCycleManagerImpl.java:61) [cxf-rt-core-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:146) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:118) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:137) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:69) [jbossws-cxf-server-4.3.0.Final.jar:4.3.0.Final] at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74) [jboss-as-webservices-server-integration-7.4.0.Final-redhat-6.jar:7.4.0.Final-redhat-6] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] Caused by: java.lang.RuntimeException: java.net.SocketException: No such device at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:201) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:893) [cxf-rt-bindings-soap-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) [cxf-rt-frontend-jaxws-2.7.10.redhat-1.jar:2.7.10.redhat-1] ... 21 more Caused by: java.net.SocketException: No such device at java.net.PlainDatagramSocketImpl.join(Native Method) [rt.jar:1.8.0] at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) [rt.jar:1.8.0] at java.net.MulticastSocket.joinGroup(MulticastSocket.java:323) [rt.jar:1.8.0] at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPDestination.activate(UDPDestination.java:185) [jbossws-cxf-transports-udp-4.3.0.Final.jar:4.3.0.Final] ... 26 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato commented on JBWS-3777: -------------------------------------- With the help of Jim, I finally realised that this bug originates from CXF; I confirmed that it also occurs in bare CXF {{2.7.10}} and also in {{3.0.0-milestone2}}. > CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL > ---------------------------------------------------------------- > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > Attachments: ws-rm.zip > > > Please port the fix for [CXF-5645|https://issues.apache.org/jira/browse/CXF-5645] to JBoss WS CXF. > Here is the original issue description: > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated JBWS-3777: --------------------------------- Description: Please port the fix for [CXF-5645|https://issues.apache.org/jira/browse/CXF-5645] to JBoss WS CXF. Here is the original issue description: The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. What I did is as follows (see the attached reproducer for details): # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: {code:xml} <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" wsp:Optional="true" /> <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" wsp:Optional="true" /> </wsp:Policy> ... {code} # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>WS-Addressing is required by this endpoint.</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> {code} [1] In WS-RM Policy 1.1 p.8: {quote} /wsrmp:RMAssertion/@wsp:Optional="true" Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. {quote} was: The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. What I did is as follows (see the attached reproducer for details): # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: {code:xml} <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" wsp:Optional="true" /> <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" wsp:Optional="true" /> </wsp:Policy> ... {code} # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>WS-Addressing is required by this endpoint.</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> {code} [1] In WS-RM Policy 1.1 p.8: {quote} /wsrmp:RMAssertion/@wsp:Optional="true" Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. {quote} > CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL > ---------------------------------------------------------------- > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > Attachments: ws-rm.zip > > > Please port the fix for [CXF-5645|https://issues.apache.org/jira/browse/CXF-5645] to JBoss WS CXF. > Here is the original issue description: > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated JBWS-3777: --------------------------------- Summary: CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL (was: wsp:Optional isn't adhered to for WS-RM policy in WSDL) > CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL > ---------------------------------------------------------------- > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > Attachments: ws-rm.zip > > > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) wsp:Optional isn't adhered to for WS-RM policy in WSDL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWS-3777: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1080321 > wsp:Optional isn't adhered to for WS-RM policy in WSDL > ------------------------------------------------------ > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > Attachments: ws-rm.zip > > > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) wsp:Optional isn't adhered to for WS-RM policy in WSDL

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato edited comment on JBWS-3777 at 3/25/14 3:28 AM: --------------------------------------------------------------- Attached a reproducer project (ws-rm.zip). See {{README.md}} for how to run the project. Note that whether adding {{@RespectBinding}} annotation to the endpoint impl class or not doesn't change the result. You can confirm that by this reproducer. It looks that CXF by default respects the WSDL bindings. was (Author: tadayosi): A reproducer project. See {{README.md}} for how to run the project. Note that whether adding {{@RespectBinding}} annotation to the endpoint impl class or not doesn't change the result. You can confirm that by this reproducer. It looks that CXF by default respects the WSDL bindings. > wsp:Optional isn't adhered to for WS-RM policy in WSDL > ------------------------------------------------------ > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > Attachments: ws-rm.zip > > > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) wsp:Optional isn't adhered to for WS-RM policy in WSDL

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated JBWS-3777: --------------------------------- Attachment: ws-rm.zip A reproducer project. See {{README.md}} for how to run the project. Note that whether adding {{@RespectBinding}} annotation to the endpoint impl class or not doesn't change the result. You can confirm that by this reproducer. It looks that CXF by default respects the WSDL bindings. > wsp:Optional isn't adhered to for WS-RM policy in WSDL > ------------------------------------------------------ > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > Attachments: ws-rm.zip > > > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) wsp:Optional isn't adhered to for WS-RM policy in WSDL

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated JBWS-3777: --------------------------------- Description: The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. What I did is as follows (see the attached reproducer for details): # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: {code:xml} <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" wsp:Optional="true" /> <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" wsp:Optional="true" /> </wsp:Policy> ... {code} # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>WS-Addressing is required by this endpoint.</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> {code} [1] In WS-RM Policy 1.1 p.8: {quote} /wsrmp:RMAssertion/@wsp:Optional="true" Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. {quote} was: The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM. However, my experimentation showed that it actually doesn't. Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. What I did is as follows (see the attached reproducer for details): # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: {code:xml} <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" wsp:Optional="true" /> <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" wsp:Optional="true" /> </wsp:Policy> ... {code} # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>WS-Addressing is required by this endpoint.</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> {code} [1] In WS-RM Policy 1.1 p.8: {quote} /wsrmp:RMAssertion/@wsp:Optional="true" Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. {quote} > wsp:Optional isn't adhered to for WS-RM policy in WSDL > ------------------------------------------------------ > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) wsp:Optional isn't adhered to for WS-RM policy in WSDL

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated JBWS-3777: --------------------------------- Description: The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM. However, my experimentation showed that it actually doesn't. Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. What I did is as follows (see the attached reproducer for details): # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: {code:xml} <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" wsp:Optional="true" /> <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" wsp:Optional="true" /> </wsp:Policy> ... {code} # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>WS-Addressing is required by this endpoint.</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> {code} [1] In WS-RM Policy 1.1 p.8: {quote} /wsrmp:RMAssertion/@wsp:Optional="true" Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. {quote} was: The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM. However, my experimentation showed that it actually doesn't. Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. What I did is as follows (see the attached reproducer for details): # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: {code:xml} <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" wsp:Optional="true" /> <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" wsp:Optional="true" /> </wsp:Policy> ... {code} # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>WS-Addressing is required by this endpoint.</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> {code} [1] In WS-RM Policy 1.1 p.8: {quote} /wsrmp:RMAssertion/@wsp:Optional="true" Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. {quote} > wsp:Optional isn't adhered to for WS-RM policy in WSDL > ------------------------------------------------------ > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM. However, my experimentation showed that it actually doesn't. > Incidentally, I couldn't reproduce the same issue on a bare CXF runtime, so I believe this is purely a JBoss WS issue. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

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 March 2014