How is the Managed Concurrency API related to HTTP outgoing connection pool?
Can you provide an example?
Regards,
Witold Szczerba
---
Sent from my mobile phone.
On Sep 27, 2013 12:01 AM, "Noah White" <emailnbw_at_gmail.com> wrote:
> Why not use the Jersey 2 client API with the new EE7 Managed Concurrency
> APIs?
>
> -Noah
>
> On Sep 26, 2013, at 2:55 PM, Witold Szczerba <pljosh.mail_at_gmail.com>
> wrote:
>
> This is exactly what I was looking for, today, and couldn't find an answer.
> I am looking forward for solution to this problem. How could the JEE spec
> group went over that?
>
> Regards,
> Witold Szczerba
> ---
> Sent from my mobile phone.
> On Sep 24, 2013 5:01 PM, "Jan Algermissen" <jan.algermissen_at_nordsc.com>
> wrote:
>
>> Hi,
>>
>> sorry, I guess I am not the first one to ask this, but searching really
>> does not turn up anything useful for me so far.
>>
>> In the application In develop, I need to make outgoing HTTP requests.
>> Given I should neither manage HTTP connections nor associated threads
>> myself in an EE container, I wonder
>>
>> - whether Glassfish maybe comes with the appropriate JCA connector to do
>> this already?
>>
>> - what other's do (besides ignoring the spec and simply firing up an
>> Apache HTTP client withit's own thread pool)?
>>
>>
>> Jan
>
>