You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Eric White <ew...@rocksteady.com> on 2002/12/06 21:42:20 UTC
explanation of how "build import" works?
I've got the latest cvs bits and have jetspeed configured against a DB
for PSML storage.
I don't quite understand how "build import" works.
After I load the psml schema and do a "build import" I thought,
operationally, that I'd modify the psml files on disk (e.g.,
.../anon/html/default.psml) and then drop tables and rerun "build
import" to suck in the new psml, but that doesn't seem to be working.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: explanation of how "build import" works?
Posted by David Sean Taylor <da...@bluesunrise.com>.
> -----Original Message-----
> From: Eric White [mailto:ewhite@rocksteady.com]
> 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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: explanation of how "build import" works?
Posted by Eric White <ew...@rocksteady.com>.
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.psmlmanager.Cast
> orPsmlManagerService
> services.PsmlManager.classname=org.apache.jetspeed.services.psmlmanager.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?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: explanation of how "build import" works?
Posted by David Sean Taylor <da...@bluesunrise.com>.
> -----Original Message-----
> From: Eric White [mailto:ewhite@rocksteady.com]
> Sent: Friday, December 06, 2002 12:42 PM
> To: Jetspeed Users List
> Subject: explanation of how "build import" works?
>
>
> I've got the latest cvs bits and have jetspeed configured against a DB
> for PSML storage.
>
> I don't quite understand how "build import" works.
>
> After I load the psml schema and do a "build import" I thought,
> operationally, that I'd modify the psml files on disk (e.g.,
> .../anon/html/default.psml) and then drop tables and rerun "build
> import" to suck in the new psml, but that doesn't seem to be working.
>
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.psmlmanager.Cast
orPsmlManagerService
services.PsmlManager.classname=org.apache.jetspeed.services.psmlmanager.db.D
atabasePsmlManagerService
2. run "ant import"
3. you can then remove the file-based psml, since its now in the database
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>