Calling a custom JSP in the teamsite runtime, exceptions being thrown

simplepieman

Hi, I apologise as I'm very new to Teamsite but my question is what is the correct procedure to add a custom JSP to the teamsite runtime (Teamsite 7.4.1)? We call this JSP from a DCT and we are seeing a ClassNotFoundException in the logs after we've run make_toolkit.ipl i.e. :

 

java.lang.ClassNotFoundException: com.interwoven.custom.my_jsp

 

If we run build.sh, we see :

[/iw-cc].[com.interwoven.custom.my_jsp]] Servlet com.interwoven.custom.my_jsp is currently unavailable

 

We've added our custom JSP to:

 

content_center/customer_src/web/custom/my.jsp

 

We also have other custom JSP's which are served correctly, however these were added by colleagues no longer in the company.

And looking through the filesystem we see that the built war file (iw-cc.war) contains the JSP i.e. in:

 

server/default/deploy/iw-cc.war/custom/

 

However, after looking at the web.xml deployment descriptor we noticed something strange. We see a servlet being declared for our JSP i.e. :

 

<servlet>
   <servlet-name>com.interwoven.custom.my_jsp</servlet-name>
   <servlet-class>com.interwoven.custom.my_jsp</servlet-class>
</servlet>

 

and a servlet url mapping for:

 

<servlet-mapping>
   <servlet-name>com.interwoven.custom.my_jsp</servlet-name>
   <url-pattern>/custom/my.jsp</url-pattern>
</servlet-mapping>

 

 

No other custom JSP's are declared other than our new JSP and this is obviously why we're seeing CNFE's (also the interwoven package is being added).

 

So it appears we're missing a step. After searching some posts we wondered whether we instead need to run install_webapps.ipl however we're not clear exactly what it does. The HP documentation we have mentions it but doesn't go into detail. 

 

So before I go looking through the various perl scripts and ant tasks any help would be appreciated.

Thanks

Lee

simplepieman

Ok I think I know what needs to be done. 

 

It appears whenever you add a new servlet or jsp, you also need to add it to the deployment descriptor in content_center/customer_src/ which makes sense. I'd guess that because I haven't done this, when the iw-cc.war war is created the build script assumes it's not custom code and appends a default package name?

 

Also, I'm assuming the web.xml for custom code is mixed in to the product's web.xml by the build script with the additional custom configuration.

 

I also noticed there is documentation on this in the UI customisation document, so apologies. 

I'll mark as solved tomorrow when I try out

 

Lee