"aaubry" wrote : "timfox" wrote : | | Though, if I compare commercial product to jBoss messaging, the behavior is quite different. In a commercial product that I won't quote here, it's quite easy to configure a queue or a topic with no datasource associated to it (storing enable=true or false). | | | | The thing I do not understand is that Jboss must have a datasource for all JMS stuff even though a persistant messaging system is not needed, because I know that if things goes wrong (server crash, ...), it's not business critical. | | | | As I say, this is a scheduled task and has been for some time. | | It is actually very easy to implement, we just haven't got around to it yet! | | We only have limited resources (two permanent developers) so we can't do everything instantly - take a look at JIRA for open tasks. | | If you like you could attempt the task yourself and contribute back to the project. | | wdyt? | | :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067310#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...