[
https://issues.jboss.org/browse/WFLY-956?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on WFLY-956:
----------------------------------
I think this points to a possibly fundamental problem with how we are handling module
dependencies. I suspect that despite the recent dependency processing algorithm rework,
mixing module loader types is still not quite right.
Ideally we'd have one uniform mechanism which sets up service dependencies for
ServiceModuleLoader modules, and then uses static deps for static modules, which should
allow everything to fail-fast (either with a service dependency error or a module
dependency error depending on what kind of module is missing).
It might be even simpler/clearer if there were separate module loaders for extensions,
file class path items, and deployment items. But that's not essential to solve this
issue I don't think.
deploy hangs if module import doesn't exist
-------------------------------------------
Key: WFLY-956
URL:
https://issues.jboss.org/browse/WFLY-956
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Class Loading
Reporter: Bill Burke
Assignee: David Lloyd
If you have a module dependency and that module has its own dependency that doesn't
exist, deployment will hang.
To reproduce, create a simple WAR that has a jboss-deployment-structure.xml that imports
an existing module. Have that existing module import a different module that doesn't
exist.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira