Re: Swing Apps & OSGI...

2010-06-16 Thread Marcel Offermans
That is indeed very similar to the solution I've used in the past. By having to 
sign the jars, you mean the jars that make up the "custom launcher", so you can 
run web start out of its normal sandbox, right? In any case we never needed to 
sign our bundles.

Greetings, Marcel


On Jun 17, 2010, at 7:39 , Rob Walker wrote:

> 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
> 


-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org



Re: Swing Apps & OSGI...

2010-06-16 Thread Rob Walker
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



Re: Swing Apps & OSGI...

2010-06-16 Thread Tony Anecito
Thanks Marcel that confirms what I have read. I had heard no one has tried 
using JWS + OSGI but I asked that question many months ago. I tried using that 
combination but ran into issues and had some other deadlines to get through 
first.

Have you or anyone else seen an example you can point me to with this 
combination? I will try again since I have some time.

Regards,
-Tony



- Original Message 
From: Marcel Offermans 
To: users@felix.apache.org
Sent: Wed, June 16, 2010 2:31:55 PM
Subject: Re: Swing Apps & OSGI...

Hello Tony,

On Jun 16, 2010, at 19:41 , Tony Anecito wrote:

> Has anyone been able to get OSGI working with java Web Start?

Yes. You can use web start to bootstrap the framework plus some kind of 
launcher or management agent that understands the web start environment 
(perhaps reading some configurable properties from the JNLP file, etc.) Since 
OSGi needs a local bundle cache, you cannot simply use the sandboxed, unsigned 
option of web start.

This management agent, when started, will then fetch the other bundles from the 
server (this has nothing to do anymore with web start). You probably want to 
use an algorithm to detemine a proper location for the bundle cache (that 
depends on the operating system and logged in user).

> 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.

Probably updating components when the client application is running is not too 
relevant (or even desired) in most desktop applications. Being able to use the 
OSGi programming model however is.

> 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.

Correct.

> 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.

OSGi by itself cannot bootstrap the JVM and there is no standard mechanism to 
bootstrap the installation of an OSGi implementation either, but combining 
JWS+OSGi definitely makes sense if you ask me.

Greetings, Marcel


-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org


  

-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org



Re: Swing Apps & OSGI...

2010-06-16 Thread Marcel Offermans
Hello Tony,

On Jun 16, 2010, at 19:41 , Tony Anecito wrote:

> Has anyone been able to get OSGI working with java Web Start?

Yes. You can use web start to bootstrap the framework plus some kind of 
launcher or management agent that understands the web start environment 
(perhaps reading some configurable properties from the JNLP file, etc.) Since 
OSGi needs a local bundle cache, you cannot simply use the sandboxed, unsigned 
option of web start.

This management agent, when started, will then fetch the other bundles from the 
server (this has nothing to do anymore with web start). You probably want to 
use an algorithm to detemine a proper location for the bundle cache (that 
depends on the operating system and logged in user).

> 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.

Probably updating components when the client application is running is not too 
relevant (or even desired) in most desktop applications. Being able to use the 
OSGi programming model however is.

> 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.

Correct.

> 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.

OSGi by itself cannot bootstrap the JVM and there is no standard mechanism to 
bootstrap the installation of an OSGi implementation either, but combining 
JWS+OSGi definitely makes sense if you ask me.

Greetings, Marcel


-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org