Like Mark had mentioned, the Beta release did not give much of an insight to the registry design. So now we need to start looking into that. The idea initially was to have a standalone custom regsitry that can be deployed on multiple machines to prevent single point of failure. Moreover the registry should be independent of a specific implementation like UDDI. Now based on the JBossWS project we decided to initially design with jUDDI and later move on to our custom regsirty. Now the problem with jUDDI is that it is WS based, so we would need to have an application server where we deployed the registry. This is something that we had planned to avoid since the registry should be essentially stand alone. I have been going thru the jUDDI code and I came to realise that along with builiding our custom listener for the requests, we may need to plugins for the aspects of security and authentication. For starters however we can get the current Code bound with jUDDI. Please let me know your thoughts on this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965754#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...