Thank you Rachana,
   
  So, if I put in the policy field of the service endpoint an address 
indicating where finding the new service endpoint, this field will not be taken 
in account if the EPR becomes invalid?
   
  So, I should add this functionality by my self.
  My question is where should I treat this issue? Is there an intermediate 
entity in the grid which can manage this?
  Or the client it self should do it? In the client code or in the client stub?
   
  Thank you
   
  Soumaya Marzouk


Rachana Ananthakrishnan <[EMAIL PROTECTED]> a écrit :        v\:* 
{behavior:url(#default#VML);}  o\:* {behavior:url(#default#VML);}  w\:* 
{behavior:url(#default#VML);}  .shape {behavior:url(#default#VML);}             
   Hi,
   
  At present we don’t have any default implementations of 
WS-RenewableReference. So if the EPR is invalid because a service address 
changed, the EPR is not usable and there is no automatic way to resolve it in 
the toolkit.
   
  Rachana
   
        
---------------------------------
  
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of soumaya marzouk
Sent: Wednesday, October 24, 2007 6:21 AM
To: [email protected]
Subject: [gt-user] invalid EndPoint Reference

   
    Hi,

    Please, I want to know what happen exactly in gt4 when a service EndPoint 
Reference becomes invalid.

    In other words, how the WS-RenewableReferences and WS-Policy are 
implemented in gt4, and how the client is involved in this?

     

    Thank you

    Soumaya Marzouk

    
    
---------------------------------
  
  Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 




             
---------------------------------
 Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 

Reply via email to