You may want to look at Karaf, which has support for deploying 'features':

http://felix.apache.org/site/44-deployer.html



On Sun, 14 Mar 2010 12:51:01 -0300, Solset - verizon.net <[email protected]> wrote:

Ali,

So I'm familiar with fileinstall and have used it in the past. It's a very convenient tool for installing a bundle but as far as I can remember if the bundle that you are installing via fileinstall has dependencies that are not installed in the container then of course it won't install because of unresolved dependencies. Is there a way for me to use fileinstall with some other tool which could use a list of URLs to retrieve and install all the required dependencies for that bundle?

Ali Naddaf wrote:
OSGi framework, on its own, doesn't monitor filesystem for new bundle or updates to them; you need to either write your own mechanism, or use something like fileinstall [1] to do that for you.
Ali

[1] http://felix.apache.org/site/apache-felix-file-install.html

On 3/14/2010 10:29 AM, Leon668 wrote:
I just manually copied the file to the folder where the other jar files are. I hope I am doing something right?

On Sat, Mar 13, 2010 at 10:12 PM, Ali Naddaf <[email protected] <mailto:[email protected]>> wrote:

    Are you using the fileinstall or something like that? How is the
    deployment happening in your case?


    On 3/13/2010 11:08 PM, Leon668 wrote:

        I am writing to see if the OSGI bundles can be installed when
        I copy a new
        bundle to the folder I deploy the bundles.

        I tried to copy some new bundles there at runtime, but it
        looks like I
        cannot get them automatically deployed. I wonder if I missed
        anything or
        not.


        Thanks,

        Leon





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



--
Greg Lucas

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to