Mach-II/Mach-II-Framework — Issue #43: modules & includes xmls in a directory
Author: mpwoodward
Created: 2012-03-01 17:30:58+00:00
State: open
Labels: enhancement

(Moved from http://trac.mach-ii.com/machii/ticket/497)

Mach-II 1.6 has module & include for building large Mach-II applications.

` .... `

We use many "module" tag to add modules to application, but there should be a more flexable way to do this, like add a "moduledir" tag, to special a directory that contains the module's config files.

` `

/opt/www/config/modules/blog.xml /opt/www/config/modules/dashboard.xml

In that case, Mach-II will auto load two module named "blog" & "bashboard" in the "moduledir".

Jobs just like tomcat's webapp loader right?

Changed 2 years ago by peterfarrell

Cc kurtwiersma, mattwoodward, brianfitgerald, mikerogers, adrianscott added
Component changed from framework - properties to framework - core
Priority changed from minor to major
Version changed from 1.8.0 - Framework to 1.9.0 - Framework
Milestone changed from Mach-II 1.8.0 Final to Mach-II 1.9.0 Un-Targeted
Keywords module loader added
Thanks for the idea. It's something we've kicked around in the past, but haven't had time to implement in a manner that would be consist. We build an ANT style pattern matcher for 1.8 so this is something we can review for Integrity (1.9) now that we have a pattern matcher utility.

comment:2 Changed 18 months ago by peterjfarrell

Cc kurt_wiersma, matt_woodward, brian_fitgerald, mike_rogers, adrian_scott, doug_smith added; kurtwiersma, mattwoodward, brianfitgerald, mikerogers, adrianscott removed
Doug, I'm looking at this ticket again and I was thinking about your applications at DR.com. Just curious on how you structured your application files and wondering if something like this would make module development easier? With the new conditional module stuff Jason has been talking about on the list -- I'm wondering if this really is a good way to spend our time. Really you only define a module once and then you never do it again for the same module.

comment:3 Changed 18 months ago by doug_smith

Right, I don't know how this would work with our apps. We declare the module name and a base xml file in the tag at the base, but then each module has a config/ directory with a full mach-ii.xml, mach-ii_properties.xml, coldspring.xml, etc. So, each module essentially is self-contained, and referenced by a one-line entry at the base level. I don't think this feature would be very useful to us.

comment:4 Changed 18 months ago by peterjfarrell

Version changed from 1.9.0 - Framework to Uncategorized - Framework
Milestone changed from Mach-II 1.9.0 Un-Targeted to Uncategorized
I'm putting this back in the uncategorized milestone for review in a later release.