[
https://issues.apache.org/jira/browse/GERONIMO-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465962
]
Lasantha Ranaweera commented on GERONIMO-2752:
----------------------------------------------
Please use the patch3 for the reviewing. It will resolve some NPE some of URL
requests additionally.
Lin,
The major difference between latest approach and previous one is the way it
calculates 'serviceName' parameter and taking out AxisService from list of
services.
In previous approach we are calculating 'serviceName' out of URL request and
tried to use it as our 'serviceName'. It is correct for the Axis2 related
service access but not for JAXWS since we are giving servlet URL to the access
services. This is not the name given to the AxisService in the services HashMap.
Latest approach I am directly take the serviceName out list of services
HashMap. The way our implementation work for each service in the
webservices.xml file it will create different Axis2WebServiceContainer object.
So the list of services in the ConfigurationContext won't exceed 1 and we can
take Axis2Service without any problem.
Dims please correct me if I am wrong here :-).
thanks,
Lasantha
> Axis2 integration displays invalid information for URL requests
> ---------------------------------------------------------------
>
> Key: GERONIMO-2752
> URL: https://issues.apache.org/jira/browse/GERONIMO-2752
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.0-M1
> Reporter: Lasantha Ranaweera
> Attachments: GERONIMO-2752.patch1, GERONIMO-2752.patch2,
> GERONIMO-2752.patch3
>
>
> Current integration of Axis2 gives wrong information to the wsdl, wsdl2, xsd=
> .. etc URL requests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
