portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Watler <wat...@wispertel.net>
Subject latest FileSystemPAM mods
Date Wed, 02 Feb 2005 02:18:47 GMT
Scott,

I am confused by this change to FileSystemPAM:

  @@ -387,6 +387,12 @@
               // save it to the registry
               log.info("Saving the portlet.xml in the registry...");
            
  +            if(registry.namedPortletApplicationExists(app.getName()))
  +            {
  +                log.warn("Deployment has found an app with the application name, "+app.getName()+
  +                        ".  The existing app will be removed in favor of this one.");
  +                undeploy(paWar);
  +            }
               registry.registerPortletApplication(app);
               log.info("Committing registry changes...");


I would like this logic to somehow be moved to the 
DeployPortletAppEventListener instead of bailing out in the middle of a 
registration process here by undeploying. Under what conditions were you 
trying to undeploy here? I do not understand how this could even happen 
unless there were some kind of race condition involved... what am I missing?

I was not able to port this change forward into my version of 
FileSystemPAM. We need to resolve this issue if we need to preserve this 
functionality.

Randy




---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message