Cannot load module alias defined for root deployment
by Thomas Diesler
Folks,
currently we allow an arbitrary module alias to be defined with a deployment/subdeployment in jboss-deployment-structure.xml. The ServiceModuleLoader will however only accept module identifiers that have the 'deployment.' prefix.
I believe the 'deployment.' prefix is an unnecessary constraint for deployed module aliases. Deployments should be able to define any alias. This would allow for a deployment to get 'promoted' to a system module without breaking clients. 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.
This change, provides a fallback in the ServiceModuleLoader that allows deployment modules to be loaded by their alias even if they don't have the 'deployment.' prefix. Unless I'm mistaken it only applies to inter deployment dependencies.
What do you think?
cheers
--thomas
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
11 years, 8 months
Windows Batch Scripts
by James R. Perkins
Hello All,
There was an issue found with the Windows batch scripts if the
JBOSS_HOME path had a space or a ) in it. I created a fix and PR to fix
the issue [1].
If anyone has any good or better ideas on how to make this cleaner
please let me know. We are toying with the idea of just using an EXE
instead of batch scripts, but any input from someone with more Windows
batch scripting experience than me is welcome.
[1]: https://github.com/wildfly/wildfly/pull/4520
--
James R. Perkins
JBoss by Red Hat
11 years, 8 months
