Re: Plugins system?
Re: Plugins system?
- Subject: Re: Plugins system?
- From: Henrique Prange <email@hidden>
- Date: Mon, 17 Jan 2011 11:39:23 -0200
Hi Pascal,
On 16/01/2011, at 14:07, Pascal Robert wrote:
>
> Le 2011-01-16 à 11:00, Anjo Krank a écrit :
>
>> - Use some scripting system like jruby. Presumably it can reload code.
>> - Include everything beforehand an en-/disable based on properties.
>
> That's a pretty neat idea!
>
We have this structure in our main application. One drawback: you have to deploy the entire application even for small changes on specific "plug-ins".
We're thinking about OSGi as way to improve the situation. But I have no idea about the implications of an integration OSGi + WebObjects. :(
Cheers,
Henrique
>> - create a new class loader, call App.main() and quit the current app (probably tricky to do).
>
> Yirk.
>
>> And it would depend on what sort of functionality you actually want to add.
>
> I was thinking of doing a small CMS as an WO/Wonder tutorial, and like most CMS it would be great to extend it with plugins. A sample plugin would be to Alfresco or CMIS integration, where you can get files from a CMIS repository (Alfresco being one of them) and link to those files in a CMS-built Web site. Somewhat like Confluence: you get a very good set of plugins by default but you can extend it by getting plugins from a central list of plugins made by Atlassian and others.
>
>> Cheers, Anjo
>>
>>
>>
>> Am 16.01.2011 um 15:44 schrieb Pascal Robert:
>>
>>> I'm thinking about doing a plugins system so that a WO server-side app can add functionality based on what the customer select. So far, I think the only options are:
>>>
>>> - Using ERXInlineTemplate for components that don't need new or modified Java code.
>>>
>>> - When a new plugin is selected, trigger a new version of the app in Hudson, send back the new version to the customer, install it and restart the instances.
>>>
>>> - When a new plugin is selected, send the plugin as a framework, modify the *ClassPath.txt file to include the new framework and restart the instances.
>>>
>>> - Wait for LiveRebel.
>>>
>>> Any other options? _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden