Hi,
I'm trying to do certain modifications to Jetspeed. The main requirement we
have is, we want to put .psml/markup information into database. We don't
want all those .psml files lying around in file system. And as number of
users grow, it will just flood the file system.
Here are some of my findings and conclusions:
0. Need to define a database schema, which will allow to store per group/per
role/per user specific .psml information in to database.
1. The current Profiler Manager Service
(org.apache.jetspeed.services.profile.JetspeedProfileManagerService) needs
to be rewritten.
2. The new rewritten class can be plugged into Jetspeed thro' properties
file.
3. Also, org.apache.jetspeed.cache.disk package needs to be modified. It
curently handles remote and local urls. It needs handle the database storage
to get the required information if the newly written Profiler Manager has to
use Disk Cache (which it will now, as we don't want to go to database
everytime user logs in).
Will someone from the Jetspeed development team comment on this, please? Or
is there a plan to incorporate this as a new feature?
Thanks,
-Atul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
