[Building Sakai] change config values on the fly

[Earle Nietzel]

Also this web service (REST and SOAP versions) can change configuration:

https://source.sakaiproject.org/svn/msub/rsmart.com/webservices/trunk/cxf/src/java/org/sakaiproject/webservices/SakaiConfiguration.java



On Thu, Oct 9, 2014 at 3:50 PM, Charles Hedrick <hedrick at rutgers.edu> wrote:

> Matthew gave me the answer.
>
> I agree that persisting things in the database has advantages. It would
> let us build a tool, so I could change things once instead of having to go
> change them on each front end. But Matthew’s version of my original hack
> did let me solve the problem.
>
> On Oct 9, 2014, at 3:45 PM, Earle Nietzel <enietzel at anisakai.com> wrote:
>
> Hi,
>
> This won't help for 2.9 or 10 but you could look at
> https://jira.sakaiproject.org/browse/KNL-1063
>
> Documentation
> https://confluence.sakaiproject.org/display/~ern/StoredConfigService
>
> This is working in trunk has been there for a while but there is a small
> change that was suggested that I need to implement.
>
> Also we are planning to start an admin ui tool soon...
>
> On Tue, Oct 7, 2014 at 3:29 PM, Matthew Jones <matthew at longsight.com>
> wrote:
>
>> Hi!
>>
>> Based on what was known around the office as the Hedrick (properties)
>> Hack I'd kept it alive and expanded upon it. YMMV on this for sure, but
>> this worked for me and should get you a little further at least. There was
>> work in more recent versions of Sakai to make so properties could be
>> registered so maybe some day there'd be a UI that could change it like how
>> the message bundles can be changed live. But in any case it makes it a
>> little different for changing them now.
>>
>> https://confluence.sakaiproject.org/x/KQPBBQ
>>
>> On Tue, Oct 7, 2014 at 3:07 PM, Charles Hedrick <hedrick at rutgers.edu>
>> wrote:
>>
>>> I am in a situation where I’d like to change a configuration item on the
>>> fly. In 2.9 this was easy. Retrieve the map and change the value, and as
>>> long as the application read the map at use rather than remembering the
>>> value at init time, it worked.
>>>
>>> Now there’s this whole new configuration system that doesn’t seem to
>>> have the functionality to change any existing parameters. This is a bit of
>>> a step back for me. Any suggestions how to change a value?
>>>
>>> _______________________________________________
>>> 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"
>>
>
>
>
> --
> earle,
> asahi net int.
>
>
>


-- 
earle,
asahi net int.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20141009/1cc678d0/attachment.html