I'm not saying that implementing ServerSessionPool will be necessary for the JBM 2.0
resource adaptor.
The current adaptor has a pool of sessions for each activation
| <inbound-resourceadapter>
| <messageadapter>
| <messagelistener>
|
<messagelistener-type>javax.jms.MessageListener</messagelistener-type>
| <activationspec>
|
<activationspec-class>org.jboss.resource.adapter.jms.inflow.JmsActivationSpec</activationspec-class>
| <required-config-property>
|
<config-property-name>destination</config-property-name>
| </required-config-property>
| </activationspec>
| </messagelistener>
| </messageadapter>
| </inbound-resourceadapter>
|
You can follow the flow JmsActivationSpec -> JmsActivation -> JmsServerSessionPool
-> JmsServerSession (this class implements javax.jms.MessageListener).
I'm looking through your API currently and will post the initial design after big
Turkey day holiday.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192623#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...