[jboss-dev-forums] [Design of JBoss ESB] - Re: Registry unRegisterService

[mark.little@jboss.com]

I think Kurt can comment more on this subject when he's able, but here's my take. At the moment nothing calls unRegisterService within the ESB because it's a potentially insecure and unsafe thing to do just out of hand, i.e., there needs to be more infrastructure behind this to ensure that one party doesn't take down a service that others are relying on.

The reason for why there is no registerService is probably related to the difference between the notion of a service and the EPRs that actually provide that service. Within JBossESB, a given "logical" service may actually be provided by many different physical services, all of which are identified by EPRs (a single service execution may itself be represented by several different EPRs concurrently). So in effect there is a 1..* mapping between service name/category and EPRs. The way the Registry interface is currently provided, the first EPR that is added for a given name/category will create the service entry in the registry and add that EPR. You can remove EPRs from a service at any point (we make the assumption that this is ok, but again we need to review this later and add in security, e.g., ACLs).

Hopefully you can now see why calling unRegisterService within the ESB is such a big deal: you will remove all of the EPRs from the registry. Since we don't have the necessary hooks (ACLs) in place yet, the best thing to do is punt this to the application at present.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118536#4118536

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118536