Le 2011-01-16 à 09:44, Pascal Robert a écrit : > 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?
... take the probleme the other way around ... Maybe the plugin doesn't 'have' to be in the same memory than the central app? So each plugin become an independant app, and you delegate/dispatch request to them. If a plugin needs 'core' functionnality, it need to link to the 'core' framework'. In order for that system to work, you would need to define a clear and deep api between the 'core' app, the 'core' plugins and the 'extra' plugins. ... as I think of it, it wont be simple ... jfv _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
