Yes, parsing [service-name.endpoint-name] instead of [service-name]
should work fine. I'll stick to that workaround.
Thanks,
Sanka
Deepal Jayasinghe wrote:
Hi Sanka,
We can solve this problem without changing the API (I am bot reluctant
to change the API now) , so I am not going to +1 to this . How about
passing the service name adding the endpoint name then we can just
change the implementation not the API. As I can see you are generating
the EPR with end point as follows
http://abc.com/axis2/services/foo.endpointname
Then you can just pass the service name as "foo.endpointname"
Thanks
Deepal
Hi,
In order to facilitate message dispatching to AxisEndpoints which we
discussed few weeks back[1], any Axis2 transport should be able to
generate service endpoints which adhere the following format.
http://[host]:[port]/axis2/services/[service-name].[endpoint-name]/
This requires the following method addition to TransportListener
interface which enables the AxisEngine to pass targeted AxisEndpoint
name to Transport mechanism so that it can generate a URL which
adhere the above format.
EndpointReference[] getEPRsForService(String serviceName, String
endpointName, String ip) throws AxisFault
Any objections to add that method to TransportListener interface ?
Thanks,
Sanka
[1]
http://www.nabble.com/-Axis2--Dispatching-messages-to-AxisEndpoints-td15587176.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Sanka Samaranayake
WSO2 Inc.
http://sankas.blogspot.com/
http://www.wso2.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
