Hi, Thanks for your concern! Through some test I think as you do that this is just an order matter (i.e.: being sure a component bas been initialized properly through the system container id. in order to use them in some sub containers).
I only found references to app and sub-app container definition in the magnolia docs > 5. In magnolia 4.5.15 I was only able to define components in the container platform/system/main. I'd hope that I could somehow define a component only available in the scope of a specific module without changing the default behaviour/expectations of other project's dependencies. Let's wait for feedback from a magnolia expert :-) Kr B. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=9e3dd8a9-c3e2-48fb-b0a6-35b3e2539ab8 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
