}Barry van Oven <[EMAIL PROTECTED]> wrote: }> I'm having a problem with mm:import declared in an mm:include. }> }> If I place the mm:import (let's call it myImport) just }below the cloud }> tag, then do stuff with it in an include, everything }works fine. If I want }> to declare myImport in the include itself, however, }Tomcat reports that }> myImport is not a registered object. } }I don't quite understand. I think you should not see object in the }mm:include. }The inverse should certainly not work.
True. The result I was seeing, came from the first mm:import, not from something the include had done with it. }> Does this have anything to do with the context of }myImport, when declared }> in an include? I though imports in an include were as }much part of the }> page context as imports declared in the page itself... } }I hardly think so, while mm:include-d pages are stand-alone. With some help I found the solution to be a simple @include, instead of mm:include. Setting the context for the included mm:import's to pageContext would have been a possibility, although somewhat hackish... Regards, B.
