[jira] Resolved: (GERONIMO-2811) got runtimeexception when processing soap request in doservice2

["Davanum Srinivas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas resolved GERONIMO-2811.
----------------------------------------

    Resolution: Fixed

Nice! fixed in 504879.

thanks,
dims

> got runtimeexception when processing soap request in doservice2
> ---------------------------------------------------------------
>
>                 Key: GERONIMO-2811
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2811
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>         Environment: winxp + sun 1.5
>            Reporter: Lin Sun
>             Fix For: 2.0
>
>         Attachments: G2811.patch
>
>
> Some code change (from Axis2) recently caused the code below to add 2 services to axis configurationcontext.
> configurationContext.getAxisConfiguration().addService(service);
> AxisConfiguration.addService(service) calls AxisConfiguration.addServiceGroup(...) method and inside the 
> addServiceGroup method:
>            if (endpoints.isEmpty()) {
>                 allServices.put(serviceName, axisService);
>             } else if (endpoints.size() == 1) {
>                 // if we have one endpoint, just process it. This is special case as this will be the case
>                 // most of the time
>                 allServices.put(serviceName, axisService);
>                 allServices.put(serviceName + "." + axisService.getEndpointName(), axisService);
> It is putting 2 axisServices there which results services.size() = 2 in in doservice2() call, thus runtimeexception is thrown.
> I haven't been able to identify where the change came from.  It can be they changed the way how wsdlBuilder.populateService() works
> so that endpoints is set to something with the new code while it was empty before.
> The fix is to determine axisservice based on the endpointclassname which seems a more robust way.   I have tested the fix and was able to run .wsdl test with jax-ws test.
> Also was able to run a full build with the latest trunk successfully.:)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.