Thanks Tobias!

Another problem I just found, which may be related, is with the new UUID
Redirection, where the redirection doesn't include the context path. This
may be fixed with recent changes, but can you double check as I also noticed
the UuidRedirectView uses the LinkUtil.convertUUIDtoURI() which means it
doesn't add the context path anyway.

I tried to implement my own version which used
"LinkTransformerManager.getInstance().getAbsolute(true)" instead, but then
hit the same problem as before with the ForwardRequestWrapper. :)


Cheers,
 Brad

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Tobias Mattsson
Sent: Tuesday, 4 January 2011 12:50 AM
To: Magnolia User-List
Subject: Re: [magnolia-user] Blossom 1.2 with ForwardRequestWrapper issue


Hi Brad,

The ForwardRequestWrapper is added to simulate a forward operation on the
request. When blossom renders it calls into a DispatcherServlet that isnt
mapped in web.xml and therefor it applies a request wrapper that simulates a
forward operation on for instance /contactForm. In this process there's no
need for a context path but as you point out it needs to be visible later in
the process, for instance in jsps, when outputting links. I will add the
context path. The second problem you're having is indeed a bug, the wrapper
is too sensitive to changed values in its parent request.

Both these issues have been fixed in trunk, expect a bug fix release in a
few days.

Cheers,

// Tobias

On Jan 2, 2011, at 5:38 AM, Brad Kazazes wrote:

> 
> Hey Magnolians,
> 
> Happy New Year to all!
> 
> I seem to be having problems accessing the origal request paths in my JSP
> views when using Blossom 1.2 due to the new ForwardRequestWrapper class.
> 
> There are two issues caused by the same problem:
> 1) ${ctx.contextPath} returns an empty string all the time
> 2) The spring form:form taglib always sets the action to the spring
> @RequestMapping value instead of the original URL
> 
> When debugging, I can see that the ForwardRequestWrapper has the values
I'm
> after in the original* properties, but I can't access them.
> 
> Is there a setting I'm missing so I can access these, or is a possible
> oversight in version 1.2?
> 
> 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]>
> ----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to