× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Follow up...

I have found the problem with the test evironment.  There is a section of
the default_app.webapp file that specifies the JSP processor to use.

 <servlet>
      <name>jsp</name>
      <description>JSP support servlet</description>

      <!--
                        ***
                        *** Replace the JSP compiler with the required
specification level.
                        ***

                        *** JSP 0.91 Compiler ***

<code>com.ibm.ivj.jsp.debugger.pagecompile.IBMPageCompileServlet</code>

                        *** JSP 1.0 Compiler ***
      <code>com.ibm.ivj.jsp.runtime.JspDebugServlet</code>

                        *** JSP 1.1 Compiler ***
      <code>com.ibm.ivj.jsp.jasper.runtime.JspDebugServlet</code>
      -->
      <code>com.ibm.ivj.jsp.jasper.runtime.JspDebugServlet</code>

      <init-parameter>
         <name>workingDir</name>
         <value>$server_root$/temp/default_app</value>
      </init-parameter>
      <init-parameter>
         <name>jspemEnabled</name>
         <value>true</value>
      </init-parameter>
      <init-parameter>
         <name>scratchdir</name>
         <value>$server_root$/temp/JSP1_0/default_app</value>
      </init-parameter>
      <init-parameter>
         <name>keepgenerated</name>
         <value>true</value>
      </init-parameter>
      <autostart>true</autostart>
      <servlet-path>*.jsp</servlet-path>
   </servlet>

I changed this to the JSP 1.1 compiler and it works ok now.

-----Original Message-----
From: Gary L Peskin [mailto:garyp@firstech.com]
Sent: Monday, June 17, 2002 4:35 PM
To: java400-l@midrange.com
Subject: RE: Using Custom JSP tags in WebSphere 3.5.3


Stephen --

What JSP processor are you using?  In the administrative console, you
should be able to look in the "Configure resources" section of your
administrative console to find the name/version of your JSP enabler for
the Web application that is giving you this error message.

Gary

> -----Original Message-----
> From: java400-l-admin@midrange.com
> [mailto:java400-l-admin@midrange.com] On Behalf Of Gibson.Stephen
> Sent: Monday, June 17, 2002 12:30 PM
> To: 'java400-l@midrange.com'
> Subject: RE: Using Custom JSP tags in WebSphere 3.5.3
>
>
> David,
>
> Thanks for the response.  I created a JSP from the sample
> code you sent me, When I run the JSP I get the same error I
> descibed previously:
>
> Error 500
> An error has occured while processing
> request:http://localhost:8080/StrutsTest.jsp
> Message: "Directive: Invalid attribute, prefix"
> ...

_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.