maintain, if you do it with UDDI you've got a new problem to deal
with.
On 5/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> Don't pidgeon-hole registry and repository into a system used only for
> discovery.
>
> Registries provide a conduit for multiple runtime systems to share
> management and control information (e.g., policies, SLAs, heuristics, etc).
> Repositories support metadata management, policy management, contract
> management, dependency management, impact analysis, and lots of other
> SDLC/governance activities.
>
> Anne
>
> On 5/22/06, Mark Baker <[EMAIL PROTECTED]> wrote:
> >
> > > This is where a UDDI Registry/Repository comes into its own,
> >
> > Ouch!
> >
> > No, the problem is that if you change implementations and stuff
> > breaks, then you're not loosely coupled. "Become more loosely
> > coupled" is the answer to that problem.
> >
> > If you centralize trivially-decentralizable functionality like
> > discovery to solve a loose coupling problem, then you've now got two
> > problems.
> >
> > Mark.
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
>
>
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
