[jboss-jira] [JBoss JIRA] (WFLY-4828) Server starts when new module contains wrong dependency
Stuart Douglas (JIRA)
issues at jboss.org
Thu Jun 25 10:09:04 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083823#comment-13083823 ]
Stuart Douglas commented on WFLY-4828:
--------------------------------------
What makes you say that it can be loaded with no error? The reason why *most* existing modules being malformed will cause boot to fail is because the server needs them to boot. If it does not need them then it will not be loaded as part of the boot process. The is exactly the same as class loading, just because a class is on the class path it does not mean that it is loaded, it is only loaded when required.
For custom modules that are not part of the server the first time they will be used is when a deployment that dependents on them tries to link against them, this will cause the deployment to fail. This is also expected behaviour.
There is no confusion here. Modules are loaded lazily, and if the module.xml file is incorrect they will fail. If they are a core part of the server the boot process will fail as a result. If they are used by a deployment the deployment will fail as a result. If they are not used at all then nothing will happen.
> 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)
More information about the jboss-jira
mailing list