[jbossws-issues] [JBoss JIRA] Updated: (JBWS-3175) After calling StubExt.setConfigName a call to StubExt.getConfigName still returns original name

[Darran Lofthouse (JIRA)]

     [ https://jira.jboss.org/browse/JBWS-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse updated JBWS-3175:
-----------------------------------

    Summary: After calling StubExt.setConfigName a call to StubExt.getConfigName still returns original name  (was: Can't change Client Config using StubExt setConfigName)


> After calling StubExt.setConfigName a call to StubExt.getConfigName still returns original name
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBWS-3175
>                 URL: https://jira.jboss.org/browse/JBWS-3175
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: JBoss 5.1.0.GA, Java 6u22, Linux 64bit
>            Reporter: Stephan Heffner
>            Assignee: Darran Lofthouse
>
> After a migration from JBoss 4.2.3.GA to a JBoss 5.1.0.GA environment, one of my WebService clients doesn't work anymore.
> After some research I've seen, that the required selection of the JAXWS Client Config "HTTP 1.0 Client" has no effect:
>                 QName namespace = new QName(namespaceURI, webServiceName);
>                 URL endpoint = new URL(ceWsdl);
>                 sampleService = new SampleServiceService(endpoint, namespace);
>                 externalServicePort = sampleService.getSampleServicePort();
>                 StubExt stubExt = (StubExt) externalServicePort;
>                 stubExt.setConfigName("HTTP 1.0 Client");
>                 log.debug(stubExt.getConfigName());
> Log still contains "Standard Client"
> We used this selection to configure the chunksize to 0 (= disable).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira