Hi Igor,
>
> While on my quest to find answers I noticed that the recent gfv3
> promoted builds don't contain grizzly-module.jar any more, and
> grizzly is packaged as what seem to be osgi enabled grizzly modules
> which are the maven artifacts from the regular build. The version in
> the build I grabbed was 1.9.4.
>
> So my guess is that grizzly-module.jar stuff was EOLed and replaced
> with artifacts from the usual grizzly build. I think that is a good
> news.
>
> Now the question is - I can just simply remove grizzly-module.jar
> and grizzly-optionals.jar and replace them with with 1.9.x build
> artifacts?
I think not, IMHO OSGi will not see those jars. Theoretically you can
repackage grizzly artifacts to grizzly-module and grizzly-optionals...
but due to Grizzly changes (Pipeline->ExecutorService) I think prelude
will not be able to use latest Grizzly.
Thanks.
WBR,
Alexey.
>
>
> /i
>
>
>
> On Mar 4, 2009, at 10:17 AM, Igor Minar wrote:
>
>> Hi everybody,
>>
>> I've read this: http://weblogs.java.net/blog/jfarcand/archive/2008/11/updating_grizzl.html
>> and http://www.nabble.com/Re:-Problem-with-Bayeux-Servlet-Client-in-GlassFish-V3-p20835330.html
>>
>> but I still wasn't able to find the answer I'm looking for.
>>
>> I'd like to upgrade glassfish v3 prelude to use the latest grizzly
>> 1.9.x. Where can I find the 1.9.x grizzly-module.jar files?
>>
>> Is there a reason why I shouldn't use 1.9 with glassfish v3?
>>
>> Does anyone know what will be the grizzly branch that glassfish v3
>> will ship with? will it be 1.9.x, 1.10.x or 2.x?
>>
>> thanks!
>>
>> /i
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>