For one thing, we're not UDDI dependant ;-) So although v3 may give some capabilities, it's not a solution. A single registry (whatever the implementation) within an organisation is a single point of failure and something we need to avoid. Hence the reason for federation (or replication) of the service within the architecture and not as a backend implementation choice. The bootstrap process we have in place at the moment would be one of the first places to start, but then you'd need some way of deciding where to go for alternate (and equivalent) replicas of the registry service(s). It would be nice to think that all of this could be hidden behind the client's interface (the JAX-R equivalent of the client stub). To a degree that should be possible. Stateful replication is a hard problem ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024375#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...