Nigel,
I'm thinking at a basic connection pool included in Java SE, like what we
have with LDAP. Of course, this connection pool should be configurable, so
that we can plug in a pool provided by a JMS server (like provided by
ActiveMQ), or by a third-party framework (for instance Spring).
The problem is, without a connection pool performance will be horrible, so
everybody is going to provide one, and hence it's better to have it
specified in the first place.
Julien.
On Tue, Jun 21, 2011 at 6:57 PM, Nigel Deakin <nigel.deakin_at_oracle.com>wrote:
> Julien,
>
>
> On 14/06/2011 10:10, Julien Dubois wrote:
>
>> 1. Configuring JMS
>> The JMS API should not rely on JNDI, so it is usable outside an
>> application server (inside Tomcat, a batch or a
>> lightweight ESB).
>> This configuration should include pooling of JMS ressources.
>>
>
> Can you please clarify what you mean by this last point?
>
> Are you suggesting that a JMS vendor needs to offer connection (etc)
> pooling for use in a Java SE environment? Or are you suggesting that JMS
> resources need to be somehow capable of being pooled in a third-party
> connection (etc) pool?
>
> Nigel
>
--
Julien Dubois
Twitter: @juliendubois <http://twitter.com/#!/juliendubois>
Phone: +33 (0)6 25 02 34 18