[Building Sakai] [Building Sak ai] adding new J AR de pend ancy to Sa kai

Sun May 10 04:04:12 PDT 2009

The covers are meant to be alternative ways to access the services but
they are not used by many of the core parts of the system so there is
a good chance your methods will not be invoked (or at least not when
you think they will be).

If you want to extend the system, a better alternative would be to
create a component which contains your code and either add the hooks
into the kernel service implementations and rebuild it OR look into
adding aspects with before or around advice to the methods in
question.

What error message do you see when trying to access the portal? Do you
still see the component manager and the portal webapp starting up in
the logs?

-AZ

On Sun, May 10, 2009 at 11:39 AM,  <m_yaghmaie at modares.ac.ir> wrote:
> Hi,
>
> Sakai binary works fine before modifying the JAR files. After the
> modification I can not access the portal anymore. I have modified
> org.sakaiproject.site.cover.SiteService.java and
> org.sakaiproject.user.cover.AuthenticationManager.java which are not an
> implementation of an interface. I have also added a new class in
> org.sakaiproject.site.cover package which is invoked by SiteService.java and
> accesses some methods in my JAR file. When running startup.bat all lines in
> shell window are INFO except some WARN about jsf which I have not changed.
>
> I really appreciate your support,
> Mak
>
> ---- Original Message ----
> From: Aaron Zeckoski <aaronz at vt.edu>
> To: m_yaghmaie at modares.ac.ir
> Cc: sakai-dev at collab.sakaiproject.org
> Sent: Sun, May 10, 2009, 11:57 AM
> Subject: Re: Re: [Building Sak ai] adding new JAR de pend ancy to Sakai
>
> Those are api jars which pretty much just have interfaces in them. If
> you change the interfaces then you would need to change the
> implementations as well.
>
> For sakai services, the service apis are mostly located in share/lib
> or common/lib. The service code is located in the components/*
> directories.
>
> Have you made sure that it will start when you remove your modified
> and added jars?
>
> Can you send along a copy of the logs from a startup attempt when you
> have the modified code in place?
>
> -AZ
>
>
> On Sun, May 10, 2009 at 7:02 AM, <m_yaghmaie at modares.ac.ir> wrote:
>> Hi,
>>
>> I have made some changes in sakai-site-api.jar and sakai-user-api.jar in
>> form of calling some methods from another JAR file which I have
>> implemented.
>> I added my JAR file and it's relevant library (which are also some JARs)
>> to
>> Tomcat/shared/lib next to the modified sakai JAR files. Tomcat starts with
>> no error or exception and when I try to access the portal it shows nothing
>> in browser. I have also tried putting my JAR files in Tomcat/common/lib.
>> Nothing changed. What could be wrong in my configuration?
>>
>> Thanks in advance, Mak
>>
>> ---- Original Message ----
>> From: Aaron Zeckoski <aaronz at vt.edu>
>> To: m_yaghmaie at modares.ac.ir
>> Cc: sakai-dev at collab.sakaiproject.org
>> Sent: Sat, May 9, 2009, 2:30 AM
>> Subject: Re: [Building Sakai] adding new JAR depend ancy to Sakai
>>
>> You probably need to provide a little more information. There must be
>> something in the tomcat logs (normally Sakai provides hundreds of
>> lines of logging on startup) so it would probably help to send that.
>> Also, what jars are you including? Are you replacing things or just
>> adding new things?
>> -AZ
>>
>>
>> On Fri, May 8, 2009 at 7:51 PM, <m_yaghmaie at modares.ac.ir> wrote:
>>> Hi,
>>>
>>> I have been working on an AI component which I am going to add to Sakai.
>>> I
>>> have downloaded and installed the binary version 2.5.4. I want to modify
>>> some JAR files in Tomcat/shared/lib directory , i.e. change some class
>>> files
>>> in order to invoke some methods from another JAR files (my component)
>>> which
>>> I have also put in shared/lib directory. When I start up Tomcat I got
>>> nothing in the log files but the portal doesn't start. Should I define
>>> the
>>> new dependency between JAR files somewhere?
>>>
>>> P.S. Since my modification to the Sakai source is very little I would
>>> rather
>>> avoid building Sakai from scratch using Maven. The binary distribution
>>> seems
>>> to work for me.
>>>
>>> Thanks, Mak
>>>
>>> _______________________________________________
>>> 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"
>>>
>>>
>>
>>
>>
>> --
>> Aaron Zeckoski (aaronz at vt.edu)
>> Senior Research Engineer - CARET - Cambridge University
>> [http://bugs.sakaiproject.org/confluence/display/~aaronz/]
>> Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
>
>
>
> --
> Aaron Zeckoski (aaronz at vt.edu)
> Senior Research Engineer - CARET - Cambridge University
> [http://bugs.sakaiproject.org/confluence/display/~aaronz/]
> Sakai Fellow - [http://aaronz-sakai.blogspot.com/]

-- 
Aaron Zeckoski (aaronz at vt.edu)
Senior Research Engineer - CARET - Cambridge University
[http://bugs.sakaiproject.org/confluence/display/~aaronz/]
Sakai Fellow - [http://aaronz-sakai.blogspot.com/]