February 2014 - jbossws-issues - Jboss List Archives

[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: ----------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1062697|https://bugzilla.redhat.com/show_bug.cgi?id=1062697] from POST 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3769) Ensure URLConnection inputstreams are properly closed in the testsuite

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3769: ------------------------------------- Summary: Ensure URLConnection inputstreams are properly closed in the testsuite Key: JBWS-3769 URL: https://issues.jboss.org/browse/JBWS-3769 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3758) Investigate better support CDI and Spring

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBWS-3758?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBWS-3758: ------------------------------------- [~jim.ma] have you considered [Snowdrop|http://www.jboss.org/snowdrop]? > Investigate better support CDI and Spring > ----------------------------------------- > > Key: JBWS-3758 > URL: https://issues.jboss.org/browse/JBWS-3758 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.4 > > > Look at how to remove the spring check in the org.jboss.as.webservices.invocation.AbstractInvocationHandler and avoid initialize endpoint implementation for several times. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3758) Investigate better support CDI and Spring

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3758?page=com.atlassian.jira.plugin.... ] Jim Ma edited comment on JBWS-3758 at 2/27/14 4:48 AM: ------------------------------------------------------- After more investigation and looked at code change for JBWS-3441, it looks the spring integration check can't be skipped. Another approach resolved JBWS-3670 could be check the spring integration and register another interceptor to put the reference contains spring injected bean for future invocation. This is actually the same way to fix JBWS-3441, and current fix is even simpler than the interceptor way. So I am keeping this as it now and mark this issue to won't fix. was (Author: jim.ma): After more investigation and looked at code change for JBWS-3441, it looks the spring integration check can't be skipped. Another approach resolved JBWS-3670 could be check the spring integration and register another interceptor to put the reference contains spring injected bean for future invocation. This is actually the same way to fix JBWS-3441, and current fix is even simpler than the interceptor way. So I am keeping this as it now and mark this issue to resolved. > Investigate better support CDI and Spring > ----------------------------------------- > > Key: JBWS-3758 > URL: https://issues.jboss.org/browse/JBWS-3758 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.4 > > > Look at how to remove the spring check in the org.jboss.as.webservices.invocation.AbstractInvocationHandler and avoid initialize endpoint implementation for several times. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3758) Investigate better support CDI and Spring

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3758?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3758: ------------------------------ After more investigation and looked at code change for JBWS-3441, it looks the spring integration check can't be skipped. Another approach resolved JBWS-3670 could be check the spring integration and register another interceptor to put the reference contains spring injected bean for future invocation. This is actually the same way to fix JBWS-3441, and current fix is even simpler than the interceptor way. So I am keeping this as it now and mark this issue to resolved. > Investigate better support CDI and Spring > ----------------------------------------- > > Key: JBWS-3758 > URL: https://issues.jboss.org/browse/JBWS-3758 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.4 > > > Look at how to remove the spring check in the org.jboss.as.webservices.invocation.AbstractInvocationHandler and avoid initialize endpoint implementation for several times. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3768) Fix issues with CXF Conduit re-use and tests modifying client conduits

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3768: ------------------------------------- Summary: Fix issues with CXF Conduit re-use and tests modifying client conduits Key: JBWS-3768 URL: https://issues.jboss.org/browse/JBWS-3768 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 We have some tests that are modifying the HTTPConduit on client side; in those cases a separate bus needs to be used, as the conduit is linked to the bus (one conduit per protocol) which in turn is linked to the current thread. So any test running later on the same thread and not creating a new bus will eventually re-use the conduit, which would still have the setup for the previous test. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3767) Implement JASPIC SOAP profile

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3767?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3767: ---------------------------------- Summary: Implement JASPIC SOAP profile (was: Implement the jsapic soap profile) > Implement JASPIC SOAP profile > ----------------------------- > > Key: JBWS-3767 > URL: https://issues.jboss.org/browse/JBWS-3767 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.3 > > > Implement JSR-196 JASPIC 1.1 soap profile -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3721) UDP endpoint failure in pure IPv6 environment

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3721?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3721: --------------------------------------- [~psakar] yep, feel free to commit the change to the testcase :-) > UDP endpoint failure in pure IPv6 environment > --------------------------------------------- > > Key: JBWS-3721 > URL: https://issues.jboss.org/browse/JBWS-3721 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-4.2.1 > Environment: pure IPv6 network with IPv4 disabled > Reporter: Petr Sakař > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.3 > > > UDPEndpointAPITestCase.testClientSide fails with connection timeout. > if the following lines are changed from > {code} > Endpoint ep = Endpoint.publish("soap.udp://:9436", implementor); > ... > service.addPort(udpPortName, "http://schemas.xmlsoap.org/soap/", "soap.udp://:9436"); > {code} > to > {code} > Endpoint ep = Endpoint.publish("soap.udp://[::1]:9436", implementor); > ... > service.addPort(udpPortName, "http://schemas.xmlsoap.org/soap/", "soap.udp://[::1]:9436"); > {code} > test passes. > I did not inspect if both addresses has to be changed or only one suffice -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3721) UDP endpoint failure in pure IPv6 environment

by Petr Sakař (JIRA)

[ https://issues.jboss.org/browse/JBWS-3721?page=com.atlassian.jira.plugin.... ] Petr Sakař commented on JBWS-3721: ---------------------------------- Would it be possible to rewrite methon isProperNetworkSetup in a little bit more readable form ? {CODE} private boolean isProperNetworkSetup() throws Exception { Enumeration<NetworkInterface> interfaces = NetworkInterface.getNetworkInterfaces(); while (interfaces.hasMoreElements()) { NetworkInterface networkInterface = interfaces.nextElement(); if (networkInterface.isUp() && !networkInterface.isLoopback() && isBroadcastAddressAvailable(networkInterface)) { return true; } } return false; } {CODE} > UDP endpoint failure in pure IPv6 environment > --------------------------------------------- > > Key: JBWS-3721 > URL: https://issues.jboss.org/browse/JBWS-3721 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-4.2.1 > Environment: pure IPv6 network with IPv4 disabled > Reporter: Petr Sakař > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.3 > > > UDPEndpointAPITestCase.testClientSide fails with connection timeout. > if the following lines are changed from > {code} > Endpoint ep = Endpoint.publish("soap.udp://:9436", implementor); > ... > service.addPort(udpPortName, "http://schemas.xmlsoap.org/soap/", "soap.udp://:9436"); > {code} > to > {code} > Endpoint ep = Endpoint.publish("soap.udp://[::1]:9436", implementor); > ... > service.addPort(udpPortName, "http://schemas.xmlsoap.org/soap/", "soap.udp://[::1]:9436"); > {code} > test passes. > I did not inspect if both addresses has to be changed or only one suffice -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3767) Implement the jsapic soap profile

by Jim Ma (JIRA)

Jim Ma created JBWS-3767: ---------------------------- Summary: Implement the jsapic soap profile Key: JBWS-3767 URL: https://issues.jboss.org/browse/JBWS-3767 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.2 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.3 Implement JSR-196 JASPIC 1.1 soap profile -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2014