Queue creation nested in EAR

[mlipp]

Hi,

I would like the queues needed by my application to be automatically created when I deploy the .ear. Currently they are created by first deploying an appl-destination-service.xml.

I first looked at some possibility to specify this in jboss-appl.xml, no luck. Now it has just occured to me that the queues are just services required by the application. So I simply included appl-destination-service.xml in EAR.jar/META-INF (first try) and then "top-level" in EAR.jar/. Doesn't work.

Is there any way to specify nested deployments aside from those that come out of application.xml? (JBoss-3.2.1, by the way.) I have read about the "general configuration flag" for nested deployments which is "No" by default. Changing this is not really a solution as it changes the behaviour of the whole server while I just want some additional deployments for my application.

- Michael

[darranl]

In addition to adding your 'appl-destination-service.xml' have you tried adding a module element to the jboss-app.xml e.g.


appl-destination-service.xml


I think that this method should work (At least in the JBoss 3.2 branch)

Previously in the JBoss 3.0 branch I think the service.xml needed to be wrapped in a sar.

[darranl]

Sorry the first line should have read :-

In addition to adding your 'appl-destination-service.xml' to the root of the ear have you tried adding a module element to the jboss-app.xml e.g.

[mlipp]

Thank's it works. My solution looks a bit different, though.

As the DTD states that should specify a .sar file, I have packed the appl-destination-service.xml in a dest.sar as META-INF/jboss-service.xml, put the dest.sar in the EAR (top-level) and specified <moduledest.sar in the jboss-appl.xml.

This should be in the manual (I looked again: the bought documentation has not a single reference to jboss-appl.xml in it).

- Michael