| RE: [orbit-dev] Questions about Apache BSF |
|
The current approach shown below has two issues. First it is
using Require-Bundle. If someone decides to supply scripting support for
say python, they may use a different bundle name. The second is of course
that *you* have to know all scripting languages ahead of time. This is a common problem with extensible infrastructure. Two
main approaches that I can suggest. -
Use a buddy loading policy that gets you the things you need -
Write some extensibility code that will help BSF find the classes
that it needs. Unfortunately, both of these then require the contributed bundle
to register somehow (well , do something) with BSF. That is better but
still less than optimal. As a first cut I am thinking that you can include as many Require-Bundles
as you think reasonable but then also add a “registered” buddy
loading policy statement to leave open the possibility of other bundles showing
up with scripting support. BTW, how does BSF access and instantiate the scripting engines? Jeff From:
orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx] On
Behalf Of Michael A Squillace
|