<div>
RAD 7 will treat mainheader.jsp as another j sp. 
 
In order to avoid compilation error 
 
you can try like this 
 
&lt;%@ include file=&quot;mainheader.jsp&quot; %&gt; 
 
as 
&lt;%@ include file=&quot;mainheader.jspf&quot; %&gt; 
 
Let me know if any concerns 
 

</div>

<div>
will a request.setAttribute and a request.getAttribute work?
</div>

<div>
I believe my comment was correct because eventually when the application is run on the server, it won't give the same error as what the development IDE RAD is giving.
</div>

<div>
<div class="content wysiwyg-content">
Hi, 
 
I have a main JSP page where header, and two more JSP pages are included dynamically like: 
 
In main.jsp page 
 
&lt;%@ include file=&quot;mainheader.jsp&quot; %&gt; 
 
 
Now in the main.jsp page, there are some variables declared 
 
like: 
&lt;% 
 
String screen=null; 
String sort=null; 
String where=null; 
 
%&gt; 
 
which are later used in the included JSP like mainheader.jsp as 
 
if (userType == &quot;E&quot; &amp;&amp;&nbsp;!screen.equals(&quot;asnhome&quot;)) { 
String checkHacker = HttpHeaderParser.encodeString(where); 
 
} 
 
 
Now RAD 7 shows these (screen, where) &nbsp;as errors in the mainheader.jsp page? 
 
This app was initially built with WAS 5.1.2 
 
I am trying to convert it to WAS 6.1 
 
 
What is the problem here? 
 
 
Thanks. 
_Esam
</div>
</div>

Hi,

I have a main JSP page where header, and two more JSP pages are included dynamically like:

In main.jsp page

<%@ include file="mainheader.jsp" %>


Now in the main.jsp page, there are some variables declared

like:
<%

String screen=null;
String sort=null;
String where=null;

%>

which are later used in the included JSP like mainheader.jsp as

if (userType == "E" && !screen.equals("asnhome")) {
String checkHacker = HttpHeaderParser.encodeString(where);

}


Now RAD 7 shows these (screen, where) as errors in the mainheader.jsp page?

This app was initially built with WAS 5.1.2

I am trying to convert it to WAS 6.1


What is the problem here?


Thanks.
_Esam

RAD 7 will treat mainheader.jsp as another j sp.

In order to avoid compilation error

you can try like this

&lt;%@ include file=&quot;mainheader.jsp&quot; %&gt;

as
&lt;%@ include file=&quot;mainheader.jspf&quot; %&gt;

Let me know if any concerns



will a request.setAttribute and a request.getAttribute work?

I believe my comment was correct because eventually when the application is run on the server, it won&#39;t give the same error as what the development IDE RAD is giving.

How to use variables from a main JSP page to an included JSP page?

Hi,

I have a main JSP page where header, and two more JSP pages are included dynamically like:

In main.jsp page

&lt;%@ include file=&quot;mainheader.jsp&quot; %&gt;


Now in the main.jsp page, there are some variables declared

like:
&lt;%

String screen=null;
String sort=null;
String where=null;

%&gt;

which are later used in the included JSP like mainheader.jsp as

if (userType == &quot;E&quot; &amp;&amp; !screen.equals(&quot;asnhome&quot;)) {
String checkHacker = HttpHeaderParser.encodeString(where);

}


Now RAD 7 shows these (screen, where)  as errors in the mainheader.jsp page?

This app was initially built with WAS 5.1.2

I am trying to convert it to WAS 6.1


What is the problem here?


Thanks.
_Esam

JavaServer Pages (JSP) allow the development of dynamically generated web pages. It uses the Java programming language; JSP pages are translated into servlets at runtime, with each servlet being cached and reused until the JSP is modified. JSP allows Java code to be interleaved with static web markup content, so the resulting page can be compiled and executed on the server to deliver the content.

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.

Java

Java Enterprise Edition (Java EE) is a specification defining a collection of Java-based server and client technologies and how they interoperate. Java EE specifies server and client architectures and uses profiles to define technology sets targeted at specific classes of applications. All Java EE profiles share a set of common features, such as naming and resource injection, packaging rules and security requirements.