try $this->getApplication()->getResource('view'). getApplication() in the
module bootstrap returns the main application bootstrap.
$this->getResource('frontController') works because the module bootstraps
register their own frontController plugin. since there's only one front
controller anyway, they all return the same thing and the registerPlugin
would still work.
-- Mon
On Wed, Feb 3, 2010 at 1:03 PM, Hector Virgen <[email protected]> wrote:
> Sorry to bring up an old topic but I'm running into an issue trying to
> accomplish this.
>
> I have a module bootstrap that is throwing an exception when I try to
> access the "view" resource. Any idea what I might be doing wrong?
>
> http://pastie.org/807111
>
> --
> Hector
>
>
>
> On Sun, Dec 20, 2009 at 1:34 PM, Matthew Weier O'Phinney <[email protected]
> > wrote:
>
>> -- Ant Cunningham <[email protected]> wrote
>> (on Sunday, 20 December 2009, 01:09 PM -0500):
>> > Im currently porting a 1.7 version of an application to 1.9 and
>> > trying to make use of the Module bootstrapping, but i think im
>> > confused on a key point...
>> >
>> > I have a few view helpers that are actually used by the Layout but
>> > are in a "module namespace" (MyModule_View_Helper_*) as opposed to a
>> > "global namespace" (My_View_Helper_*). They dont seem to be
>> > available by default for the Layout to use when using the module
>> > autoloader resource.
>> >
>> > I was under the impression the module bootstrapping process front
>> > loaded all the resources for all modules (or in my case all enabled
>> > modules). Is this not the case or am i doing it wrong?
>>
>> Module bootstrapping sets up autoloading, but it doesn't automatically
>> add view helper/script/filter paths to the view; that must be done
>> manually currently.
>>
>> (Autoloading !== plugin loading, though the latter is affected by the
>> former.)
>>
>> --
>> Matthew Weier O'Phinney
>> Project Lead | [email protected]
>> Zend Framework | http://framework.zend.com/
>>
>
>
