I am used to jboss 5 deployment schemes where I use to deploy this order:
D: \ jboss5 \ bin \ run.bat -cZZZ
whatever posted in the jboss5 \ server \ ZZZ folder
This structure is on my Jabs 7:
D: \ jboss7 \ standalone-server ++ zzz +++ module
Run jboss7 like this when I try:
D: \ jboss7 \ bin \ standalone-server.bat -cZZZ
The complaint with the N:
org.jboss.modules.ModuleNotFoundException: Module org.jboss.as.standalone: Main local module is not found in loader @ 7559ec47 (root: D : \ jboss7 \ standalone server \ modules) on org .jboss.modules.LocalModuleLoader.findModule org.jboss.modules.ModuleLoader.loadModuleLocal (ModuleLoader.java:275) to (LocalModuleLoader.java:126) org.jboss.modules.ModuleLoader on .preloadModule (ModuleLoader.java:222) on org.jboss.mod ules.LocalModuleLoader.preloadModule org.jboss.modules.ModuleLoader.loadModule (ModuleLoader.java:204) (LocalModuleLoader.java:94) org.jboss.modules
Appreciate the answer for .main.main (Main.javamore62)
A standalone JBoss the default EAP is based directory for 7 example as 6 / JBoss $ {JBOSS_HOME} / standalone
-Djboss.server.base.dir = ZZZ
You can see the JBoss instance based directory So if your ZZZ / configuration
and ZZZ / Deployment
directory, and place your standalone.xml file in
ZZZ / configuration>, then start the jboss using options. If your JBoss configuration file is not called, then
standalone.xml / code> to add you n eed
something like this will appear
-Dtarget.appserver.configfile = my_standalone_config.xml
$ There's no need to be within {JBOSS_HOME}
subdirectory tree in fact it is better to keep it different anywhere else because you without JBOSS binaries to update / re with overwriting your configuration files Allows the President. Module
folder $ {JBOSS_HOME}
was $ {JBOSS_HOME}
Code> C: \ jboss7
c: \ jboss7 + bin + module + standalone < - Not used! ... etc c: \ standalone-server + zzz ++ configuration +++ standalone.x + deployment
No comments:
Post a Comment