ConnectionConsumer feature

[joany]

Hi,

Our JMS does not support ASF ( chapter 8 SUN spec). According to my understading, we need to have the three interfaces:
* ServerSession
* ServerSessionPool
* ConnectionConsumer
The Application Server vendor has to implement these interfaces. Please correct me if I am wrong. Can you please throw some light on it.
We are going to support this feature. How to go for the same?

Thanx in advance.

[adrian.brock]

The JMS provider implements the ConnectionConsumer.
The AS implements the server session pool.
see the package org.jboss.jms.asf if you are interested

[joany]

Thanx Adrian for the spontaneous response.

Since I dont have much hang about the ASF, can you please answer this doubt of mine.

We have our own JMS provider (it is platfrom specific). The point is even if we make use of any AS in the market, how to plugin our Jms Provider. Most of the App Server have their own implementaion of Jms provider.

This question might be sounding silly, but your response will be very helpful.

Thanx in advance.
:-)

[adrian.brock]

It is a spec requirement that your ConnectionFactorys and Destinations are both
Serializable and Referenceable.

With these two requirements they can be bound into any AS's jndi,
although the mechanism to achieve the binding varies.

I'd suggest you take your fine tooth comb out of your back pocket and re-read the spec.

[joany]

Hi Adrian,

Thanx a lot.

Finally one last doubt... For websphere MQ JMS, it is mentioned that we can use ASF in a standalone environment ( that is, you do not need a suitable application server ) ..

Is it feasible?

Thanx in advance.
J

[adrian.brock]

Of course, but you would have to configure it yourself.

Non managed environment == You have to take over the management