Check out the refresh method in the PsmlManagerService interface. If you are using file-based psml (as oppose to the psml stored in DB), the CastorPsmlManagerService class implements this interface. The refresh method will call a getDocument method in the same class and the logic within will get the psml from the file location instead of cache. It will also refresh the psml in the cache at the end. Maybe you can somehow use this method and pass in the ProfileLocator that represents the modified psml. Hope this will give you a jump start. Andy
-----Original Message----- From: Carlos Torres [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 24, 2004 6:03 AM To: Jetspeed Users List Subject: Re: PSML Change in Runtime The screen didn't change after I make the change. I sumit a request to my application and I change the psml file. When the results come back to the screen it must be changed. There is the parameter services.PsmlManager.scanRate=120 in JetspeedResource.properties file. But I must change immediately. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 23, 2004 5:29 PM Subject: RE: PSML Change in Runtime > When you said the screen didn't change, did it change after a few minutes or > after you bounce your container? > The psml can be stored in cache and refreshed periodically depending on the > setup in the JetspeedResource.properties file. > Andy > > -----Original Message----- > From: Carlos Torres [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 23, 2004 1:17 PM > To: Apache JetSpeed User; Apache JetSpeed Dev > Subject: Re: PSML Change in Runtime > > > I tried this way too: > > JetspeedPortletInstance pi = > (JetspeedPortletInstance)getInstance(runData); > Profile profile = pi.getProfile(); > PsmlManagerService exporterService = > (PsmlManagerService)TurbineServices.getInstance().getService("PsmlImportMana > ger"); > PSMLDocument psmlNew = exporterService.getDocument(file_path); > profile.setDocument(psmlNew); > profile.store(); > ((JetspeedRunData)runData).setProfile(profile); > QueryLocator locator = new QueryLocator(QueryLocator.QUERY_USER); > exporterService.refresh(locator); > > and get the same result, the psml file change but the screen no. > > If anybody hava an idea, I thanks a lot. > > > > > ----- Original Message ----- > From: Carlos Torres > To: Apache JetSpeed User ; Apache JetSpeed Dev > Sent: Tuesday, November 23, 2004 2:01 PM > Subject: Re: PSML Change in Runtime > > > I have been changing the psml name file when the new one will be the > default.psml and the old one will be another name. I'm using the methods > after rename the files: > > exporterService.getDocument(locator); > > and after this > > PSMLDocument doc2 = exporterService.refresh(locator); > > where exporterService is a PsmlManagerService object and locator is a > QueryLocator object. > > The code run ok, but the screen configuration doesn't change. Anybody hava > any idea how to "refresh" the screnn and aply the changes? > > Please, help me. > > Thanks. > > > > ----- Original Message ----- > From: Carlos Torres > To: Apache JetSpeed User ; Apache JetSpeed Dev > Sent: Friday, October 22, 2004 2:41 PM > Subject: PSML Change in Runtime > > > Hi people, > > I need to change the PSML file for a type of user(role) in runtime. > According to an action in portal, the panels and portles for the user must > be changed. I will have other PSML files and when the user select an option > it will change with the portal configuration. > > Anybody have any idea to how make this? > > Thank you very much. > > Regards, > > Carlos Alberto Torres > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
