Mach-ii sub-application - part 2

To demonstrate sub-application setup I am going to use example application from mach-ii site called ContactManager. If you are going to follow along then download it and unzip into ContactManager folder under your webroot. After that you should be able to browse to it using http://[your-web-root]/contactmanager/

Next I made a folder under contactmanager called "subapp". Under that "config" folder. Also I made a subapphome.cfm file in the "views" folder to show something different in subapp. Just put any random text in that file. Look at an image of the ContactManager tree to see added elements.

Now we separate common elements into an include called mach-ii-common.xml
<br /><mach-ii version="1.5"><br /> <!-- PLUGINS --><br /> <plugins><br /> <plugin name="tracePlugin" type="MachII.plugins.TracePlugin" /><br /> </plugins><br /> <br /> <!-- EVENT-HANDLERS --><br /> <event-handlers><br /> <event-handler event="exceptionEvent" access="private"><br /> <view-page name="exception" /><br /> </event-handler><br /> </event-handlers><br /> <br /> <!-- PAGE-VIEWS --><br /> <page-views><br /> <page-view name="mainMenu" page="/views/mainMenu.cfm" /><br /> <page-view name="mainTemplate" page="/views/mainTemplate.cfm" /><br /> <page-view name="exception" page="/views/exception.cfm" /><br /> </page-views><br /></mach-ii><br />
Those elements are removed from main applications mach-ii.xml, but we add an include before properties section
<br /><includes><br /> <include file="../config/mach-ii-common.xml" override="true" /><br /></includes><br />
Here is sub-application mach-ii.xml
<br /><mach-ii version="1.5"><br /> <includes><br /> <include file="/contactmanager/config/mach-ii-common.xml" override="true" /><br /> </includes><br /> <br /> <!-- PROPERTIES --><br /> <properties><br /> <property name="applicationRoot" value="/ContactManager" /><br /> <property name="defaultEvent" value="showsubappHome" /><br /> <property name="eventParameter" value="event" /><br /> <property name="parameterPrecedence" value="form" /><br /> <property name="maxEvents" value="10" /><br /> <property name="exceptionEvent" value="exceptionEvent" /><br /> <br /> <property name="urlDelimiters" value="/|/|/" /><br /> <property name="urlBase" value="/index.cfm" /> <br /> </properties><br /><br /> <!-- EVENT-HANDLERS --><br /> <event-handlers><br /> <event-handler event="showsubappHome" access="public"><br /> <view-page name="subapphome" contentArg="content" /><br /> <view-page name="mainTemplate" /><br /> </event-handler><br /> </event-handlers><br /> <br /> <!-- PAGE-VIEWS --><br /> <page-views><br /> <page-view name="subapphome" page="/views/subapphome.cfm" /><br /> </page-views><br /></mach-ii><br />
Notice the properties for SES URLs.

There is at least one issue with this setup is that links need to be relative to the web root so that they work from main app and from sub app. So in mainTemplate.cfm file I added "/contactmanager/" to all the links resource references at the top.
Here is an example, following lines
<br /><a href="index.cfm?event=showHome">Home</a> | <br /><a href="index.cfm?event=listContacts">List Contacts</a> | <br /><a href="index.cfm?event=newContactEventArgs">Add Contact Using Event Arguments</a> | <br /><a href="index.cfm?event=newContactEventBean">Add Contact Using an Event Bean</a> | <br /><a href="subapp/">Sub-Application</a><br />
became...
<br /><a href="/contactmanager/index.cfm?event=showHome">Home</a> | <br /><a href="/contactmanager/index.cfm?event=listContacts">List Contacts</a> | <br /><a href="/contactmanager/index.cfm?event=newContactEventArgs">Add Contact Using Event Arguments</a> | <br /><a href="/contactmanager/index.cfm?event=newContactEventBean">Add Contact Using an Event Bean</a> | <br /><a href="/contactmanager/subapp/">Sub-Application</a><br />
As you can see I also added a link to my sub-application.

After all this you should be able to get to your subapp by going to http://[your-web-root]/contactmanager/subapp/index.cfm/event/subapphome/