Hello Martin,
client and server side aren't tied in any way, Jersey server doesn't
know which client is accessing it, thus restarting after each get is
something not related to jersey server or client.
If you experience this in your tests (and you do use jersey test
framework) then it is standard behavior BUT grizzly reinitialization
happens not after each get() (or request in general) but for each @Test
method. Is this your case?
Pavel
On 5/17/10 11:45 AM, Martin Scholl wrote:
> Hi,
>
> I've would like to have a little hint to understand, what is going on when accessing a REST resource using the Jersey Client API and Grizzly Container:
>
> Every time I invoke WebResource.Builder.get(MyClass.class) I see the message
>
> May 17, 2010 11:34:16 AM com.sun.grizzly.Controller logVersion
> INFO: Starting Grizzly Framework 1.9.18-i - Mon May 17 11:34:16 CEST 2010
>
> which seems to me that Grizzly is initialised every time I invoke the method which would be pretty inefficient.
>
> Is this a fact or did I just misconfigure Jersey or Grizzly or both or where did I do sth wrong? Is anyone familiar with this "issue"?
>
> Thanks for your help.
>
> Cheers,
>
> Martin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>