Yep - we have it working fine, albeit we use a very "thin" webstart
layer which is really just a custom launcher.
The launcher loads the usual OSGi properties via URL, which amongst
other things then installs and starts the various bundles, whose
location are also specified via URLs in the auto.installl an auto.start
properties.
So in truth - it's only really the launcher that actually gets loaded
via webstart, the rest of the application loading is done via OSGi -
which in our case is exactly what we wanted.
We found we needed to sign all of our JARs to make the process work, to
meet WebStart security policy which gets inherited by the VM OSGi runs in
Regards
-- Rob
On 16/06/2010 7:41 PM, Tony Anecito wrote:
Has anyone been able to get OSGI working with java Web Start? Or is there a
different recommendation for intial deployment for Swing-OSGI. Seems like OSGI
is good for after you deploy but not the model for initial deployment for java
apps. Web Start handles jnlp initial deployment of the java jvm where as OSGI
doe not but does do the updates like Web Start does already. I am looking for a
more complete solution and it seems OSGI is not quite the complete solution but
I am very open to constructive suggestions on how to achieve that using OSGI
and something else.
Regards,
-Tony
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
--
Ascert - Taking systems to the Edge
r...@ascert.com
+44 (0)20 7488 3470
www.ascert.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
