Now that I've gotten Velocity templates working properly with Liferay, I need to be able to create URLs within the portal. I understand how to do that, e.g.:



The problem is that I don't know how to get at the response object in the default Velocity environment. I'm assuming that there's some way to do this, similar to how you can just reference the request and response objects in JSP pages:



I've worked around it for now by explicitly adding the renderResponse object to the model data in my portlet controller:



But I'd really rather not have to do this in every single one of my controllers. Is there a way to get at this stuff through Velocity and/or some type of context or configuration that's automatically set up in the template?

According VelocityVariablesImpl it should be exposed by renderResponse;

Thanks Corné,

I had seen that elsewhere (not sure where) and tried to use that in my template. To test it, I put this into my template:



This gives me this output:



Am I maybe missing some kind of activation or configuration that will make this work?

Also, it's worth noting that I'm not going through the Liferay Velocity stuff, which I mostly see referenced in regard to theming, but instead through the Spring Framework VelocityViewResolver. I'm guessing that's affecting it, but I'm not sure how to bring those two worlds together.

Sorry i'm mistaken;

There are 4 different Variable insert functions;
insertHelperUtilities(VelocityContext, String[])
insertHelperUtility(VelocityContext, String[], String, Object)
insertTilesVariables(VelocityContext, HttpServletRequest)
insertVariables(VelocityContext, HttpServletRequest)

This is helpful;
http://docs.liferay.com/portal/5.2/javadocs/portal-impl/com/liferay/portal/velocity/VelocityVariables.java.html
explore velocity variables

Hi Rick,

The way we use request and response in JSP's is similar in Velocity as well. Just the syntax differs

for eg:



So coming to your example,

You can always set Model attributes map and get the object,



here you have added response object to the map - Request and Response are implicit objects for any server side templating mechanisms. You need not pass it. You have them available all the time in your velocity context

Think that you will be adding some other object say <b>userDetails</b> to the Model Map.

Now it is easier to access userDetails in Velocity like below

#set($first_name = $userDetails.getFirstName())

#set($last_name = $userDetails.getLastName())

Spring will make the things happen in the background.

HTH,
Sharan

That's what I would expect, but that's not what I'm seeing unfortunately. I've attached a sample project that tries to access the response through both $response and $renderResponse. Here's the code in the Velocity template:



The results of this are:





Right and that's basically what works if I explicitly add the response to the model map returning from the controller, but like you say I shouldn't need to do that.

Thanks for the help on this, I do appreciate it!

Attachments:

LiferayMavenProject-portlet.zip (11.2k)