[
https://issues.apache.org/jira/browse/AXIS2-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tammo van Lessen resolved AXIS2-5164.
-------------------------------------
Resolution: Invalid
Sorry for a confusion, the Axis2 code is correct. Looks like a missing
setContextPaths on our side. Bug resolved as invalid.
> HTTP endpoint URL calculation does not reflect servicePath parameter
> --------------------------------------------------------------------
>
> Key: AXIS2-5164
> URL: https://issues.apache.org/jira/browse/AXIS2-5164
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.5.5, nightly
> Reporter: Tammo van Lessen
>
> In Apache ODE we use the servicePath parameter to relocate endpoints from
> /services/ to /processes/. I'm currently experimenting with dual channel WS-A
> req/resp operations from an anonymous service client and experience some
> troubles with wrong ReplyTo EPRs in these requests.
> After some debugging, I figures that
> org.apache.axis2.transport.http.HTTPTransportUtils.getEPRsForService(...) is
> only taking the servicePath into account when the HTTP_FRONTEND_HOST_URL
> parameter is present. Interestingly, the EPR generation in the listServices
> Admin JSP returns the correct EPR, which basically prefixes the servicePath
> with HTTP_FRONTEND_HOST_URL. So I think there is bug in getEPRsForService, it
> should always take the servicePath into account, even if the
> HTTP_FRONTEND_HOST_URL is not present. When looking at the code, I assume
> that this bug has been introduced with AXIS2-3843 and is more or less due to
> a wronly places closing brace. Please see [1], Line 336 makes IMO only sense
> if the block is closed after appending the servicePath. Otherwise EPR would
> be always empty.
> [1]
> https://github.com/apache/axis2-java/blob/00c6c019f9fca2f837ef65d5eedf9f56ea089e82/modules/transport/http/src/org/apache/axis2/transport/http/HTTPTransportUtils.java#L333
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]