Win a copy of The Business Blockchain this week in the Cloud forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Error: renderRequest cannot be resolved

 
pulijala hari
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am newly developing JSR 168 portlets.
while i try to use renderRequest object, i am getting an error renderRequest cannot be resolved. I tried for portlet.tld on the net.

Does any body have the links to download JSR 168 portlet jars and portlet.tld files?
 
Ryan Wilson
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I assume this post is related to you other about where to find the portlet.tld.

Are you getting these errors while running on the server or only in the RAD environment?
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here's a tutorial that demonstrates how to create and develop a simple JSR168 portlet using Notepad, the JDK and JetSpeed2

Creating, Compiling and Deploying a Simple JSR-168 Portlet using JetSpeed2

Regardless of whether you are using JetSpeed2 or not, this tutorial demonstrates how to add the appropriate jar files to your classpath, and allow your portlet to run. The appropriate libraries are supplied with JetSpeed2 when you download and install it. With WebSphere, they come packaged along with the WebSphere Portal Development Toolkit.

Good luck!

-Cameron McKenzie
 
pulijala hari
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i am getting the error only in the RAD environment, not on the server.
Can i still continue my work using renderRequest in my portlet although the error exists only in the RAD?
 
Ryan Wilson
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hariprasad this is only a validation error in RAD. You will be fine if you continue developing your portlet. The tld will be correctly resolved during runtime.
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Heh, I was thinking the same thing.

Even though everything is in place, the JSP editor coughs up on the custom tags, and it's not allowing you to reference the renderRequest or renderResponse, or any of those 'implicit objects' that are supposedly available if use the portlet custom tags.

If you look at a few of my tutorials on creating JSPs with IRAD on my website (check out my signature links), you'll see the same error message. Still, when I deploy the apps, they all deploy fine.

-Cameron
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic