Frequently Asked Questions

---

---

Q: What is Cosmo and why is OSAF doing this project?

• A: Cosmo is a web application and a content/calendar sharing server to support collaboration with Chandler users. Chandler users will be able to share calendar collections with friends who do not use Chandler, iCal or any other desktop clients by providing them with Cosmo URLs for the collections.
  • Chandler - a desktop PIM client
  • Cosmo - a CalDAV /WebDAV server and a web application way for Chandler users to view their calendars on the web from a browser

Q: Where can I get more information about the Cosmo project?

• A: Take a look at the Cosmo project website http://cosmo.osafoundation.org. (currently being updated)

Q: Can I use Cosmo to create and maintain my on-line calendar?

• A: Someday, but not today! This is intended for developers to get a early look at our code. It is not intended to provide the functionality, features, stability, security, scalability, or user interface necessary for an end-user product.

Q: How do I download Cosmo?

• A: You download the Cosmo server bundle and install them on your server.

Q: Where do I go to look at the Cosmo code?

• A: Build instructions and how to access the Subversion source code repository can be found at: http://wiki.osafoundation.org/bin/view/Projects/ScoobyBuildInstructions

Q: Can I see how Cosmo works without downloading and installing the Cosmo server bundle?

• A: Sure, we've installed the bundle on one of OSAF's servers as a Cosmo demo. Just create an account for yourself, login to Cosmo and try it out.

Q: Is Cosmo open source, and what is the license?

• A: Yes Cosmo like Chandler is open source! The Cosmo server bundle is available under the terms of the Apache Software License, Version 2.0.

Q: How do I submit a patch to Cosmo?

• A: Check out instructions on Patch Life Cycle. It’s currently Chandler specific until we have Cosmo code guidelines written.

---

Q: Wow, the build seems to be downloading a lot of jars. Is that normal?

• A: Yes. Cosmo has a lot of external dependencies. The jars only need to be downloaded the first time you build though, and afterwards only when we update our dependencies.

Q: Where did all those downloaded jars go?

• A: In your local Maven repository at ~/.maven/repository.

Q: Huh? Maven?

• A: http://maven.apache.org

Q: The build fails because Maven can't download one of my jars. What's going on?

• A: A few of our dependencies are not distributed by ibiblio (jta.jar is not indepently distributable, and the jcr/jackrabbit/jcr-server jars are built from source). OSAF hosts a Maven repository containing all of the dependencies. You should make sure your project.properties file contains this:

maven.repo.remote=http://downloads.osafoundation.org/maven/,http://www.ibiblio.org/maven/

and that it is not overridden in your build.properties file.

Q: The build fails with a =NoClassDefFoundError for org/apache/xml/serializer/OutputPropertiesFactory. What's going on?

• A: You forgot to copy serializer.jar from the Xalan distribution into $MAVEN_HOME/lib/endorsed.

Q: Why does Cosmo fail to create the Derby database when being built on Mac OS X?

• A: Because there is a problem with Derby 10.1.1.0 on OS X 10.3 (with JDK 1.4) and OS X 10.4 (with JDK 1.5). The solution to this is documented at the Derby FAQ site. Place your derby.properties file in the top level source directory and, if you dist Cosmo and run it out of that directory, into the top level dist directory.

Note that Apple has issued an update to JDK 1.5 which solves this problem. Also, in 0.2.4 we have updated to Derby 10.1.2.1 which works around the issue as well.

Q: I'm using the server bundle and pointing Tomcat at my cosmo checkout. When i run osafsrvctl start, I see an error like this in osafsrv.log. What gives?

2006-02-28 11:18:10,785 ERROR [[/cosmo]] Error configuring application listener of class org.osaf.cosmo.jackrabbit.query.TextFilterListener
java.lang.ClassNotFoundException: org.osaf.cosmo.jackrabbit.query.TextFilterListener

• A: You probably forgot to run maven war:inplace in your cosmo checkout. Stop Tomcat, build the webapp with that maven command, then restart Tomcat. The error should go away.

-- PriscillaChung - 11 Sep 2006