I note a couple of promises to post on endpoint issues related to matching and serialization. I look forward to these and I'd like to eventually bring the conversation together into a clear statement of what our endpoint/endpointreference lifecycle is. At the moment we have two bites at the cherry. At build time reference target/service resolution and matching happens giving rise to endpoints and endpoint references. The endpoints are added to the registry at activation time and at run time the matching process is completed for references to endpoints running elsewhere in the domain (local endpoint references will already be matched). There are a couple of things we can improve on here.
- make sure we use the same matching algorithm at build and run time - get a better understand of the events that indicate changes in the domain and what the impact on endpoint/endpoint references will be. This is the somewhat abstract model I have in my head at the moment. (EP = endpoint, EPR = endpoint reference) Build ----- for each service binding create EP for each target create EPR (target = reference target or binding uri target or autowire target) Match targeted EPR against EP (*The matching algorithm) for each configured binding create EPR Activate/Start -------------- Add EP to registry Run - Message passes through EPR -------------------------------- If EPR not matched Match EPR against EP (*The matching algorithm) Run - Remove EP from domain --------------------------- Deactivate matching EPRs Run - Add EP to domain ---------------------- Find/create EPRs Match EPR against EP (*The matching algorithm) Deactivate/Stop --------------- Deactive EP Remove EP from regsitry Deactivate EPR (*The matching algorithm) = a comment epr/ep matching algorithm that we don't yet have. It may be advantageous to also consolidate the epr creation step to be driven of a "new ep" event so that the build time and runtime handling of new eps is the same Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
