-
15. Re: schema for standalone server
For some reason I didn't receive an email for Brian's post. I've just merged the schemas into jboss_7_0.xsd and added standalone element.
http://github.com/aloubyansky/jboss-as/commit/55dd758b5fe37d7b45ae8da74b308a1c8012842d
If there are no objections/suggestions then separate domain and host schemas should be removed to avoid confusion.
Ok, thanks, I'll check out the branch.
-
16. Re: schema for standalone server
I pulled in your stuff, made some tweaks, removed jboss-domain.xsd and jboss-domain-host.xsd and pulled everything I could out of jboss-domain-common.xsd. There are a few things left there since jboss-domain-web and jboss-domain-mod-cluster aren't in separate namespaces yet and use some of the common elements.
I then did added parsing and marshalling code to the Standalone class.
I pushed this to my github repo, server-mgr-dev branch.
Standalone includes a field:
private JvmElement jvm
I want to get rid of that. A <jvm/> child of <standalone/> doesn't make much sense, since standalone is single process -- the vm config is whatever the user did at command line. I added that field to Standalone to hold the result of combining the jvm elements from server-group, host and server in a domain.xml + host.xml. But that combination shouldn't be done in Standalone and result shouldn't be cached there. Tomorrow I'll move it to the server-manager module; the SM is the one that uses this jvm stuff.
I'll also add an example standalone.xml and some a validation test.