[Building Sakai] Upgrading sakai from 2.6.1 to 2.8 in jboss 4.0.5.GA

[Steve Swinsburg]

Sakai has a special deployment of the API implementations and Spring wiring in the components directory within Tomcat. You are missing that. Is there any reason you want to use JBoss rather than Tomcat, if you had it running in Tomcat? 

I am unaware of anyone using Sakai within JBoss or how/ if it will even work at all. 

Cheers
Steve


Sent from my iPhone

On 10/11/2011, at 15:27, Gurupriya T <gurupriya_t at amritatech.com> wrote:

> 
> Upgrading sakai from 2.6.1 to 2.8 in jboss 4.0.5.GA
> ---------------------------------------------------
> 
>            Affects Versions: 2.8.0
>            Reporter: GuruPriyaT
>            Priority: Trivial
>            Attachments: serverlog.log
> 
> 
> I am upgrading sakai from 2.6.1 to 2.8 in jboss.
> The sakai src 2.8 with maven build was working fine in tomcat.
> I moved all war files from webapps to jboss/deploy
> and common/lib,server/lib,shared/lib files to jboss/default/lib folder
> I've attached the server log
> The entity broker calls destroy()
> Please help me.
> 
> 
> <serverlog.log>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"