Hi Mike, I don't currently have any documentation put together on using the persistence plug in standalone. I should have some time this weekend to put together a how-to on using the persistence plug in a standalone application.
I the mean time, you can checkout J2 from the CVS, you can start looking at the code under plugin/src. You can also look in portal/src/webapp/WEB-INF/conf/jetspeed.properties to see how the service is configured. Look at portal/src/webapp/WEB-INF/conf/persistence-plugins.xml on how to define a plugin instance(s). portal/src/webapp/WEB-INF/conf/ojb contains all the standard OJB information for the OJB-based plguins. hth, *===================================* * Scott T Weaver������������������� * * Jakarta Jetspeed Portal Project�� * * [EMAIL PROTECTED] * *===================================* � > -----Original Message----- > From: Trinka, Mike R [mailto:[EMAIL PROTECTED] > Sent: Friday, September 19, 2003 11:34 AM > To: 'Jetspeed Users List' > Subject: Persistence plugin > > Hi all, I have been extremely impressed with Jetspeed's malleability so > far. > It seems that every modification is very easy to implement, but now I am > stumped, so here goes: > > I have set up Jetspeed to use an Oracle database, and everything seems to > be > working. However, I would like to get away from using a blob to store the > psml. I know that Jetspeed 2 will use a persistence plugin to allow this, > but I also read on the dev list that the persistence plugin can be used in > a > Jetspeed 1 project, because it can be a standalone thing. Is there a list > of things that need to be changed to implement this? If so, where? > > I originally thought that a re-write of DatabasePsmlManagerService would > be > necessary, but this has me hoping otherwise. I have a need to implement > this before the end of the year, and I will want to migrate to Jetspeed 2 > when it is ready, so I would like to make the transition as painless as > possible. I figured this would accomplish both goals, if it is possible. > > Any hints or guidance or points in the right direction would be helpful. > Thanks. > > -Mike Trinka > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
