[Deploying Sakai] [Building Sakai] Step by Step Guide for request flow from UI to backend(Database)
steve.swinsburg at gmail.com
Fri Oct 9 02:18:32 PDT 2009
You can either setup the dependencies in the classpath manually to
point to the jars in your M2 repo, or quit eclipse and run:
mvn eclipse:clean eclipse:eclipse -DdownloadJavadocs=true
to regenerate all the Eclipse project files.
Then import again. But to be honest, you don't need the whole source
in Eclipse. What are you trying to do? Build a tool?
You can attach debuggers to a running Tomcat:
On 09/10/2009, at 6:21 PM, Ravinder Kankanala wrote:
> Hi steve,
> I have configured the project in eclipse but I could n't able to set
> the buildpath in eclipse.
> And also I need to debug the sakai application.
> In eclipse there is no chance to go dependency of one java class to
> another class due to buildpath was not configured.
> Even some classes I couldn't find in eclipse through <ctrl><shift>R.
> Please send me the detailed solution for the same.
> -----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
> Subject: Re: [Building Sakai] Step by Step Guide for request flow
> from UI to backend(Database)
> Have a look here:
> 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,
> 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.
>> -----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
>> Here's one I prepared earlier:
>> 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.
>>> Ishtiaq Ahmad
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
>> 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.
> 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.
More information about the production