Home/ Questions/Q 6365847
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T00:20:46+00:00

I am running the Java Pet Store example and this is the top part

  • 0

I am running the Java Pet Store example and this is the top part of my “index.jsp” file :

<%-- Copyright 2006 Sun Microsystems, Inc. All rights reserved. You may not modify, use, reproduce, or distribute this software except in compliance with the terms of the License at: http://developer.sun.com/berkeley_license.html
$Id: index.jsp,v 1.20 2007-03-16 20:18:59 basler Exp $ --%>

<%@page contentType="text/html"%>
<%@page pageEncoding="UTF-8"%>
<%@page import="java.util.*, com.sun.javaee.blueprints.petstore.model.CatalogFacade, com.sun.javaee.blueprints.petstore.model.Tag"%>

<%
try {
    CatalogFacade cf = (CatalogFacade)config.getServletContext().getAttribute("CatalogFacade");
    List<Tag> tags=cf.getTagsInChunk(0, 12);
    // since top 20 come from database or desending refCount order, need to reorder by tag name
    Collections.sort(tags, new Comparator() {
        public int compare(Object one, Object two) {
             int cc=((Tag)two).getTag().compareTo(((Tag)one).getTag());
             return (cc < 0 ? 1 : cc > 0 ? -1 : 0);
        }
    });    
%>

<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html;charset=utf-8" >
        <title>Java Pet Store Reference Application</title>
        <link type="text/css" rel="stylesheet" href="./tag.css"/>
    </head>
    <body>

….

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is not a direct answer to your question, but I’ll attempt to show what goes on to render a JSP. Following that path, and analysis of domains/domain1/server.log (if your installation is using the default domain called domain1) might give you a hint on what’s wrong.

    Normally in a GF2 there’s a file called default-web.xml in the domain’s config directory.

    It contains these snippets:

      <servlet>
    <servlet-name>jsp</servlet-name>
    <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
    <init-param>
      <param-name>xpoweredBy</param-name>
      <param-value>true</param-value>
    </init-param>
    <load-on-startup>3</load-on-startup>
  </servlet>

    The above code configures JSP support – of course it will fail if it cannot locate the servlet code, but that should be logged in server.log.

    After that, the following snippets ensure that the above servlet is called to manage jsp’s – one mapping for “classic” jsp’s and one for “xml syntax” jsps.

      <servlet-mapping>
     <servlet-name>jsp</servlet-name>
     <url-pattern>*.jspx</url-pattern>
  </servlet-mapping>


  <!-- ================ Built In Servlet Mappings ========================= -->


  <!-- The mapping for the JSP servlet -->
  <servlet-mapping>
    <servlet-name>jsp</servlet-name>
    <url-pattern>*.jsp</url-pattern>
  </servlet-mapping>

    Now, if for whatever reason these segments are missing in default-web.xml, jsp support will be inactive, and you’ll get an effect like the one you describe because the file will be picked up by the default servlet, and will be handled as a static resource.

    • 0