They both are dependencies, just with a little different defaults. Based on the FAQ item I created when I was looking at the difference before, it should be started but not installed:
Q8 What is the difference between depends and demand elements?
A8: depend is a dependencyItem on the referenced bean reaching its Start state before the dependee will be allowed to reach its Start state.
Demand is a dependencyItem on the referenced bean reaching its Installed state before the dependee will be allowed to reach its whenRequired(state attribute of demand) state.
This does not say exactly when injection happens though. Ales?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192584#4192584
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192584
"jesper.pedersen" wrote :
| These are used in the inflow part of the resource adaptor currently (in the class that implements javax.jms.ServerSessionPool).
|
Can you take me through why that is necessary?
anonymous wrote :
| The DLQ functionality is also used in the inflow part - just for your information.
|
Hmmm, JBM already has DLQ I don't follow why this would be necessary for a JBM 2.0 only RA...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192571#4192571
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192571
This file is supposed to be bundled as per the messaging workspace.
| anil@localhost:~/messaging/Branch_1_4$ find . -name connection-factories-service.xml
| ./integration/EAP4/etc/server/default/deploy/connection-factories-service.xml
| ./integration/AS5/etc/server/default/deploy/connection-factories-service.xml
| ./output/etc/server/default/deploy/connection-factories-service.xml
| ./output/jar/connection-factories-service.xml
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192570#4192570
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192570
anonymous wrote : max messages and max session - these can probably go
These are used in the inflow part of the resource adaptor currently (in the class that implements javax.jms.ServerSessionPool).
anonymous wrote : All the dlq stuff can go - JBM has its own sophisticated dlq system
The DLQ functionality is also used in the inflow part - just for your information.
Thanks for the pointer to the internal API - I'll look it over and post some design.
I think we should aim for a solution that uses as much of the existing resource adaptor as possible for the first beta. After getting it up and running we can start to make optimizations.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192569#4192569
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192569