Problem in calling a JSP using cgi-callout

TS 6.7.2 / Windows 2003

Hi,

We are in the process of migrating from TS 6.1 to TS 6.7.2 with a fresh install of TS 6.7.2 on new server.

When I migrated the store and tested the DCTs, I found that instead of executing the .jsp file that is called when I click a cgi-callout button, the server returns the whole JSP code. When I view source, I could see all the JSP tags in it. This JSP file is available in location - iw-home\httpd\webapps\custom\templating\single_file_upload\index.jsp

The URL specified in the template is - "/iw/custom/templating/single_file_upload/index.jsp"

Can you tell me which configuration would enable execution of JSP files?

Find more posts tagged with

Comments

AdarshKukanur

Hey ,

Even I am facing a similar issue. Did u fina any solution to the above ?

Adam Stoller

Hey ,

Even I am facing a similar issue. Did u fina any solution to the above ?

After almost 4 years I'd hope they found a solution - whether or not they're still paying attention to devnet and if so, whether or not they still remember the problem and the solution - is a bigger question.

sheikh1

I did tried copying jsp to to customer_src and doing make_toolkit but it didn't worked.

-Sheikh

Rick Poulin

My first thought is that there must be a misconfiguration of your servletd and/or your JSPs are not at a path that's forwarded to the servletd. Is this the only (custom) JSP that isn't being rendered as such?

BTW, the answer to the original poster's question is exactly that -- his path isn't one that's forwarded to Tomcat.
(/iw/custom/templating/single_file_upload/index.jsp)
The /iw/ folder is handled direcly by Apache (iwwebd) which is why it's being handed back as-is. By putting it in customer_src, your path to the JSP should start with /iw-cc/, which IS forwarded to Tomcat.

AdarshKukanur

Copy yr jsp to customer_src/web and run maketoolkit . It will work!!!

Dhru

Migrateduser

Sir! you are out of the servletd context! That being, if you wish to run a jsp, you need to place it at one of the locations specified under server.xml under servlet folder in iw-home.
As pointed out, placing your custom code in a toolkit like customer_src should do the trick!