April 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3773: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1077259|https://bugzilla.redhat.com/show_bug.cgi?id=1077259] from ASSIGNED to MODIFIED > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3773: ----------------------------------------------- Alessio Soldano <asoldano(a)redhat.com> changed the Status of [bug 1077259|https://bugzilla.redhat.com/show_bug.cgi?id=1077259] from NEW to ASSIGNED > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3773: ---------------------------------- Fix Version/s: jbossws-cxf-4.3.1 (was: jbossws-cxf-5.0) > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3787) Upgrade to Apache CXF 2.7.11

by Leandro Kersting de Freitas (JIRA)

Leandro Kersting de Freitas created JBWS-3787: ------------------------------------------------- Summary: Upgrade to Apache CXF 2.7.11 Key: JBWS-3787 URL: https://issues.jboss.org/browse/JBWS-3787 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Leandro Kersting de Freitas Upgrade to Apache CXF 2.7.11. http://cxf.apache.org/cxf-2711-release-notes.html -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3750: -------------------------------- Location of code changes Following the JBossWS custom host and port implementation, org.apache.cxf.transports.http.configuration.HTTPClientPolicy is the location where the new property for custom URI_path should be added. This is a JAXB generated file. The source schema is declared in {http://svn.apache.org/repos/asf/cxf/trunk}/rt/transports/http/src/main/resources/schemas/wsdl/http-conf.xsd The "customized path" substitution is best performed in org.apache.cxf.transport.http.HTTPConduit. references [1] http://www.ietf.org/rfc/rfc2396.txt > Add ability to rewrite path in WSDL URL references > -------------------------------------------------- > > Key: JBWS-3750 > URL: https://issues.jboss.org/browse/JBWS-3750 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > > Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3626) Ability to globally configure SSL settings for JAX-WS clients

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3626?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3626: -------------------------------- This enhancement has some overlap with the upstream task to provide a unified solution across the whole of WildFly 9 / EAP 7: - https://community.jboss.org/wiki/CommonMechanismForSecureSocketDefintions https://issues.jboss.org/browse/WFLY-1136 We should follow this task and contribute as appropriate. > Ability to globally configure SSL settings for JAX-WS clients > ------------------------------------------------------------- > > Key: JBWS-3626 > URL: https://issues.jboss.org/browse/JBWS-3626 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > > Right now, every JAX-WS client that needs to connect to an SSL-enabled endpoint needs to utilize the {{TLSClientParameters}} object from the CXF API library to configure SSL/TLS (unless everything is already configured in the JDK for this particular endpoint). It would be nice if this could be configured globally (perhaps in standalone.xml/domain.xml?) and without CXF-specific APIs needed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3670) Spring declared endpoints, AS components and injection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3670?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3670: ----------------------------------------------- Petr Sakař <psakar(a)redhat.com> changed the Status of [bug 1060001|https://bugzilla.redhat.com/show_bug.cgi?id=1060001] from ON_QA to VERIFIED > Spring declared endpoints, AS components and injection > ------------------------------------------------------ > > Key: JBWS-3670 > URL: https://issues.jboss.org/browse/JBWS-3670 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2.4, jbossws-cxf-4.3 > > > See https://community.jboss.org/message/822796#822796 . Basically the user is trying to declare a WS endpoint using Spring configuration and having other Spring beans injected in it. The problem is the endpoint is actually being created as an AS component later after the spring context has already been built. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3786) @Resource injection not working on handlers attached to JAX-WS clients running in-container

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3786: ------------------------------------- Summary: @Resource injection not working on handlers attached to JAX-WS clients running in-container Key: JBWS-3786 URL: https://issues.jboss.org/browse/JBWS-3786 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3670) Spring declared endpoints, AS components and injection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3670?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3670: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1060001|https://bugzilla.redhat.com/show_bug.cgi?id=1060001] from MODIFIED to ON_QA > Spring declared endpoints, AS components and injection > ------------------------------------------------------ > > Key: JBWS-3670 > URL: https://issues.jboss.org/browse/JBWS-3670 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2.4, jbossws-cxf-4.3 > > > See https://community.jboss.org/message/822796#822796 . Basically the user is trying to declare a WS endpoint using Spring configuration and having other Spring beans injected in it. The problem is the endpoint is actually being created as an AS component later after the spring context has already been built. -- 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, 3 months

1
0
0 / 0

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

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3778?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3778: -------------------------------- I do not believe this is a bug but expected behavior. Section 4.4, Default Sending Algorithm in RFC 1933, "Transition Mechanisms for IPv6 Hosts and Routers" explains the cause of the initial java.net.SocketException that is thrown.[1] Because this is a IPv6 ONLY network the router has no record of any IPv4 addresses, even the multicast address,239.255.255.250 is unknown. The router has algorithms for destination address lookup. When an address can not be resolve, the router must treat it as "unreachable", hence the SocketException. There is no clean solution to this issue because there is no way for an application to know if the network environment in which it is running is a mixed node (IPv4/IPv6) network and the thrown error indicates a true failure in the env or if the app is running in a single node type (IPv6 only nodes or UPv4 only nodes) network and the failure is expected. [4] http://tools.ietf.org/html/rfc1933 > 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 > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > > 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, 3 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 April 2014