... | ... | @@ -34,7 +34,7 @@ The my/XRX/src/mom directory contains the code connected to the mom-ca browser e |
|
|
Open the two auth.app.xml files side by side: The core/auth/auth.app.xml contains general infrastructural code. It contains different XQuery-modules that are pretty general. Now look at the mom/auth/auth.app.xml: In line 3 there is an xrx-element we have not seen before
|
|
|
-> ```<xrx:inherits>tag:www.monasterium.net,2011:/core/app/auth</xrx:inherits>```
|
|
|
The modules are inherited from /core/app/auth. So we have the basic infrastructural components at our disposal. The specific MOM implementation adds to that the routing information in the ```<xrx:resolver>``` element. And in the ```<xrx:conf>``` part that follows the sequence of user-roles that we are using in Monasterium (e.g. Moderator, HtmlAuthor).
|
|
|
A quick word concerning inheritance: You will only find ```<xrx:inherits>``` elements in files in the mom directory and not in files in the core folder, because the core directory only contains the fundamental building blocks -- thus the name "core" directory. See Inheritance for detailed info.
|
|
|
A quick word concerning inheritance: You will only find ```<xrx:inherits>``` elements in files in the mom directory and not in files in the core folder, because the core directory only contains the fundamental building blocks -- thus the name "core" directory. See [XRX plus plus Inheritance] for detailed info.
|
|
|
|
|
|
See the [MOM-CA compiling and deployment guide](./Compiling-and-Deploying-Source-Code) on how to compile and deploy XRX source code into a MOM-CA instance.
|
|
|
|
... | ... | |