From: <ste...@jb...> - 2005-07-28 17:53:42
|
One other thing that has to happen if we do go down this path: we need to add .har as a standard recognized archive extension, so that we don't leave existing users out-to-dry. There have been numerous discussions about attaching listeners/aspects to service lifecycle. A long time ago, one such discussion was to also remove the need for a HARDeployer by simply having a generic way for services to "know about" there deployment url. What ever happened with those discussions? Personally, I think that is a more viable approach simply because it does allow this ability to still have multiple session factories defined within a single deployment (provided each is within it own nested deployment bundle). Short-term couldn't we just introduce an interface like: | public interface DeploymentURLAware { | public void setDeploymentUrl(URL deploymentURL); | } | which services could optionally implement to be notified about its deployment url? The question of course is what is responsible for notifying such mbeans. ServiceConfigurator seems the logical choice but it, unfortunately, knows nothing about DeploymentInfo or deployment urls. Guess it could be done in SubDeployerSupport.create(DI). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887118#3887118 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887118 |