Server Side Issues

Since there are so many different server options, and we expect to work on all of them, it will be useful to collect any gotcha’s we come across here.

Apache on OS X

When working on the Cappuccino frameworks you will need to compile them after each change, so it is convenient to symlink your test project’s “Frameworks” directory to $CAPP_BUILD/Release (assuming you have set up the tools and $CAPP_BUILD environment variable):

cd /path/to/testproject
ln -s $CAPP_BUILD/Release Frameworks

You can either load the sample project directly from the filesystem (file://path/to/testproject/index.html) or put it in your Sites directory and load it via Web Sharing (apache webserver). For the latter you must enable symlink following in Apache. See the following blog post:

Mac OS X, Web Sharing / Apache, and Symlinks

Microsoft IIS7

Apparently IIS (at least 7, maybe others), needs to have the mime type of file types it doesn’t understand set to something for Cappuccino to work. Specifically, you should set the following mime-type/extension pairs:

text/javascript for ".j"
text/xml for ".plist" and 
text/javascript for ".sj"

Glassfish

You need to have the mime type of file types it doesn’t understand set to something for Cappuccino to work. Specifically, you should set the following mime-type/extension pairs. This can be done in the web.xml:

<mime-mapping>
     <extension>j</extension>
     <mime-type>text/javascript</mime-type>
</mime-mapping>
<mime-mapping>
     <extension>plist</extension>
     <mime-type>text/xml</mime-type>
</mime-mapping>
<mime-mapping>
      <extension>sj</extension>
      <mime-type>text/javascript</mime-type>
</mime-mapping>