I believe that the kernel, roles, and stores are needed. The jdom and webdav servlet jars are for the webdav side of the world, iir. I might be wrong, but this should be a good start to see it all work properly. One thing that I found out: there is not API abstraction right now to allow you to deploy the kernel as, say, and mbean and talk to it over a transport. Thus, you will either need to package these jars, the Domain.xml, and the properties file (if you need it for customizations) into your .war or .ear that you deploy, copy them to a shared classpath on for your server (like a /lib or /serverclasses kinda thing), or make sure its in the main classloader for your standalone application.
HTH, James > -----Original Message----- > From: Tarkenton, Daniel S. [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 05, 2003 6:13 PM > To: '[EMAIL PROTECTED]' > Subject: Low level slide api > > > I am trying to use the slide api (version 1.0.16) as the > actual content mgmt component of my component based > application. Meaning that I do not need the webdav portion > of the slide api. Basically, I need to know which jar files > from the [slide home]/slide/lib directory I would need to > bundle into my application lib directory so that I may use > slide as my content repository. > > thanks in advance, > dan > > --------------------------------------------------------------------- > 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]
