[jboss-jira] [JBoss JIRA] (WFLY-4828) Server starts when new module contains wrong dependency

[Hayk Hovsepyan (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087456#comment-13087456 ] 

Hayk Hovsepyan commented on WFLY-4828:
--------------------------------------

Sorry for miscomprehension about "loaded without error".
Let me rephrase the description.

Case1: We have new added custom module X which depends on non existing module Y.
Server is started correctly. As you have clarified in your comments, due to lazy loading design, it works as expected.
When module X is loaded to be used, it fails to be loaded, which is expected as well, but the failure message is: "module X is not found", in fact it should be "module X can not be loaded, because dependent module Y is not found".

Why I say it should be, because of case 2.
Case2: When the module A, which loaded in boot process, contains dependencies to non existent module B (somehow spoiled), the failure message is something like "module A can not be loaded as dependency module B can not be found".

So here is the confusion: In a failure message difference in above described cases.



> Server starts when new module contains wrong dependency
> -------------------------------------------------------
>
>                 Key: WFLY-4828
>                 URL: https://issues.jboss.org/browse/WFLY-4828
>             Project: WildFly
>          Issue Type: Bug
>          Components: Server
>            Reporter: Hayk Hovsepyan
>            Assignee: Jason Greene
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)