Are the scripts stored as text on disk or packaged as a bundle?
Kind regards,
Peter Kriens
On 4 mrt 2011, at 07:50, Hamlet DArcy wrote:
> Hi all,
>
> I am hoping for some architectural/design guidance.
>
> I have an existing application that loads & executes Groovy scripts from disk
> in order to provide custom logic to different customers. For instance,
> Customer X is mapped to a certain directory and the custom validation rules
> sit in "validation.groovy" in that customer's directory. We have almost 5000
> scripts that get executed this way. I want to use OSGi to execute the scripts
> because then each customer can specify which version of Groovy to use
> (modularity) but the calls are still in process and fast.
>
> My idea is to define an OSGi service interface and have 3 implementations
> (Groovy 1.6, Groovy 1.7, and Groovy 1.8). The script controller will know
> what version to execute against and dispatch processing to the correct OSGi
> bundle that has that version of Groovy as a private dependency.
>
> My questions:
> 1) Do you see any obvious problems with this approach?
> 2) How easy & performant is it to embed an OSGi container into my existing
> application?
> 3) Do you have any recommendations on which container to use?
> 4) Do you have an links or examples that are a good starting point on how to
> do this?
>
> Thanks in advance,
>
> --
> Hamlet D'Arcy
> [email protected]
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
