title: How to create a modular JSF 2.0 application?
body: <p>I have an application with a well defined interface.  It uses CDI for resolution of the modules, (Specifically it uses Instance&lt;> injection points on API interfaces to resolve modules) and passes various data back and fourth via the interfaces without issue.  I've intentionally kept the API and implementation separate, and the modules only inherit from the API to avoid tight coupling, and the application only knows of the modules through runtime dependancies, and data passing accomplished via the APIs.  The application runs fine without the modules, which can be added simply by dropping the jar into the WEB-INF/lib folder and restarting the app server.</p>
  
  <p>Where I'm running into issues is that I want the modules to create a portion of the view, and I therefor want to invoke, in a portable way, either a JSF component, or do an include from the module in order to have it render its view. I already have resolved what module I want to invoke, and have references to the module's interface ready. The way I initially thought to do this was to do a ui:include that asks the module to supply where it's view template is, but I have no idea how to answer that query in a meaningful way, as view resolution is done from the application root, not the library root.</p>
  
  <p>The executive summary is that I have no idea how to jump the gap from Application to Library using JSF for .xhtml (template/component) files.</p>
  
  <p>Using a CC would be nice, but how do I specify that I want a particular CC instance at runtime, instead of having that hard coded into the page?</p>
  
  <p>I can of course invoke the application code directly and ask it for markup, but this seems really brute force, and once I have the markup, I'm not sure exactly how to tell JSF to evaluate it.  That said, I can imagine a component that would take the resource path, grab the markup and evaluate it, returning the completed markup, I just don't know how to implement that.</p>
  
  <p>I'd rather avoid forcing module developers to go the heavy duty UIComponent approach if possible, which means either a dynamic way of doing ui:include (or some equivalent) or a dynamic way of invoking CCs. (I don't mind coding the UIComponent approach ONCE in the application if that's what it takes to make module developers' lives easier)</p>
  
  <p>Any suggestions on where I should look to figure this out?  (I'll post the answer here if I find it first)</p>