It doesn't actually need to make HTTP calls. The user invokes
methods on the Client class. You could very well translate those calls
into equivalent server-side requests without ever happening opened a
socket. Remember, we've got Jersey on both ends.
Gili
On 16/06/2011 11:54 AM, zzantozz [via Jersey] wrote:
> I haven't looked into the in-memory test stuff yet, but unless there
> have been some pretty drastic changes to the client API, I'd say
> that's not possible. The Jersey client makes HTTP calls. It wouldn't
> make a lot of sense to make it aware of a test framework that it might
> possibly be talking to.
>
> On Wed, Jun 15, 2011 at 4:10 PM, Gili <[hidden email]
> </user/SendEmail.jtp?type=node&node=6483633&i=0>> wrote:
>
> Hi,
>
> How exactly does InMemoryTestContainerFactory work? Am I correct
> in assuming
> that it never binds itself to any port? Does it simply redirect
> function
> calls from the client directly to function calls on the server?
>
> Thanks,
> Gili
>
> --
> View this message in context:
> http://jersey.576304.n2.nabble.com/InMemoryTestContainerFactory-tp6480614p6480614.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
>
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the
> discussion below:
> http://jersey.576304.n2.nabble.com/InMemoryTestContainerFactory-tp6480614p6483633.html
>
> To unsubscribe from InMemoryTestContainerFactory, click here
> <http://jersey.576304.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=6480614&code=Y293d29jQGJicy5kYXJrdGVjaC5vcmd8NjQ4MDYxNHwxNTc0MzIxMjQ3>.
>
--
View this message in context: http://jersey.576304.n2.nabble.com/InMemoryTestContainerFactory-tp6480614p6484169.html
Sent from the Jersey mailing list archive at Nabble.com.