Loading...

XML

Word

Printable

Steps to Reproduce:

Hide

1. Add new module: Create new empty directory "org/jboss/remote-messaging".
2. Add "module.xml file" which contains wrong module dependency into that directory:
"<module xmlns="urn:jboss:module:1.3" name="org.jboss.remote-messaging">
<dependencies>
<module name="org.jboss.wrongmodule"/>
</dependencies>
</module>"
3. Start the server in "standalone" mode. Server starts without any problem, but it should FAIL with message that module "org.jboss.wrongmodule" was not found.
When adding the same wrong module dependency into existing module's configurations, server start fails.

Show
1. Add new module: Create new empty directory "org/jboss/remote-messaging". 2. Add "module.xml file" which contains wrong module dependency into that directory: "<module xmlns="urn:jboss:module:1.3" name="org.jboss.remote-messaging"> <dependencies> <module name="org.jboss.wrongmodule"/> </dependencies> </module>" 3. Start the server in "standalone" mode. Server starts without any problem, but it should FAIL with message that module "org.jboss.wrongmodule" was not found. When adding the same wrong module dependency into existing module's configurations, server start fails.

When there is dependency to non existing modules in a new added module configuration file, server starts without any problem. But should fail.

The same non existent dependency added into existing modules configurations, causes server to not start and appropriate errors are shown.

clones

JBEAP-363 Server starts when new module contains wrong dependency