Static compiles do not seem to include JSP's?

With wl 510/sp6 and using the command line: java weblogic.jspc
          exceptionHandler.jsp any included files using the directive like: <%@
          include file="style.jsp" %> do not seem to be found.
          The resulting java has the following in it:
          try { // begin check exception try block
          out.print(" \n");
          out.print("\n");
          out.print("\n");
          out.print("\n");
          out.print("\n");
          out.print("\n");
          // cannot include file 'style.jsp' //[
          /exceptionHandler.jsp; Line: 16]
          //[ /exceptionHandler.jsp; Line: 17]
          out.println(""); //[ /exceptionHandler.jsp; Line: 16]
          //[ /exceptionHandler.jsp; Line: 17]
          out.print("\n\n\n");
          //[ /exceptionHandler.jsp; Line: 19]
          A sinple ls -alt shows the file to be there in the tree.
          Any ideas?

Similar Messages

Static variable could not seem as attribute in JMX

Hi,
I defined a Global class and I have a static variable. I could not see them as attribute in jConsole. BTW, the methods could seem in jconsole. And, I used the class includes static variables as a Global class.
How can i see the static variable in jconsole?

Global class is a final Class it is not be instantiated.
Static variables should be accessible because I want to monitor something ( for example file processing time or file sending time .. ). I set the variable as average time of file processing and I would like to monitor in jmx.
In application-context xml in spring environment I represent the bean as mbean as below :
     <bean id="exporter3" class="org.springframework.jmx.export.MBeanExporter" lazy-init="false">
     <property name="beans">
          <map><entry key="bean:name=Global" value-ref="Global"/></map>
     </property>
     </bean>

Ant autotype does not seem to recognize xsd:include

Hi
I am currently using WebLogic 7.0. I was trying to use ant autotype to generate
java classes based on a schema. I ran into a problem that the autotype does not
seem to include the other schema files listed with xsd:include. I could only get
around the problem by literally copy and paste the complex types definition into
the calling schema file. Below are the two schemas that illustrate the problem.
x.xsd includes y.xsd but however the EmployeeBean listed in y.xsd results in a
unresolve type with autotype. Problem only goes away if EmployeeBean definition
is listed in x.xsd.
Any help is much appreciated.
==========================================================
x.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema xmlns:ofx="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://ofx.net/v3.0">
<xsd:include schemaLocation="y.xsd" />
<xsd:complexType name="Company">
<xsd:sequence>
<xsd:element name="XYZ" type="ofx:EmployeeBean" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
==========================================================
y.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema targetNamespace="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ofx="http://ofx.net/v3.0">
<xsd:complexType name="EmployeeBean">
     <xsd:sequence>
     <xsd:element name="name"
          type="xsd:string"
          nillable="true"
          minOccurs="1"
          maxOccurs="1">
     </xsd:element>
     <xsd:element name="id"
          type="xsd:int"
          minOccurs="1"
          maxOccurs="1">
     </xsd:element>
     </xsd:sequence>
</xsd:complexType>
</xsd:schema>
=============================================================

Actually imports will work in most cases, though some bug fixes have
been made since and will show up in future releases.
--Scott
In article <[email protected]>,
Bruce Stephens <[email protected]> wrote:
Hello,
At the moment, we handle wsdl imports as done by SOAPBuilders Round
3, but not schema imports. Look for this in the upcoming release;
Contact Michael Bamford ([email protected]) if you would like
to be on the Beta.
Thanks,
Bruce
Sooleng Lau wrote:
Thank you for the response and info. What about schema import, is
it handled by weblogic 7.0 at the moment ? What is the upcoming
release, is it WebLogic 7.1 ?
Thank you.
Soo Leng
Bruce Stephens <[email protected]> wrote:
Hello,
Schema include is a known problem that will be corrected in the upcoming
release.
The workaround at this point is the cut and paste :-( you described.
Bruce
Sooleng Lau wrote:
Hi
I am currently using WebLogic 7.0. I was trying to use ant autotypeto generate
java classes based on a schema. I ran into a problem that the autotypedoes not
seem to include the other schema files listed with xsd:include. I couldonly get
around the problem by literally copy and paste the complex types definitioninto
the calling schema file. Below are the two schemas that illustratethe problem.
x.xsd includes y.xsd but however the EmployeeBean listed in y.xsd resultsin a
unresolve type with autotype. Problem only goes away if EmployeeBeandefinition
is listed in x.xsd.
Any help is much appreciated.
==========================================================
x.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema xmlns:ofx="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://ofx.net/v3.0">
<xsd:include schemaLocation="y.xsd" />
<xsd:complexType name="Company">
<xsd:sequence>
<xsd:element name="XYZ" type="ofx:EmployeeBean" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
==========================================================
y.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema targetNamespace="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ofx="http://ofx.net/v3.0">
<xsd:complexType name="EmployeeBean">
<xsd:sequence>
<xsd:element name="name"
type="xsd:string"
nillable="true"
minOccurs="1"
maxOccurs="1">
</xsd:element>
<xsd:element name="id"
type="xsd:int"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
=============================================================

How do I add an included jsp to my project and not get a compile error?

Hi,
I have a project with some included jsp's however if I add them to the project, when I build I get a compile error as the jsp uses variables from the calling jsp.
Any ideas on how to get round this.
Thanks
DM

There are two main ways that I deal with this problem (yeah, it sucks, but it sort of makes sense that it happens...) (I presume you're talking static include here...)
#1 - name the included file with an extension that JDev will not try to compile (.jspf - for JSP Fragment - is common) Then it will be compiled in with the including page, but won't gag the project compilation. Advantage - it works, and you find out at compile time if you hosed up the variable reference. Disadvantage: JDev tries really, really, really hard to keep you from naming a JSP file with an extension of .jspf I normally create the .jsp file in JDev, remove it from the project, rename the file outside of JDeveloper, then add it back to the project - pain in the butt, but it works (and you probably aren't building scads of these included files...)
#2 - add the variable to be referenced to the pageContext implicit object as an attribute in your including page (ex, <% pageContext.setAttribute("myVar", myVar); %>), then reference that attribute in your included JSP (ex, <%= pageContext.getAttribute("myVar") %>) . It will compile fine (as the compiler has no way of knowing if the pageContext attribute actually exists, it just sees that the syntax is good and motors along merrily. Advantage: don't have to have differently named JSP files (which isn't actually a big deal). Disadvantage: You hvae to add the variable to the pageContext (and you have to always add Object derivatives, as primitives won't go into a hash) and you don't find out if you screwed the variable up until runtime (when it tries the getAttribute, which could return null if you didn't properly set it to start with) vs at compile-time w/ the direct reference.
HTH!
Jim

Preventing the compilation of included .jsps

Hi,
          I am using WLS 5.1sp9
          We have the constraint of compiling our .jsps when weblogic is started, not
          at request time. And we need to use the include directive for some of the
          .jsps, as the included
          .jsps contains references to objects that are declared in the includeing
          .jsp, our included
          .jsps do not compile and that stucks weblogic initialization.
          Here is a simple example:
          a.jsp
          <% int toto = 123; %>
          <%@ include file="includes/myInclude.jsp"%>
          myInclude.jsp
          <b> <%= toto%><b>
          Of course myInclude.jsp cannot be compiled on its own, so we named it
          myInclude.inc, which works but is unelegant.
          Is there a way to still give the .jsp extension to the included file but
          prevent it from being
          compiled by WLS ?
          Cheers,
          Marc.


          No. Nothing more elegant that naming them .inc.
          Mike
          "Marc-Andre Fontaine" <[email protected]> wrote:
          >Hi,
          >I am using WLS 5.1sp9
          >We have the constraint of compiling our .jsps when weblogic is started,
          >not
          >at request time. And we need to use the include directive for some of
          >the
          >..jsps, as the included
          >..jsps contains references to objects that are declared in the includeing
          >..jsp, our included
          >..jsps do not compile and that stucks weblogic initialization.
          >
          >Here is a simple example:
          >a.jsp
          >....
          ><% int toto = 123; %>
          ><%@ include file="includes/myInclude.jsp"%>
          >....
          >----
          >myInclude.jsp
          >....
          ><b> <%= toto%><b>
          >....
          >
          >Of course myInclude.jsp cannot be compiled on its own, so we named it
          >myInclude.inc, which works but is unelegant.
          >Is there a way to still give the .jsp extension to the included file
          >but
          >prevent it from being
          >compiled by WLS ?
          >
          >Cheers,
          >Marc.
          >
          >

Included JSPs not displaying anything

Hi there
I'm using the JSP directive to include a small JSP into the main one, using
<jsp:include page="/Summary.jsp">
Everything was working fine until I did a change in the Summary.jsp and the included page just stopped generating the HTML. I have a feeling that it is a compilation error, but I just don't get anything in the screen or in the console window for catalina.
I tried using the <%@ page errorPage="/DisplayException.jsp"%> in the included jsp (Summary.jsp) but the redirection does not happen at all.
Do I have to turn some kind of flag in Tomcat to see the errors (either compilation or runtime) that happen in the included JSPs?
I'm using Tomcat 5.0.27 and JDK 1.5 running on Windows.
Thanks in advance for your time and help
Leo.

The problem is that you are getting an error after
the response is already committed (HTML is already
written to the client machine). That means that the
server can not redirect to the error page.
Your option are to make sure that you do not flush
the output buffer when you do the include:
<jsp:include page="..." flush="false"/>
and make sure that the page that is doing the include
has a big enough buffer:
<%@page buffer="20kb" %> (at the top of the page)
Setting this high enough should make sure that your
response is not committed before your error occurs,
and so you should get redirected to the error page.
The higher it is set, though, the more memory your
r server will eat up, so remember to turn it back
down when debugging is done.Hi Steve
I did that and I could finally see the exception. Thanks a lot for your help
Leo.

Included JSP files not seeing JavaScript in main JSP file

Hi All,
I have a JSP page that defines a JavaScript block in it's HEAD block and then includes multiple JSP pages in it's BODY block. Calling a JavaScript function from any of the included JSP pages is met with the following JavaScript error:
JavaScript Error: [unknown origin]:
showBatchDetail is not defined.
I'm not sure what is wrong here since the JSP is generating on the server side and everything is fine by the time it gets to the client side. The entire client side file should be seeing the JavaScript block that was included in the main file.
Any help here would be much appreciated.
Steph.
Some barebones code appears below:
Main.jsp
<HTML>
<HEAD>
<TITLE>UNIT INFO</TITLE>
<SCRIPT LANGUAGE="JavaScript">
function showBatchDetail(batchKey)
var url = "/pditools/html/SfmReports/ShowBatchDetail.jsp"
+ "?batchKey=" + batchKey;
document.location = url;
</SCRIPT>
</HEAD>
<BODY>
<%@include file="ShowBatchSummary.jsp"%>
<%@include file="ShowUnitDefects.jsp"%>
<%@include file="ShowUnitHistory.jsp"%>
</BODY>
</HTML>
ShowBatchSummary.jsp
<TABLE>
<TR>
<TD>
BATCH SUMMARY
<A TARGET="_blank" HREF="JavaScript:showBatchDetail(1000);">(Batch Detail)</A>
</TD>
</TR>
<TR>
Show some data ...
</TR>
</TABLE>

The problem is not about include but about link use
----ShowBatchSummary.jsp----
<TABLE>
<TR>
<TD>
BATCH SUMMARY
<A TARGET="_blank" HREF="#" onclick="JavaScript:showBatchDetail(1000);">(Batch Detail)</A>
</TD>
</TR>
<TR>
Show some data ...
</TR>
</TABLE>
-------end of ShowBatchSummary.jsp--------

Include jsp tags

I am having a problem relacing the include file of let's call it a
header.jsp in a menu page named menu.jsp.
So in my header.jsp file let's say I do something simple like
<table>
<tr><td><jato:href name="first">First Option
</jato:href></td></tr></table>
and so on....
And in my main.jsp I have a simple include at the top of my page
like so
<html
<body>
<%include file=header.jsp%>
etc.
Now when JRun 3.0 makes the include replacement, it seems to have a
problem where it tells me
Servlet error 500
com.iplanet.jato.view href : taglib navigation not found
BUT when I take out the jato tags in the include file...I can get
JRun to make the replacement perfectly....
Does anyone else have this problem and if so how did you get around
it?

Sorry to bother you again, but I couldn't find anything that looked strange
is this file. Can you send us the original file at our personal email
addresses? I'd like to see exactly where the compilation error occurs and
it's not possible with the file inlined here.
todd.fast@e...
michael.frisino@s...
Thanks,
Todd
----- Original Message -----
From: <suket@u...>
Sent: Wednesday, January 17, 2001 2:02
Subject: [iPlanet-JATO] Re: include jsp tags
Hi Mike,
Both of the jsp files (pgHelp.jsp and pgFooter.jsp)
are in the same folder. I removed the IPP/ipp portion in the
include directive but still giving the same err.
iam using Allair Jrun 3.0.
Here is the intermediary generated Jsp file
/ Generated by JRun, do not edit
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
import allaire.jrun.jsp.JRunJSPStaticHelpers;
public class jrun__IPP__ipp__pgHelp2ejsp13 extends
allaire.jrun.jsp.HttpJSPServlet implements
allaire.jrun.jsp.JRunJspPage
private ServletConfig config;
private ServletContext application;
private Object page = this;
private JspFactory __jspFactory = JspFactory.getDefaultFactory();
public void _jspService(HttpServletRequest request,
HttpServletResponse response)
throws ServletException, java.io.IOException
if(config == null) {
config = getServletConfig();
application = config.getServletContext();
response.setContentType("text/html; charset=ISO-8859-1");
PageContext pageContext = __jspFactory.getPageContext(this,
request, response, null, true, 8192, true);
JspWriter out = pageContext.getOut();
HttpSession session = pageContext.getSession();
try {
out.print("\r\n\r\n");
IPP.ipp.pgHelpViewBean viewBean = (IPP.ipp.pgHelpViewBean)
pageContext.getAttribute("viewBean", PageContext.REQUEST_SCOPE);
if(viewBean == null) {
if(JRunJSPStaticHelpers.getAndSetBean(pageContext,
"viewBean", IPP.ipp.pgHelpViewBean.class
, PageContext.REQUEST_SCOPE, 3)) {
viewBean = (IPP.ipp.pgHelpViewBean)pageContext.getAttribute
("viewBean", PageContext.REQUEST_SCOPE);
} else {
viewBean = (IPP.ipp.pgHelpViewBean)pageContext.getAttribute
("viewBean", PageContext.REQUEST_SCOPE);
pageContext.setAttribute("viewBean",viewBean);
out.print("\r\n");
com.iplanet.jato.taglib.UseViewBeanTag useViewBean__4_1 =
(com.iplanet.jato.taglib.UseViewBeanTag)
JRunJSPStaticHelpers.createTagHandler(pageContext,
"com.iplanet.jato.taglib.UseViewBeanTag");
useViewBean__4_1.setPageContext(pageContext);
useViewBean__4_1.setParent(null);
useViewBean__4_1.setClassName("IPP.ipp.pgHelpViewBean");
int useViewBean__4_1_startVal = useViewBean__4_1.doStartTag();
JRunJSPStaticHelpers.checkStartVal
("com.iplanet.jato.taglib.UseViewBeanTag",useViewBean__4_1_startVal,Bo
dyTag.EVAL_BODY_INCLUDE,4);
if(useViewBean__4_1_startVal == BodyTag.EVAL_BODY_INCLUDE) {
com.iplanet.jato.view.ContainerView currentView =
(com.iplanet.jato.view.ContainerView)pageContext.getAttribute
("currentView");
com.iplanet.jato.view.TiledView currentTiledView =
(com.iplanet.jato.view.TiledView)pageContext.getAttribute
("currentTiledView");
out.print("\r\n<HTML>\r\n<HEAD>\r\n");
com.iplanet.jato.taglib.TextFieldTag textField__7_1 =
(com.iplanet.jato.taglib.TextFieldTag)
JRunJSPStaticHelpers.createTagHandler(pageContext,
"com.iplanet.jato.taglib.TextFieldTag");
textField__7_1.setPageContext(pageContext);
textField__7_1.setParent(useViewBean__4_1);
textField__7_1.setSize("20");
textField__7_1.setMaxLength("20");
textField__7_1.setFireDisplayEvents("true");
textField__7_1.setName("tbUserID");
textField__7_1.doStartTag();
if(textField__7_1.doEndTag() == Tag.SKIP_PAGE) {
if(true) return;
out.print("\r\n<TITLE>pgHelp</TITLE>\r\n</HEAD>\r\n<body BGCOLOR=
\"white\" bgcolor=\"#FFFFFF\" text=\"#000000\" link=\"#0000FF\" vlink=
\"#800080\" alink=\"#FF0000\">\r\n");
com.iplanet.jato.taglib.FormTag form__11_1 =
(com.iplanet.jato.taglib.FormTag)JRunJSPStaticHelpers.createTagHandler
(pageContext, "com.iplanet.jato.taglib.FormTag");
form__11_1.setPageContext(pageContext);
form__11_1.setParent(useViewBean__4_1);
form__11_1.setMethod("post");
form__11_1.setName("pgHelp");
int form__11_1_startVal = form__11_1.doStartTag();
JRunJSPStaticHelpers.checkStartVal
("com.iplanet.jato.taglib.FormTag",form__11_1_startVal,BodyTag.EVAL_BO
DY_INCLUDE,11);
if(form__11_1_startVal == BodyTag.EVAL_BODY_INCLUDE) {
out.print("\r\n");
if(form__11_1.doEndTag() == Tag.SKIP_PAGE) {
if(true) return;
out.print("\r\n");
com.iplanet.jato.taglib.UseContainerViewTag view__1_1 =
(com.iplanet.jato.taglib.UseContainerViewTag)
JRunJSPStaticHelpers.createTagHandler(pageContext,
"com.iplanet.jato.taglib.UseContainerViewTag");
view__1_1.setPageContext(pageContext);
view__1_1.setParent(null);
view__1_1.setName("IPP.ipp.pgFooterViewBean");
int view__1_1_startVal = view__1_1.doStartTag();
JRunJSPStaticHelpers.checkStartVal
("com.iplanet.jato.taglib.UseContainerViewTag",view__1_1_startVal,Body
Tag.EVAL_BODY_INCLUDE,1);
if(view__1_1_startVal == BodyTag.EVAL_BODY_INCLUDE) {
currentView = (com.iplanet.jato.view.ContainerView)
pageContext.getAttribute("currentView");
currentTiledView = (com.iplanet.jato.view.TiledView)
pageContext.getAttribute("currentTiledView");
com.iplanet.jato.view.ContainerView
IPP.ipp.pgFooterViewBean = (com.iplanet.jato.view.ContainerView)
pageContext.getAttribute("IPP.ipp.pgFooterViewBean");
out.print("\r\n<hr color=red size=2>\r\nfrom new_footer.jsp in
IPP/ipp directory\r\n<font size=\"-2\" face=\"Arial\"><i>Send
comments to <a href=\"mailto:supportdept@a...\">Any
Company</a></i></font>\r\n<hr color=red size=2>\r\n");
com.iplanet.jato.taglib.HiddenTag hidden__6_1 =
(com.iplanet.jato.taglib.HiddenTag)
JRunJSPStaticHelpers.createTagHandler(pageContext,
"com.iplanet.jato.taglib.HiddenTag");
hidden__6_1.setPageContext(pageContext);
hidden__6_1.setParent(view__1_1);
hidden__6_1.setFireDisplayEvents("true");
hidden__6_1.setName("hdFooter");
hidden__6_1.doStartTag();
if(hidden__6_1.doEndTag() == Tag.SKIP_PAGE) {
if(true) return;
out.print("\r\n");
if(view__1_1.doEndTag() == Tag.SKIP_PAGE) {
if(true) return;
out.print("\r\n");
out.print("\r\n</BODY> \r\n</HTML>\r\n");
if(useViewBean__4_1.doEndTag() == Tag.SKIP_PAGE) {
if(true) return;
} catch(Throwable t) {
if(t instanceof ServletException)
throw (ServletException) t;
if(t instanceof java.io.IOException)
throw (java.io.IOException) t;
if(t instanceof RuntimeException)
throw (RuntimeException) t;
throw JRunJSPStaticHelpers.handleException(t,
pageContext);
} finally {
__jspFactory.releasePageContext(pageContext);
public String getServletInfo()
return "pgHelp";
private static final String[] __dependencies__ =
{"/IPP/ipp/pgHelp.jsp",null};
private static final long[] __times__ = {979720473658L,0L};
public String[] __getDependencies()
return __dependencies__;
public long[] __getLastModifiedTimes()
return __times__;
public int __getTranslationVersion()
return 14;
it is generating 2 semicolons automatically..
near pageContext.getAttribute("IPP.ipp.pgFooterViewBean");
regards
ravi
In [email protected], "Mike Frisino" <Michael.Frisino@S...>
wrote:
Hi Suket,
I just retested something very similar to this in 1.0.
Essentially, i took an existing page which included a tiledView.
I moved the TiledView jsp block into an entirely separate jsp file.
I then replace the TiledView jsp block in the original jsp with aninclude
<%@ include file="TiledGetOrders.jsp"%>
It worked like a charm.
So I am not sure what is wrong in your case.
Could be a jrun bug?
I have tested in resin 1.2.1
To do proper analysis, we would need to see
1. The intermediary .java file that the jsp engine creates, andthen tries
to compile.
C:/Program
Files/Allaire/JRun/servers/default/ipp/WEB-INF/jsp/jrun__IPP__ipp__pgHelp2ej
sp.java
Can you send that to us?
Incidentally, although we do not think a problem there would causethe
compile time error you are seeing,
i am curious about your file value.
<%@ include file="/IPP/ipp/pgFooter.jsp"%>I did not need to use a qualified file name, although my includetarget file
was in the same directory as the
page that was including it. What is the file system relationshipbetween
your top level page "pgHelp" and the include
target "pgFooter".
Are they in same or diff directories?
----- Original Message -----
From: <suket@u...>
Sent: Tuesday, January 16, 2001 9:42 PM
Subject: [iPlanet-JATO] Re: include jsp tags
Hi,
We tried to follow the steps described by you to have
dynamic include in a jsp page.
my jsp file content is
<%@p... info="pgHelp" language="java"%>
<%@t... uri="/WEB-INF/jato.tld" prefix="jato"%>
<jsp:useBean id="viewBean" class="IPP.ipp.pgHelpViewBean"
scope="request"></jsp:useBean>
<jato:useViewBean className="IPP.ipp.pgHelpViewBean">
<HTML>
<HEAD>
<jato:textField name="tbUserID" size="20" maxLength="20"
fireDisplayEvents="true" />
<TITLE>pgHelp</TITLE>
</HEAD>
<body BGCOLOR="white" bgcolor="#FFFFFF" text="#000000"
link="#0000FF" vlink="#800080" alink="#FF0000">
<jato:form name="pgHelp" method="post">
</jato:form>
<%@ include file="/IPP/ipp/pgFooter.jsp"%>
</BODY>
</HTML>
</jato:useViewBean>
This is my pgFooter.jsp
<jato:view name="IPP.ipp.pgFooterViewBean">
<hr color=red size=2>
from new_footer.jsp in IPP/ipp directory
<font size="-2" face="Arial"><i>Send comments to <a
href="mailto:<a href="/group/SunONE-JATO/post?protectID=061075104115193209050223163176249165134048139046">supportdept@a...</a>">Any Company</a></i></font>
<hr color=red size=2>
<jato:hidden name="hdFooter" fireDisplayEvents="true" />
</jato:view>
There is no compilation error in pgFooterViewBean and in
pgHelpViewBean.
How ever iam getting a runtime error,
500 Internal Server Error
/ipp/servlet/IPP.ipp.ippServlet:
javax.servlet.ServletException: Compilation error occured:
allaire.jrun.scripting.DefaultCFE:
Errors reported by compiler:C:/Program
Files/Allaire/JRun/servers/default/ipp/WEB-
INF/jsp/jrun__IPP__ipp__pgHelp2ejsp13.java:105:50:105:50: Syntax:
expected instead of this token
What could be the reason for this error message?
We tried the same thing with another approach, instead of using
include directive, we directly copied the code of pgFooter.jsp in
pghelp.jsp.
even that is giving the same error..
<%@p... info="pgHelp" language="java"%>
<%@t... uri="/WEB-INF/jato.tld" prefix="jato"%>
<jsp:useBean id="viewBean" class="IPP.ipp.pgHelpViewBean"
scope="request"></jsp:useBean>
<jato:useViewBean className="IPP.ipp.pgHelpViewBean">
<HTML>
<HEAD>
<jato:textField name="tbUserID" size="20" maxLength="20"
fireDisplayEvents="true" />
<TITLE>pgHelp</TITLE>
</HEAD>
<body BGCOLOR="white" bgcolor="#FFFFFF" text="#000000"
link="#0000FF" vlink="#800080" alink="#FF0000">
<jato:form name="pgHelp" method="post">
</jato:form>
<jato:view name="IPP.ipp.pgFooterViewBean">
<hr color=red size=2>
from new_footer.jsp in IPP/ipp directory
<font size="-2" face="Arial"><i>Send comments to <a
href="mailto:<a href="/group/SunONE-JATO/post?protectID=061075104115193209050223163176249165134048139046">supportdept@a...</a>">Any Company</a></i></font>
<hr color=red size=2>
<jato:hidden name="hdFooter" fireDisplayEvents="true" />
</jato:view>
</BODY>
</HTML>
</jato:useViewBean>
Please give us a feasible solution to solve this problem.
Thx
Ravi
--- In [email protected], "Todd Fast" <Todd.Fast@S...>wrote:
Craig & Eric--
(If you're not interested in the resolution to the problem Craigposted,
please skip ahead to the section in which I describe the
preferred
technique
for including headers and other common content in a JATO page.
This
discussion is very important because I introduce the concept of"view
compostion", in which JATO pages are composed of modular andreusable view
components. This is one of the most powerful new features of
JATO,
and a
capability that simply wasn't possible in NetDynamics.)
Posted Problem Resolution
Craig & Eric, from what I can tell, you are both trying to
include
a full
view bean in a parent page at translation time. This is notpossible, as
you can see from the compiler errors you get. There are
collisions
when
multiple top-level tags are included in the same JSP.
When I said earlier that you needed to use a translation-timeinclude
instead of a run-time include, I was assuming that you were
trying
to
include a fragment of HTML/JSP in the parent page. By
fragment, I
mean HTML
or JSP content that does not declare a view bean or form, but
rather
references views contained within the parent view bean. If youwant to
include a full page (JSP + ViewBean) in another page, then you'dneed to use
a run-time include. A run-time include temporarily pauses therendering of
the current page, and sends the full request to the included
page
as if it
were a separate client request. The resulting content from theincluded
page is inlined into the parent page's content, and processing
of
the parent
page then continues.
Now I realize after thinking about it a bit that we may not have
sufficiently provided for full page includes because of some
late-
breaking
changes in the request context handling. After some basic
testing,
it
appears that if you try to include one JATO page in another byreferencing
the JSP, the included page will cause a class cast exception tooccur.
There may also be problems because the request context on theincluded page
will not have been set. In any case, full JATO page inclusionlooks like
it's an issue we're going to have to address with some fixes
before
it will
work properly. My apologies. (One workaround if this is
necessary
is to
make the included view bean a child view of the parent view
bean.
I won't
go into that however).
How to Include Common Content
Now, on to the discussion of the preferred way of including
common
content
in a JATO page. Let's say you have a common header you want toinclude in
one or more of your JATO pages. Because of the issue I notedabove, and the
fact that the header is not really independently displayable,
you
don't want
to do a run-time include (which, remember, would necessitateincluding a
full JATO page).
Instead, you should include the header as an HTML/JSP fragmentusing a
translation-time include. Depending on whether your header hasdynamic
information, you can do one of two things. If the header is
just
static
content and/or set of links, you can just reference the HTMLfragment in the
parent HTML directly, and you won't need any kind of view or
view
bean to
back it, or any reference to anything in JATO.
If you need some dynamic info in the header, like the module URLfor a link,
you can reference the parent page's view bean for this
information
by simply
including references to the parent page's implicit JSP variables(viewBean,
currentVIew, and currentTiledView). For example:
Parent JSP:
<jsp:useBean id="viewBean" class="..."scope="request"></jsp:useBean>
<jato:useViewBean className="..." fireChildDisplayEvents="true">
<%@ include file="MyInclude.jsp" %>
</jato:useViewBean>
Included content (MyInclude.jsp):
... viewBean.getRequestContext().getModuleURL() ...
The final HTML with the included content would then look like
this:
<jsp:useBean id="viewBean" class="..."scope="request"></jsp:useBean>
<jato:useViewBean className="..." fireChildDisplayEvents="true">
... viewBean.getRequestContext().getModuleURL() ...
</jato:useViewBean>
MyInclude.jsp will be inlined in the parent JSP before it istranslated to a
servlet. Note that it does not include the full HTML tags
normally
found in
an HTML file--there are no <html>, <head>, or <body> tags
because
it is not
expected to be used outside of an include page. In effect,
this is
the
equivalent of a server-side include (SSI).
Now, if you need truly dynamic info in the header, like say youwant to
display the user's name and SSN, then you'd likely want to
embed a
child
view in the parent view bean which will encapsulate & provide
the
necessary
information. This is in contrast to actually making these
fields
direct
children of the the parent view bean, which would be a tedious
and
error
prone task on every page you wanted to include this information.Let me try
to contrast these two approaches with a diagram of parent-child
relationships:
Here's the bad way:
ParentViewBean (ViewBean)
|
+-- UserFirstName (StaticTextField)
|
+-- UserSSN (StaticTextField)
In this situation, you'd need to provide the logic to populatethese fields
in every view bean on which they appeared. This is tedious andessentially
eliminates the "common"-ness of the content (this is also whatNetDynamics
forced people to do).
Now, the better way:
ParentViewBean (ViewBean)
|
+-- MyHeaderView (MyHeaderView.java)
|
+-- UserFirstName (StaticTextField)
|
+-- UserSSN (StaticTextField)
In the better way, you can see that the header information isencapsulated
in an instance of "MyHeaderView", which is a subclass ofContainerViewBase
or one of the other ContainerView subtypes. The population of
the
data
fields is encapsulated in that view, and the parent view need
not
know
anything about what's actually being displayed by that view.
Thus, you can see that MyHeaderView, in conjunction with a
snippet
of JSP
content in a companion file, is completely modular and can beembedded in
any parent view bean on which you want the header to appear.
The
only
requirement is then to include MyHeaderView as a child view of
the
parent
view bean, and to include the correct JSP content that
references
that child
view.
The included JSP content would now look something like this:
<jato:view name="MyHeaderView">
<table>
<tr><td>... <jato:staticText name="UserFirstName"/>
...</td></tr>
<tr><td>... <jato:staticText name="UserSSN"/> ...</td></tr>
</table>
</jato:view>
If we now included this content in the parent JSP from furtherabove, we get
the following as the JSP content before it is translated into aservlet:
<jsp:useBean id="viewBean" class="..."scope="request"></jsp:useBean>
<jato:useViewBean className="..." fireChildDisplayEvents="true">
<jato:view name="MyHeaderView">
<table>
<tr><td>... <jato:staticText name="UserFirstName"/>
...</td></tr>
<tr><td>... <jato:staticText name="UserSSN"/> ...</td></tr>
</table>
</jato:view>
</jato:useViewBean>
Ultimately, this technique is called "view compostion" or "view
aggregation", and is one of the major new features of JATO. Youcan now
define reusable view components and embed them in multiple viewcontainers,
on the same page or on different pages. Each page acts as a
frame,
in which
you provide the contents from modular components. Using thistechnique, you
can develop reusable view classes and chunks of JSP that can bearbitrarily
combined into complex pages.
I know this is a long and rambling discussion, but I hope I've
made
myself
at least partly clear. I'm more than happy to clarify anything
or
elaborate
more. Please let me know.
Todd
Todd Fast
Senior Engineer
Sun/Netscape Alliance
todd.fast@e...
[email protected]
[email protected]

How to access a variable from a dynamically included JSP page

I have a jsp (say main.jsp) using the following in its code :
<jsp:include page="menu.jsp" flush="true" />
I have a variable in menu.jsp which I would like to use in my main.jsp.
How do I get the value of the variable defined in menu.jsp ?
I called this variable in menu.jsp, Public, but this didnot help me use the value of that variable in main.jsp
Any help is highly appreciated.. thnks a lot

I do notice the variable var1 has the value populated - in menu.jsp - (from View -->
Source in the browser) but for some reason not able to use it in main.jspI'm not quite sure of the way your jsps are structured from your code snippet but I think there is something to be aware of here that may be part of your problem, namely the difference between the include directive and the include action.
You are currently using the include action, this treats the included resource as a dynamic object - i.e. a request is sent to that resource and the resulting response is included in your page. So when you think of what there is no java variable actually included - you'll just get the resulting HTML that is generated by menu.jsp
The include directive, as in <%@include file=�menu.jsp � %>, on the other hand treats the resource as a static object. This means the actual bytes in the included resource are inserted into the including jsp and then the result of that is compiled and processed, effectively you are cutting and pasting the menu.jsp into your calling jsp. In this case the variable would be available to the calling jsp.
However this approach does bring other difficulties that may break your current code, you'll just have to try it and see what happens.
Hope that's relevant to your problem,
Matt

%@ page import="..." % does not seem to be working correctly

Hi,
          I am running Weblogic 6.1 sp1 and I am having a problem with import page
          directive. <%@ page import="my.package.*" %> does not appear to be working
          correctly when I try to reference classes in imported packages (my.package,
          etc.) from the useBean tag.
          The following code works with Resin, but not Weblogic:
          <%@ page import="my.package.*" %>
          <jsp:useBean id="errorBean" class="ErrorBean" scope="request"/>
          If, I take out the page directive, and change the useBean tag to:
          <jsp:useBean id="errorBean" class="my.package.ErrorBean"
          scope="request"/>
          then the page compiles and runs just fine.
          Michael


Here's a snippet from Sun's j2ee tutorial
          (http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/JSPBeans4.html):
          <jsp:useBean id="beanName"
          class="fully_qualified_classname" scope="scope"/>
          But I agree with you, the excerpt you posted seems to include the
          useBean tag, which is misleading.
          Nils
          Michael Hill wrote:
          >
          > I don't think this is the way it is "supposed" to be. Here is an excerpt
          > from the JSP Syntax reference on http://developer.java.sun.com
          > on the page directive:
          >
          > import= "{ package.class | package.* }, ..."
          > A comma-separated list of one or more packages that the JSP file should
          > import. The packages (and their classes) are available to scriptlets,
          > expressions, declarations, and tags within the JSP file. You must place the
          > import attribute before the tag that calls the imported class. If you want
          > to import more than one package, you can specify a comma-separated list
          > after import or you can use import more than once in a JSP file.
          >
          > ---
          >
          > It says the packages are available to tags within the JSP file as long as
          > you place the import before the tag that calls the imported class. In my
          > case, I am placing the import before the <jsp:useBean> tag.
          >
          > Michael
          >
          > "Nils Winkler" <[email protected]> wrote in message
          > news:[email protected]...
          > > I'm pretty sure that you have to specify the fully qualified class name
          > > in the useBean tag. import won't help you here.
          > >
          > > Nils
          > >
          > > Michael Hill wrote:
          > > >
          > > > Hi,
          > > >
          > > > I am running Weblogic 6.1 sp1 and I am having a problem with import page
          > > > directive. <%@ page import="my.package.*" %> does not appear to be
          > working
          > > > correctly when I try to reference classes in imported packages
          > (my.package,
          > > > etc.) from the useBean tag.
          > > >
          > > > The following code works with Resin, but not Weblogic:
          > > >
          > > > <%@ page import="my.package.*" %>
          > > > <jsp:useBean id="errorBean" class="ErrorBean" scope="request"/>
          > > >
          > > > If, I take out the page directive, and change the useBean tag to:
          > > >
          > > > <jsp:useBean id="errorBean" class="my.package.ErrorBean"
          > > > scope="request"/>
          > > >
          > > > then the page compiles and runs just fine.
          > > >
          > > > Michael
          > >
          > > --
          > > ============================
          > > [email protected]
          ============================
          [email protected]

How we can use jsf tags in included jsp enclosed in subview tags

Hello everybody,
I am developing web app by using jsf. I am including a jsp page "header.jsp" into another jsp page "main.jsp". The header.jsp page is enclosed in jsf subview tag on main.jsp page. The header.jsp contains some static html code and some jsf tags like "outputText". When i added tag library url in header.jsp then my app was not even not initiating and i was getting following exception
ERROR [UIComponentTag] Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml.
16:22:16,890 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at javax.faces.webapp.UIComponentTag.setupResponseWriter(UIComponentTag.java:929)
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:310)
....Now i removed jsf tag library url from included jsp "header.jsp" so now my app is running but only static html data is being displayed but the value in the jsf tag "outputText" is not being printed in the browser
kindly help me. i would be very thankful....

Your question has nothing to do with Sun Java System Directory Server.
Please use the right forum(s).
Thanks

ADF Question: included jsp action firing after page load

Hi all,
I am using JDeveloper 10.1.3.3 and ADF + BC.
Here is another interesting situation for you. I have a page with an included jsp at the top with tabbed navigation.
My page is for entering an order. Users can have multiple orders "open" in other tabs at the same time. Users can also have many other non-order pages opened in tabs. We are using the same View Objects (Entity Based) along with Transient View Objects on each order.
Each order tab needs to "remember" the orderId so that when the user clicks on a tab, the appropriate rows are set in the order that is to be "opened". This occurs in a tab's action() - setting the orderId and forwarding to the appropriate page (if different) or reloading the same page with the new id.
On page load we try to get the tab's orderId and load that as the current row of all of our view objects. This should make it seem like they are all concurrently running.
The problem is when going from order to order, once the tab is clicked, the page's OnPageLoad method runs BEFORE the action of the tab click is processed. Therefore the order that loads thinks it is the previous order, and does not load the correct View Object rows.
Does anyone know how we can force the tab action to occur before the page load so that we can get the proper orderId?
Thanks,
Heather

Thanks for your speedy reply Frank,
We are using the onPageLoad from the OnPageLoadBackingBeanBase which implements the PagePhaseListener.
In this we are doing something like:
        if (isPostback()) {
            String selectedTabNum =
                EL.getAsString("#{TabCounter.currentSelectedTab}");
            String test = EL.getAsString("#{TabCounter.tabOrderId" + selectedTabNum + "}");
            System.out.println("tab num " + selectedTabNum);
            System.out.println( "testing " + test );
        }our tab counter (a session bean) has these two methods (among others):
    public void setCurrentSelectedTab(int currentSelectedTab) {
        this.currentSelectedTab = currentSelectedTab;
        for(int i=1;i<= 20; i++) {
            EL.set(BACKING_START+"selectedTab"+i+"}", false);
        EL.set(BACKING_START+"selectedTab"+currentSelectedTab+"}", true);
    public String getNextAvailableTab () {
        for(int i=2;i<=20;i++) {
            boolean isTab = (new Boolean (String.valueOf(EL.get(BACKING_START+"render"+i+"}")))).booleanValue();
            if (!isTab) {
                return String.valueOf(i);
        return "0";
    }our tab header (request bean) has this method as the action for clicking a tab:
        System.out.println("handleTabNavigation");
        String componentId = actionEvent.getComponent().getId();
        String selectedTab = componentId.replaceFirst("tab","");
        int selectedTabNum = new Integer(selectedTab).intValue();
        EL.set("#{TabCounter.currentSelectedTab}", selectedTabNum);
        String tabType = EL.getAsString("#{TabCounter.tabType"+selectedTabNum+"}");
        if (tabType.equals("regular")) {
            String orderId = EL.getAsString("#{TabCounter.tabOrderId"+selectedTabNum+"}");
            EL.set("#{processScope.unfinishedHeaderId}", orderId);
        } else if (tabType.equals("standing")) {
            String orderId = EL.getAsString("#{TabCounter.tabOrderId"+selectedTabNum+"}");
        }Thanks,
Heather

Can we include a JSP page in an already included JSP Page

Hi guys,
I have a doubt with JSP include tag. The problem is ..
Can we include a JSP page in an already included JSP Page
AS shown below
I have one JSP page
Index.jsp
-in this I am including "include.jsp"
-Again within the "include.jsp" I am including "include1.jsp"
It is neither giving an error nor displaying the content which is there in the "include1.jsp" but it is displaying the content of "include.jsp"
first of all let me know whether it is possible or no.. If so then why is it not coming and what is required to do this..
fast...
Thanks
Sreenadha Reddy K

Hi guys,
I have a doubt with JSP include tag. The
g. The problem is ..
Can we include a JSP page in an already included JSP
Page
AS shown below
I have one JSP page
Index.jsp
-in this I am including "include.jsp"
-Again within the "include.jsp" I
he "include.jsp" I am including "include1.jsp"
It is neither giving an error nor displaying the
content which is there in the "include1.jsp" but it is
displaying the content of "include.jsp"
first of all let me know whether it is possible or
no.. If so then why is it not coming and what is
required to do this..
fast...
Thanks
Sreenadha Reddy KIt is possible , u just have to change all the files and save them all again, clear the temp dirs where all the jsp's as compiled. Now after all this try , it should work .

Include jsp file

There are 2 jsp files: main.jsp, process.jsp.
In the main.jsp,
String name="java";
<jsp:include page="process.jsp" flush="true" />
.....In the process.jsp,
String name="abc";
....My problem is the parameter - name have not changed to "abc" .
How can I solve this problem ?
thanks.

Hi,
Dont think that it should happen like that, the diffrence between <jsp:include> and <%@ include> is that jsp:include is a dymanic include i.e. the processed contents of the jsp flie are added to your page, while @ include is a static include meaning that the contents are first put together as one big jsp and then the contents are processed.
That is why the original jsp is recompiled, and your server should automatically determine that when a parent jsp is to be recompiled when a included jsp is changed. What server are you using?
And as in jsp:include the processed result (html) is added the variable declairations or manipulations in a child will not be accesable in the parent, while they will be in case of @include.
Hope this helps
Regards
Omer

Problems with managed beans on included JSPs

I've got a problem with managed beans within an included JSP
The included page looks as follows:
<f:subview id="includedPage" binding="#{testBean.component}">
     <h:outputText value="Hallo from the included page"/>
     <h:outputText value="#{testBean.msg}" />
</f:subview>The including page is also very simple
<f:view>
     <html>
          <head>
               <title>Test include</title>
          </head>
          <body>
               <h:outputText value="Hello from the including page"/>
               <jsp:include page="included.jsp"/>
          </body>
     </html>
</f:view>The testBean is a managed bean with page scope and looks as follows:
public class TestBean {
    public UIComponent fComponent;
    public TestBean() {
        System.out.println("TestBean Constructor called " + toString() );
    public String getMsg() {
        return "Component = " + fComponent ;
    public void setComponent(UIComponent component) {
        System.out.println("setComponent called " + component);
        fComponent = component;
    public UIComponent getComponent() {
        System.out.println("getComponent called " + fComponent);
        return fComponent;
}The output to the console is:
TestBean Constructor called de.kvb.athena.web.beans.TestBean@1bc16f0
getComponent called null
TestBean Constructor called de.kvb.athena.web.beans.TestBean@18622f3
setComponent called javax.faces.component.UINamingContainer@160877b
TestBean Constructor called de.kvb.athena.web.beans.TestBean@5eb489
and the page displays
Hello from the include page
Hello from the included page Component = null
Can anyone explain this behavior ? What's the reason that the page displays
Component = null
and is it possible to display the parent naming container (subview) this way ?
how ?
Thanks

By "page scope" I assume you mean "none"? If so JSF creates a new bean for each place it's referenced. The closest to the behavior you want, once per "page", is really request scope.
(I'm not sure why the constructor is being called thrice, though. I should look into this.)
I assume you want a bean-per-subview scenario. This should be doable, and one way that allows a dynamic number of subviews would be as follows:
--create a "manager" bean in request scope
--give it get/set methods that retrieves a Map of "TestBean" instances; the idea is that each subview use a different key "s1", "s2", etc
back the manager method with Map implementation that checks if there's already a TestBean associated with the key returns it if yes, else null.
If that seems messy, the component solution is hairy :-) See http://forum.java.sun.com/thread.jspa?threadID=568937&messageID=2812561
--A

Static compiles do not seem to include JSP's?

Similar Messages

Maybe you are looking for