Hi Cristian, Either Magnolia has failed to start like the exception message says or things are starting in the wrong order.
One situation where I expect this to happen is if you've configured BlossomDispatcherServlet in web.xml. It shouldn't be configured in web.xml as its not supposed to handle requests from outside, not even internal forward request. It is called directly from within rendering. The proper way of setting it up is detailed on the documentation site [1]. The sample webapp [2] have it done that way, have a look at the sources. [1] http://documentation.magnolia-cms.com/modules/blossom.html#Ownmodulerecommended [2] http://documentation.magnolia-cms.com/modules/blossom.html#GettingStarted Regards, Tobias Mattsson Senior Software Engineer Magnolia International Ltd. On Dec 13, 2011, at 8:31 AM, Magnolia Forums (on behalf of Cristian ) wrote: > can anyone told me why this is can be happen? > > -- > Context is everything: > http://forum.magnolia-cms.com/forum/thread.html?threadId=4cdae7b1-baba-480f-a413-f932acfa17f3 > > > ---------------------------------------------------------------- > 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]> > ---------------------------------------------------------------- ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
