[Building Sakai] [Building Sak ai] New component-newdep endency-Please help!

[Nuno Fernandes]

Mak,

> The suggestion for creating a new implementation for SiteService did not
> work out. I created a new class which extends DbSiteService (the previous
> implementation of SiteService) and implemented only the modified methods in
> it. I also changed the components.xml file and changed the bean-class
> attribute to my new new name.
>

I think the default implementation is BaseSiteService and not DbSiteService
- this may be the cause of your failure. Also, this is the recommended way
of changing core services behavior: inject our custom implementation that
overrides the default one!

Nuno


>
>
> Thanks for your help, Mak
>
> ---- Original Message ----
> *From*: "Zach A. Thomas" <zach at aeroplanesoftware.com>
> *To*: sakai-dev at collab.sakaiproject.org
> *Sent*: Fri, May 22, 2009, 6:11 PM
> *Subject*: Re: [Building Sakai] [Building Sak ai] New
> component-newdependency-Please hel p!
>
> On May 22, 2009, at 8:26 AM, m_yaghmaie at modares.ac.ir wrote:
>
> > I was wondering whether my message was ignored or no body in this
> > group has any idea about it. I really really need help. My thesis
> > project is stoped :(
> The way this list works is that someone will answer if they have some
> idea how to help you. If you don't hear anything back, you should
> reframe your question or bring more information for us to consider.
>
> > The thing is that I am trying to make Sakai an adaptive learning
> > environment. So I developed an AI component which will some how
> > adapt the output for different learners. Right now I want to filter
> > the course material delivered to each learner. As I studied Sakai
> > module, this can be done by filtering the output that is generated
> > by SiteService. Specifically I have filtered the output of getSite
> > and findPage in the implementation of the SiteService by calling
> > some methods from my API. That is why SiteService depends on my API
> > but I have trouble in defining this dependency.
>
> SiteService should not depend on your API. Once you go down this road,
> you will eventually have to customize practically everything in Sakai.
>
> The shortest path to adaptive behavior in Sakai is to write a new tool
> that exhibits the behavior. As Steve said, you can then intercept any
> calls to any Sakai service and make changes as you need.
>
> If you really want SiteService with different behavior, you can try
> writing a new class that implements the SiteService interface, and
> delegate to the "real" SiteService for anything that doesn't need to
> behave differently. This is the Decorator pattern.
>
> good luck,
> Zach Thomas
> Owner, Aeroplane Software LLC
> http://aeroplanesoftware.com
>
> _______________________________________________
> 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"
>
>
> _______________________________________________
> 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"
>



-- 
Nuno Fernandes  [www.linkedin.com/in/nfgrilo]
Software Developer - UFP-UV  [Universidade Virtual]
Software Developer - Sakai Foundation  [sakaiproject.org]
Sakai Fellow 2008 - Sakai Foundation  [
confluence.sakaiproject.org/confluence/x/FIF9AQ]

Universidade Fernando Pessoa  [www.ufp.pt]
Praça 9 de Abril, 349
4249-004 Porto
tel: + 351 22 507 13 00
fax: + 351 22 550 82 69
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090522/bf446047/attachment.html