RE: JSPF on WAS

Thanks, Gary.

I set up the <jsp-config> element in the web.xml file and all is well.
That method is more portable than editing the ibm-web-ext.xmi file since
the latter only applied to WAS.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx




"Gary L Peskin"
<garyp@firstech.c
om> To
Sent by: "'Java Programming on and around
java400-l-bounces the IBM i'"
@midrange.com <java400-l@xxxxxxxxxxxx>
cc

2011-01-28 15:19 Subject
RE: JSPF on WAS

Please respond to
Java Programming
on and around the
IBM i
<java400-l@midran
ge.com>






Sorry, Todd. I missed your reply on Wednesday so I'm glad that you sent
this again. The additional information that you provided on Wednesday was
very helpful. The JSP engine is set up to compile the four extensions:
.jsp, .jspx, .jspw, and .jsv. To add .jspf to this list, specify the .jspf
extension for the jsp.file.extensions parameter in the JSP engine
configuration or create a <jsp-property-group> in web.xml and add a
<url-pattern> for *.jspf.

The following should be helpful:

http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=w

as-nd-iseries&topic=rweb_jspengine
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=w

as-nd-iseries&topic=tweb_jspengine
JavaServer Pages specification Chapter JSP.3 (look at JSP.3.3 and
JSP.3.3.6)

Gary

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of TAllen@xxxxxxxxxxxx
Sent: Friday, January 28, 2011 11:02 AM
To: Java Programming on and around the IBM i
Subject: RE: JSPF on WAS

Has anyone using Websphere been able to use the JSPF extension? The
file is included but all JSP code is ignored. I don't know if this is
unsupported or there is a setting that must be changed.

Thanks,
Todd




TAllen@edpstech.c
om
Sent by:
To
java400-l-bounces Java Programming on and around
the
@midrange.com IBM i <java400-l@xxxxxxxxxxxx>

cc

2011-01-26 16:35
Subject
RE: JSPF on WAS

Please respond to
Java Programming
on and around the
IBM i
<java400-l@midran
ge.com>






Changing the extension from .jspf to .jsp makes everything works fine.
Below is a snippet.

<jsp:include page="included.jspf" flush="true">
<jsp:param name="parm" value="<%= value %>" />
</jsp:include>

In the "included.jspf" file:

<%
String parmValue = request.getParameter("parm");

%>

With the JSPF extension the last code snippet is displayed in the
browser, like it was never interpreted.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx




"Gary L Peskin"
<garyp@firstech.c
om>
To
Sent by: "'Java Programming on and around
java400-l-bounces the IBM i'"
@midrange.com <java400-l@xxxxxxxxxxxx>

cc

2011-01-26 16:09
Subject
RE: JSPF on WAS

Please respond to
Java Programming
on and around the
IBM i
<java400-l@midran
ge.com>






Can you be more specific about what directives are being ignored in your
included .jspf files? If you're including them with a "<%@ include"
directive, they should be treated as if the source as included in your
original .jsp file.

If you copy/paste the text from the .jspf file into the .jsp file
itself, does that work?

Gary

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of TAllen@xxxxxxxxxxxx
Sent: Wednesday, January 26, 2011 11:53 AM
To: Java Programming on and around the IBM i
Subject: JSPF on WAS

Does Websphere support the .jspf extension? I am using WAS 6.1 and it
appears to ignore all directives in files with a JSPF extension, In
my case the JSPF file is included by a JSP.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx

This communication and any transmitted documents are intended to be confidential. If there is a problem with this transmission, please contact the sender. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.