[jbossws-issues] [JBoss JIRA] (JBWS-3819) Allow parametrization of web connector created within TS execution
Alessio Soldano (JIRA)
issues at jboss.org
Thu Oct 16 11:09:35 EDT 2014
[ https://issues.jboss.org/browse/JBWS-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated JBWS-3819:
----------------------------------
Fix Version/s: jbossws-cxf-4.3.2
> Allow parametrization of web connector created within TS execution
> ------------------------------------------------------------------
>
> Key: JBWS-3819
> URL: https://issues.jboss.org/browse/JBWS-3819
> Project: JBoss Web Services
> Issue Type: Feature Request
> Components: jbossws-cxf, jbossws-integration
> Affects Versions: jbossws-cxf-4.3
> Environment: EAP 6.3.0 (jbossws-cxf-4.3.0.Final-redhat-3, jbossweb-7.4.8.Final-redhat-4)
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Priority: Minor
> Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0
>
> Attachments: patch.diff
>
>
> During execution of TS there is new 'https' connector created for several testcases. This connector has hardcoded protocol value {{HTTP/1.1}} which means use JIO conector (org.apache.coyote.http11.Http11Protocol), this is done in [https://source.jboss.org/browse/JBossWS/container/jboss72/tags/jbossws-jboss720-4.3.0.Final/tests-integration/src/main/java/org/jboss/as/webservices/deployer/RemoteDeployer.java?r=18419#to273]
> If we want to test with NIO connector enabled (org.apache.coyote.http11.Http11NioProtocol), we can do it only by changing already existing connectors before TS execution, but not for the new ones created during execution.
> The simple solution here is to allow overriding connector protocol class by system property.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbossws-issues
mailing list