[Deploying Sakai] Sakai fails to load.

Steve Swinsburg steve.swinsburg at gmail.com
Tue Jan 21 15:25:08 PST 2014

Cool. All of that was from memory and written hasty, glad you could
decipher it :)

The component directory is a special area of Sakai that holds the API
implementation code. Spring knows to look here to find the classes. This is
so that individual web apps can communicate with each other via the API.

There was a post by Zach a while back about the specific issues with the
distributed versions of Tomcat. I don't think this is ever going to change
though since it is so specific so the go is to just use the archived
distributions rather than the packages.

On Wed, Jan 22, 2014 at 9:25 AM, Gesh hseG <gesh at gesh.uni.cx> wrote:

> Did what you said, with a few changes:
> - In step 4, I checked out https://source.sakaiproject.org/svn/sakai/trunk,
> as the link you provided was not a maven project.
> - In step 8, I passed ../logs/catalina.out to tail. Again, I suspect you
> missed a component.
> - Since tomcat was complaining about a lack of memory, I created the
> setenv.sh file as directed in step 5.7
> Apart from that, it works!
> Thank you very much. I can't begin to express the relief that this is
> finally over.
> Gesh.
> P.S. Why won't the distributed version of tomcat work with Sakai?
>      That is to say, why does Sakai depend on having the components
> directory
>      and why aren't there instructions in the wiki explaining how to
> reverse the patching
>      done by distributions that breaks the components directory?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20140122/d1beb0a0/attachment.html 

More information about the production mailing list