[Building Sakai] Adding Sites via API / SiteService deprecated

[Steve Swinsburg]

+1 site properties. This is what they are for.

Cheers,
S

Sent from my iPad

On 12/08/2013, at 23:27, "Mark J. Norton" <markjnorton at earthlink.net> wrote:

> What you are proposing comes under the heading of "a bad thing to do".  
> You are proposing to fork the Site code to add local information.  If 
> you do that, you will be stuck with maintaining that code for as long as 
> you are using Sakai.
> 
> I would suggest you look at Site properties, instead.  This is a general 
> mechanism that allows arbitrary information to be associated with a Site 
> object.  It is persisted in the database and simple to set and get.  You 
> can still write your custom "module that creates/adds sites to my sakai from
> another datasource", just save the extra datum as a property. That way 
> you won't be creating a custom kernel, you can use the standard Sakai 
> Site API.  Look for the "Entity" base  case, which Site extends.
> 
> - Mark Norton
> 
> On 8/12/2013 9:18 AM, Michael Mertins wrote:
>> Hi,
>> 
>> it seems I will need to extend the Sakai Worksites to add a few new fields
>> into the database with additional information. How do I extend the site
>> definition and the add site dialogue?
>> 
>> Could I simply extend the BaseSite implementation (for example with a new
>> course identifier) and add this one via SiteService? Do I have to touch
>> the SiteManager aswell if I want it to include the new field every time I
>> add a new site? And will it ask for it in the add-site-dialogue?
>> 
>> Best wishes,
>> 
>> Michael Mertins
>> 
>> 
>>> org.sakaiproject.site.api.SiteService is not deprecated, I'm guessing
>>> you are talking about the cover ?
>>> org.sakaiproject.site.cover.SiteService.
>>> 
>>> Generally, the recommend pattern is to inject the siteService into
>>> your class using the component manager (Spring).
>>> 
>>> Depending on what you are trying to do, you might find it easier to
>>> actually use web services for this type of activity.  That would allow
>>> you to keep your code outside of the core Sakai deployment, which
>>> often has its advantages.
>>> 
>>> There are methods for doing this stuff expose via Soap:
>>> 
>>> http://nightly2.sakaiproject.org:8085/sakai-axis/SakaiScript.jws?wsdl
>>> 
>>> Possibly via REST as well, I'm not so familiar with the Site capabilities
>>> there:
>>> 
>>> http://nightly2.sakaiproject.org:8085/direct/
>>> 
>>> On Thu, Aug 8, 2013 at 12:52 PM, Michael Mertins
>>> <mertins at zedat.fu-berlin.de> wrote:
>>>> Hi,
>>>> I would like to write a module that creates/adds sites to my sakai from
>>>> another datasource, should I rely on the SiteService although it's
>>>> deprecated right now? Any suggestions where to start? Advice?
>>>> Best wishes,
>>>> 
>>>> Michael Mertins
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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"
>>> 
>>> 
>>> --
>>> John Bush
>>> 602-490-0470
>>> 
>>> ** This message is neither private nor confidential in fact the US
>>> government is storing it in a warehouse located in Utah for future
>>> data mining use cases should they arise. **
>> 
>> _______________________________________________
>> 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"