Hey Magnolians,
Ive hit a problem when attempting to use the latest versions of the
Magnolia, STK and Blossom where the Spring DispatcherServlet is throwing a
NullPointerException on all my Blossom paragraphs due to the
WebContext.Response being null.
After a bit of debugging, I noticed that the cause of this was that the
WebContext instance being used at the Blossom/Spring level was the same
instance created through the STK/FreeMarker Dispatcher; which, based on the
FreeMarker HttpRequestHashModel class, is an instance without a Response.
What I cant seem to work out is the difference between Magnolia 4.3.8 and
4.4.1 as the earlier version uses the same FreeMarker WebContext, but
somewhere before it gets to Blossom, it has either been popped back to a
previous WebContext or a new WebContext has replaced the previous one -
either way it has a Response.
There is a little too much code for me to step through to work it out
exactly, so I'm hoping someone who knows that code a bit better may have a
better idea of what's happening and either let me know if I missed something
in my update process, or if this is a bug with either Magnolia, STK or
Blossom. For now I've switched back to Magnolia 4.3.8 which is working fine.
Please let me know if you need any specific information about my code,
configuration, etc.
Cheers,
Brad
Brad Kazazes | Bundles IT
W: (03) 9600 4424 | M: 0402 018 722 | E: [email protected]
Melbourne, VIC, 3000
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
