The hornetq-server and sub-resources have extra configurable properties and operations currently not exposed for deployments.
HornetQ server for deployments has been updated. master branch commit: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=749d24468d8861bd476f15a6b8e58e6d3ffbb41f
verifying on JON 3.1.ER4 I see one confusing thing here. If I try to add Child resource for 'hornetq' typeof 'Path', resourceName I type in is ignored and new resource is always called 'journal-directory'. I was checking AS7 CLI and messaging schema found out that: there are 4 possible path names, that can be added (in schema directoryType): paging-directory bindings-directory journal-directory large-messages-directory Using CLI I can do this: /subsystem=messaging/hornetq-server=default/path=paging-directory:add(path=/tmp) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } But I cannot do the same using JON, since resource-name is ignored and there's always passed 'journal-directory' Anyway, for a JON user configuring hornetq it is very hard to figure out above 4 setting names. I suggest transforming 'Path' child resource into 4 hornetq configuration properties.
Comment #2 does not apply to deployment messaging subsystem. Please retest this BZ within the context of a deployment with the messaging subsystem. The path would be /deployment=test.war/subsystem=messaging I created bug 826066 to capture comment #2 from Libor.
verified on JON3.1.CR1
Bulk closing of old issues in VERIFIED state.