April 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3903) Automatic / dynamic test port selection

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3903: ------------------------------------- Summary: Automatic / dynamic test port selection Key: JBWS-3903 URL: https://issues.jboss.org/browse/JBWS-3903 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf, productization Reporter: Alessio Soldano Fix For: jbossws-cxf-5.1 Jan writes: {quote}I think it would be nice to have some notes about ports used for testsuite run, because after move to arquillian there are many more ports used now. Something like that because there are several different configuration being started, you need all "offsetted" ports to be free. Reference for basic container ports: https://docs.jboss.org/author/display/WFLY8/Admin+Guide#AdminGuide-Interf... Current offsets: <port-offset.cxf-tests.jboss>0</port-offset.cxf-tests.jboss> <port-offset.cxf-tests.ssl-mutual-auth>5000</port-offset.cxf-tests.ssl-mutual-auth> <port-offset.cxf-tests.default-config-tests>10000</port-offset.cxf-tests.default-config-tests> <port-offset.cxf-tests.jms>35000</port-offset.cxf-tests.jms> <port-offset.shared-tests.jboss>15000</port-offset.shared-tests.jboss> <port-offset.shared-tests.default-config-tests>20000</port-offset.shared-tests.default-config-tests> <port-offset.shared-tests.address-rewrite>25000</port-offset.shared-tests.address-rewrite> <port-offset.cxf-spring-tests.jboss>30000</port-offset.cxf-spring-tests.jboss> And there are some special cases: - org.jboss.test.ws.jaxws.endpoint.EndpointTestCase -- where hardcoded 8081 port is used - org.jboss.test.ws.jaxws.cxf.udp.UDPEndpointAPITestCase -- hardcoded 9436 - org.jboss.wsf.stack.cxf.addons.transports.udp.UDPTransportTest -- hardcoded 9434 - org.jboss.test.ws.jaxws.samples.wsdd.WSDiscoveryTestCase -- 3072 port by WS-Discovery specification {quote} We should have something like the port utilities in org.apache.cxf.testutil.common.TestUtil (except that's not thread safe, while we need it to be thread safe to let the testsuite run with -Pfast profile). The idea is that we could have an "ofsetted" range of ports "reserved" for the JBossWS testsuite. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3901: --------------------------------------- ok, fine. We can still add stuff later (or if anybody comments here before release). > Allow configuring default HTTP Conduit > -------------------------------------- > > Key: JBWS-3901 > URL: https://issues.jboss.org/browse/JBWS-3901 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. > We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's built using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on JBWS-3901: ----------------------------------------- If there is no demand, we should keep current set of attributes. > Allow configuring default HTTP Conduit > -------------------------------------- > > Key: JBWS-3901 > URL: https://issues.jboss.org/browse/JBWS-3901 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. > We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's built using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3902) Missing cxf-xjc-runtime.jar artifact

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3902?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3902: ---------------------------------- Forum Reference: https://developer.jboss.org/message/923495?et=watches.email.thread#923495 > Missing cxf-xjc-runtime.jar artifact > ------------------------------------ > > Key: JBWS-3902 > URL: https://issues.jboss.org/browse/JBWS-3902 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > cxf-xjc-runtime is missing from both Maven dependencies and distribution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3902) Missing cxf-xjc-runtime.jar artifact

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3902: ------------------------------------- Summary: Missing cxf-xjc-runtime.jar artifact Key: JBWS-3902 URL: https://issues.jboss.org/browse/JBWS-3902 Project: JBoss Web Services Issue Type: Bug Reporter: Alessio Soldano Assignee: Alessio Soldano cxf-xjc-runtime is missing from both Maven dependencies and distribution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3901: --------------------------------------- If you believe that's going to be used quite often, I can add it to the set of attributes we expose thorugh system properties. I didn't include it so far as I can't remember remember of any users of ours that explicitly asked about it (while many asked about those I already included). Just let me know. > Allow configuring default HTTP Conduit > -------------------------------------- > > Key: JBWS-3901 > URL: https://issues.jboss.org/browse/JBWS-3901 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. > We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's built using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on JBWS-3901: ----------------------------------------- I was looking at http://cxf.apache.org/docs/client-http-transport-including-ssl-support.ht... and one more attribute caught my attention - AutoRedirect (Specifies if the client will automatically follow a server issued redirection. The default is false.). Can't say how often it is used in cxf community. > Allow configuring default HTTP Conduit > -------------------------------------- > > Key: JBWS-3901 > URL: https://issues.jboss.org/browse/JBWS-3901 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. > We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's built using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3901: ---------------------------------- Description: With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's built using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. was: With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's build using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. Moreover, we could use the usual Service API (META-INF/services/org.jboss.ws.cxf.transport.http.HTTPConduitFactoryWrapper or such) for resolving optional user provided conduit factory wrappers, to override the default behaviour. > Allow configuring default HTTP Conduit > -------------------------------------- > > Key: JBWS-3901 > URL: https://issues.jboss.org/browse/JBWS-3901 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. > We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's built using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3901: --------------------------------------- Note: this will require an entry in the migration guide as the org.jboss.security.ignoreHttpsHost property is not used by jbossws-cxf anymore, while cxf.tls-client.disableCNCheck is used instead. > Allow configuring default HTTP Conduit > -------------------------------------- > > Key: JBWS-3901 > URL: https://issues.jboss.org/browse/JBWS-3901 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. > We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's build using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. > Moreover, we could use the usual Service API (META-INF/services/org.jboss.ws.cxf.transport.http.HTTPConduitFactoryWrapper or such) for resolving optional user provided conduit factory wrappers, to override the default behaviour. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3901: ---------------------------------- Description: With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's build using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. Moreover, we could use the usual Service API (META-INF/services/org.jboss.ws.cxf.transport.http.HTTPConduitFactoryWrapper or such) for resolving optional user provided conduit factory wrappers, to override the default behaviour. was: With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. We could have a custom implementation of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's build using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. Moreover, we could use the usual Service API (META-INF/services/org.apache.cxf.transport.http.HTTPConduitFactory) for resolving optional user provided conduit factories, to override the default behaviour. > Allow configuring default HTTP Conduit > -------------------------------------- > > Key: JBWS-3901 > URL: https://issues.jboss.org/browse/JBWS-3901 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options. > We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's build using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties. > Moreover, we could use the usual Service API (META-INF/services/org.jboss.ws.cxf.transport.http.HTTPConduitFactoryWrapper or such) for resolving optional user provided conduit factory wrappers, to override the default behaviour. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

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 2015