Re: [wildfly-dev] Cannot load module alias defined for root deployment
On Friday 24 May 2013 06:50 PM, Thomas Diesler wrote:
A module alias should be unique, if a deployment defines an alias of
an already existing module it should fail. System modules cannot have
dependencies on deployment modules.
That looks like a (unnecessary) complexity. Assume, there's a foo.bar
static module and then some deployment configures a module named foo.bar
within it's jboss-deployment-structure.xml. I haven't looked at JBoss
Modules implementation and how it interacts with the module loaders, but
how would it know that foo.bar "already exists" as a static module?
By the way, why do we need this? I read up the JIRA and the comments in
the PR but I am not sure what the real requirement is.
-Jaikiran
Attachments:
- attachment.html (text/html — 1.5 KB)