Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Micky Santomax

No help for me ?
-- 
View this message in context: 
http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.



Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Guillaume Nodet
Maybe you could rewrite your question ?
I don't really understand what you want to do.
The URI of the http endoint is usually configured using
the httpLocation attribute of the endpoint...

On 9/14/07, Micky Santomax [EMAIL PROTECTED] wrote:


 No help for me ?
 --
 View this message in context:
 http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738
 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/


Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Gert Vanthienen

Guillaume,

I think this this user has several http consumer endpoints, configured 
at different URIs (e.g. http://0.0.0.0/service1, 
http://0.0.0.0/service2, http://0.0.0.0/service3).  On all of these 
endpoints, the same targetService is configured (ex:Service) and it is 
in this targetService that he would like to distinguish between the 
originating consumer endpoints.


Gert

Guillaume Nodet wrote:

Maybe you could rewrite your question ?
I don't really understand what you want to do.
The URI of the http endoint is usually configured using
the httpLocation attribute of the endpoint...

On 9/14/07, Micky Santomax [EMAIL PROTECTED] wrote:
  

No help for me ?
--
View this message in context:
http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.






  




Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Guillaume Nodet
If this is the case, the consumer endpoint can be accessed on the message
exchange.  IIRC there is also a property that has a unique ID for this
endpoint.
The URI should also be available as a property.

On 9/14/07, Gert Vanthienen [EMAIL PROTECTED] wrote:

 Guillaume,

 I think this this user has several http consumer endpoints, configured
 at different URIs (e.g. http://0.0.0.0/service1,
 http://0.0.0.0/service2, http://0.0.0.0/service3).  On all of these
 endpoints, the same targetService is configured (ex:Service) and it is
 in this targetService that he would like to distinguish between the
 originating consumer endpoints.

 Gert

 Guillaume Nodet wrote:
  Maybe you could rewrite your question ?
  I don't really understand what you want to do.
  The URI of the http endoint is usually configured using
  the httpLocation attribute of the endpoint...
 
  On 9/14/07, Micky Santomax [EMAIL PROTECTED] wrote:
 
  No help for me ?
  --
  View this message in context:
 
 http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738
  Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
 
 
 
 
 
 




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/


Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Guillaume Nodet
The consumer *component* can be retrieved using:

  ((MessageExchangeImpl) exchange).getSourceContext().getComponent()

ServiceMix components also set the following property:

   exchange.getProperty(JbiConstants.SENDER_ENDPOINT)

which returns a string uniquely identifying the endpoint.

I don't really recall where/if the uri is stored...



On 9/14/07, Guillaume Nodet [EMAIL PROTECTED] wrote:

 If this is the case, the consumer endpoint can be accessed on the message
 exchange.  IIRC there is also a property that has a unique ID for this
 endpoint.
 The URI should also be available as a property.

 On 9/14/07, Gert Vanthienen [EMAIL PROTECTED] wrote:
 
  Guillaume,
 
  I think this this user has several http consumer endpoints, configured
  at different URIs (e.g. http://0.0.0.0/service1,
  http://0.0.0.0/service2 , http://0.0.0.0/service3).  On all of these
  endpoints, the same targetService is configured (ex:Service) and it is
  in this targetService that he would like to distinguish between the
  originating consumer endpoints.
 
  Gert
 
  Guillaume Nodet wrote:
   Maybe you could rewrite your question ?
   I don't really understand what you want to do.
   The URI of the http endoint is usually configured using
   the httpLocation attribute of the endpoint...
  
   On 9/14/07, Micky Santomax [EMAIL PROTECTED] wrote:
  
   No help for me ?
   --
   View this message in context:
   http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738
 
   Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
  
  
  
  
  
  
 
 


 --
 Cheers,
 Guillaume Nodet
 
 Blog: http://gnodet.blogspot.com/




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/


Re: How to obtain URI address of http:endpoint ?

2007-09-14 Thread Micky Santomax

Yes this was my case :

  I think this this user has several http consumer endpoints, configured
  at different URIs (e.g. http://0.0.0.0/service1,
  http://0.0.0.0/service2 , http://0.0.0.0/service3).  On all of these
  endpoints, the same targetService is configured (ex:Service) and it is
  in this targetService that he would like to distinguish between the
  originating consumer endpoints.

Thanks to Guillaume for reply which give me the solution
:-)


gnodet wrote:
 
 The consumer *component* can be retrieved using:
 
   ((MessageExchangeImpl) exchange).getSourceContext().getComponent()
 
 ServiceMix components also set the following property:
 
exchange.getProperty(JbiConstants.SENDER_ENDPOINT)
 
 which returns a string uniquely identifying the endpoint.
 
 I don't really recall where/if the uri is stored...
 

-- 
View this message in context: 
http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12679719
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.