MainDeployer.listDeployed() returns empty collection

[chilin]

The admin console uses MainDeployer's listDeployed() operation to obtain needed information, but on the JBoss 5.0 Beta1 release, the results returned from listDeployed() is empty. Does anyone know what's going on? Has this problem been reported yet?

[starksm64]

The deployment layer is completely rewritten in jboss5. The old MainDeployer is being replaced with the kernel VDF based version that is an implementation of org.jboss.deployers.spi.deployment.MainDeployer. The VDF is described here:

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework

We need a testcase in the jboss5 testsuite that illustrates what the console is looking for so it can be mapped to the new implementation.

Also, services to not have to be jboss mbean services, so they may not be exposing a jmx interface at this point. We are working on beans express their management interface for the next beta.

[chilin]

When the user wants to view a list of queues (or topics, or a specific type of data sources), the console obtains the ObjectName of the mbeans from the MBeanServer, then walks through the results of the MainDeployer's listDeployed() operation to obtain the deployment information of these mbeans. The information that the console collects include:

DeploymentInfo.url
DeploymentInfo.state
DeploymentInfo.status

[mf1]

Has there been any progress in this issue? I see that in Beta2 the JMX console still doesn't show any deployed modules, i.e. that MainDeployer.listDeployed() or MainDeployer.listDeployedModules() still return empty collections.