JBM 2 default configuration, what should it be

[ataylor]

I think the default jms configuration should contain 1 default Connection Factory named ConnectionFactory and 2 queues DLQ and ExpiryQueue.

As far as security goes I think we should have one default user 'guest' who has a 'guest' role. There should be one catch all security setting (#) that applies only the send, consume, createTempQueue and deleteTempQueue to ther guest role only. admin, deleteDurableQueue and createDurableQueue will need to be added by the user. There should be no security match for admin either

There should be one catch all queue settings that basically applies the defaults.

Also I'll remove the jbm-queues from the standalone config so its the same as the AS config and I will rename all the beans files to jbm-jboss-beans.xml, this means the user should just be able to copy over the examples config if this is what they want.

I'll remove any commented out config from all the config files, its messy and we have this covered in the examples now.

regarding the jbm-configuration.xml file, should we leave all the defaults in or trim them down similar to what we do in the examples config?

wdyt?

[timfox]

I think that in our standard config we should only specify a value in the config if there is a need to specifically override a default - i.e. the configs will be almost empty.

Right now I am creating a "full config", for illustration purposes and the docs. We can include this in the distro too, as an example of everything specified.

[ataylor]

I think that in our standard config we should only specify a value in the config if there is a need to specifically override a default - i.e. the configs will be almost empty.

+1.

Should we have the invm acceptor/connectors configured by default or just Netty?

[ataylor]

I also notice that the AS configs have no jbm-jms.xml config. I think the AS config should be the same as the standalone config so I'm adding defaults.

[jmesnil]

"ataylor" wrote:
I also notice that the AS configs have no jbm-jms.xml config. I think the AS config should be the same as the standalone config so I'm adding defaults.

Not sure about that: I think AS must not have default resources (CF, destinations). We changed the javaee examples so that they also create the resources they need.

Tim will confirm that.

[ataylor]

Not sure about that: I think AS must not have default resources (CF, destinations). We changed the javaee examples so that they also create the resources they need.

Either way we should be consistent between both stand alone and AS. 1.4 does have default resources, a cf, dlq and expiry queue.