> -----Original Message----- > From: Eric White [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 06, 2002 1:18 PM > To: Jetspeed Users List > Subject: RE: explanation of how "build import" works? > > > On Fri, 2002-12-06 at 14:57, David Sean Taylor wrote: > > > > > Hi Eric, > > > > You should only need to run it once to get the initial files > off the disk > > and into the db. > > > > The steps are: > > > > 1. change the PSML service properties > > > > # > > > services.PsmlManager.classname=org.apache.jetspeed.services.psmlma > nager.Cast > > orPsmlManagerService > > > services.PsmlManager.classname=org.apache.jetspeed.services.psmlma > nager.db.D > > atabasePsmlManagerService > > > > 2. run "ant import" > > > > 3. you can then remove the file-based psml, since its now in > the database > > > > > > So, I guess this approach assumes any future changes I make to the PSML > files will be through the customizer? i.e., even if I wanted to make a > file-based change, I should use the customizer to import? > There are options. The first parameter passed to the importer can be "true" or "false", default "true". The parameter determines if an import has been run before on this database. If true, the importer performs the safety check and will not import over a previously imported database. By passing in false, you are telling "don't check, just run".
You can also import from the PSMLBrowser into a live system. Or you can write your own PSML Manager to handle things specifically to your needs. For instance, I wrote a PSMLManager service that stores read-only profiles on the file system, and user profiles in the database. David -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
