[Building Sakai] sakai stable version and where do we get please suggest.

Thu Oct 1 00:53:43 PDT 2009

Here is the info about persistence (ie database) in Sakai:

http://confluence.sakaiproject.org/display/BOOT/Persistence

You can use Hibernate or JDBC. Take a look at the source of a CRUD  
tool generated from the Sakai App Builder:
http://confluence.sakaiproject.org/display/BOOT/Sakai+App+Builder

It will show you how the DAO works.

Steve

On 01/10/2009, at 5:43 PM, Ravinder Kankanala wrote:

> Hi Steve,
>
> In our sakai project, how we are achieving database connection  
> management.
>
> Here what I understood, We are mentioning all the database related  
> properties in sakai.properties file.
>
> But through in java classes how we are implementing I couldn't get  
> flow from DAO layer to database layer whether we are using Hibernate  
> session factory or JDBC or Spring.
>
> Actually we need to implement multitenant feature in sakai project,  
> could you please suggest on this.
>
> Thanks,
> Ravinder
>
>
>
> -----Original Message-----
> From: Steve Swinsburg [mailto:steve.swinsburg at gmail.com]
> Sent: Thursday, October 01, 2009 11:38 AM
> To: Ravinder Kankanala
> Cc: sakai-dev at collab.sakaiproject.org Developers
> Subject: Re: sakai stable version and where do we get please suggest.
>
> The version you build against varies depending on your local needs. If
> you already have a Sakai instance, build against a version that
> matches that so that you know the app will work. If not, build against
> trunk or at least 2.6.x
>
> Check out section 16 onwards on this page:
> http://confluence.sakaiproject.org/display/BOOT/Development+Environment+Setup+Walkthrough
>
> That will get you setup with your source code in eclipse and
> classpaths setup nicely.
>
> I've found that when importing, best to use File > Import > General >
> Maven Projects
>
> There is info about attaching debuggers in the Programmers Cafe
> section, ie BOOT in Confluence.
>
> cheers,
> Steve
>
>
>
> On 01/10/2009, at 3:14 PM, Ravinder Kankanala wrote:
>
>> Hi Steve,
>>
>> Can you please suggest which sakai version to take build and deploy
>> the application.
>>
>> And also we are unable to debug the application and also how can I
>> set the class path for sakai project because for this project in
>> eclipse it doesn't showing build path option when right click on
>> project.
>>
>> Thanks,
>> Ravinder k
>>
>>
>>
>> -----Original Message-----
>> From: Steve Swinsburg [mailto:steve.swinsburg at gmail.com]
>> Sent: Friday, September 25, 2009 4:41 PM
>> To: Ravinder Kankanala
>> Cc: organic.ishtiaq at gmail.com; production at collab.sakaiproject.org; sakai-dev at collab.sakaiproject.org
>> Developers
>> Subject: Re: [Building Sakai] Step by Step Guide for request flow
>> from UI to backend(Database)
>>
>> Have a look here:
>>
>> http://confluence.sakaiproject.org/display/BOOT/Sakai+application+%28tool%29+structure
>>
>> There is a diagram that shows the general layout of how a tools  
>> works.
>> You'll need to understand things like what a DAO does, what goes in
>> the Logic, and what a Model is etc.
>>
>> In a nutshell, there is a webapp which has a frontend (the
>> presentation layer) and a set of services (the API/Impl bundle) which
>> take care of the persistence (generally via Hibernate or JDBC). This
>> service also has access to the other Sakai API's from the core
>> services and other tools. Likewise, the services from your tool can  
>> be
>> accessed by other tools (if you code it nicely ;)
>>
>> You can install the Sakai App Builder plugin into Eclipse, and
>> generate a basic Sample App which has everything you examine and
>> learn. There are some conventions you'll need to follow to register
>> new tools and to make sure your jars are deployed to the right spot  
>> in
>> your app server. For the presentation layer, may I suggest Apache
>> Wicket pas thats been added/updated in the app builder recently.
>>
>> Best of luck,
>>
>> Steve
>>
>>
>> On 25/09/2009, at 8:52 PM, Ravinder Kankanala wrote:
>>
>>> Hi Team,
>>>
>>> In sakai project, we are unable to understand the code structure,
>>> means request flow from front-end to back-end(Database layer).
>>>
>>> Please at least explain for one tool how it will be working for UI
>>> to Back end(DB) and also please let me know sakai complete technical
>>> architecture diagram at least we can know how request will goes from
>>> one layer to another layer.
>>>
>>> Please explain initial request call in the application.
>>>
>>> And also we are unable to set the build path for sakai project.
>>>
>>>
>>> Thanks,
>>> Ravinder
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org
>>> ] On Behalf Of Steve Swinsburg
>>> Sent: Friday, September 25, 2009 4:09 PM
>>> To: organic.ishtiaq at gmail.com
>>> Cc: production at collab.sakaiproject.org; swinsb2 at une.edu.au; sakai-dev at collab.sakaiproject.org
>>> Subject: Re: [Building Sakai] LDAP Integration Step by Step Guide
>>>
>>> Hi,
>>>
>>> Here's one I prepared earlier:
>>>
>>> http://confluence.sakaiproject.org/display/~steve.swinsburg/LDAP+in
>>> +Sakai+2.5
>>>
>>> cheers,
>>> Steve
>>>
>>> On 25/09/2009, at 8:18 PM, Ishtiaq Ahmad wrote:
>>>
>>>> Need a step by step guide for integrating Sakai with LDAP in 2.5.x.
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Ishtiaq Ahmad
>>>
>>> _______________________________________________
>>> 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"
>>>
>>> DISCLAIMER
>>> ==========
>>> This e-mail may contain privileged and confidential information
>>> which is the property of Persistent Systems Ltd. It is intended only
>>> for the use of the individual or entity to which it is addressed. If
>>> you are not the intended recipient, you are not authorized to read,
>>> retain, copy, print, distribute or use this message. If you have
>>> received this communication in error, please notify the sender and
>>> delete all copies of this message. Persistent Systems Ltd. does not
>>> accept any liability for virus infected mails.
>>
>>
>> DISCLAIMER
>> ==========
>> This e-mail may contain privileged and confidential information
>> which is the property of Persistent Systems Ltd. It is intended only
>> for the use of the individual or entity to which it is addressed. If
>> you are not the intended recipient, you are not authorized to read,
>> retain, copy, print, distribute or use this message. If you have
>> received this communication in error, please notify the sender and
>> delete all copies of this message. Persistent Systems Ltd. does not
>> accept any liability for virus infected mails.
>
>
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information  
> which is the property of Persistent Systems Ltd. It is intended only  
> for the use of the individual or entity to which it is addressed. If  
> you are not the intended recipient, you are not authorized to read,  
> retain, copy, print, distribute or use this message. If you have  
> received this communication in error, please notify the sender and  
> delete all copies of this message. Persistent Systems Ltd. does not  
> accept any liability for virus infected mails.