Import in JSP

Hi
We have a product developed by one of our clients,
ITs deployed in Weblogic 7.0.
When I was reading the JSP's in the application , I noticed that they are using "Vectors" and Hashtables in the jsp , but the import statement is missing for java.util.*
then i checked all the other JSP's and found the samething.
The JSP's are working without any problem.
Why is this happening. Should the compiler throw an error saying that the class cannot be resolved/not found.
Can we do any global settings in the application server, so that the java.utils.* can be refered in all the Jsp's?
Please advise
Thanks in advance

Probably no one of the jsp's have the import statement. Instead check if there is some pre-compiled class that makes de import.
regards,
-eduardo s.m.

Similar Messages

Jsp:useBean vs page import in JSP

Hi,
What is the difference between jsp:useBean vs page import in JSP?
By using page import also I can call the method of the class, apart from jsp:useBean does have scope associated with it. I don't think there is any change between both the 2. Yes by using jsp:useBean we can set the property and get the property as well.
Is there any major differences between the 2 and when to use which ? Please clarify.
Thanks.

797836 wrote:
Hi,
What is the difference between jsp:useBean vs page import in JSP?
By using page import also I can call the method of the class, apart from jsp:useBean does have scope associated with it. I don't think there is any change between both the 2. Yes by using jsp:useBean we can set the property and get the property as well.
Is there any major differences between the 2 and when to use which ? Please clarify.
Thanks.Yes there is a difference.
If you use import, then you have to create/use the reference object to use the class methods. And you can't define the scopes like session, page .. etc. Apart from this you will be using scriptlets <% %>.
if you are using jsp:useBean , then you can skip the above activities. useBean takes care of it.
or you can say jsp has provided a utility to access the beans without creating its object or using scriptlets.

Cannot static import in JSP (WebLogic 10.3)

I am facing a problem with the use of 'static import' in JSP. This is on WebLogic 10.3. Please help/advise.
Running weblogic.jspc results in the following error:+
$ java weblogic.jspc -verboseJspc -keepgenerated -d /tmp/jsp WEB-INF/jspf/fragment.jspf
\[jspc\] Overriding descriptor option 'keepgenerated' with value specified on command-line 'true'
\[jspc\] Compiling /WEB-INF/jspf/fragment.jspf
jspc failed with errors :weblogic.servlet.jsp.CompilationException: fragment.jspf:6:17: Syntax error on token "static", Identifier expected after this token
<%@page import="static java.util.Collections.EMPTY_LIST" %>
^-------------------------------------^
fragment.jspf:6:17: The import java.util.Collections.EMPTY_LIST cannot be resolved
<%@page import="static java.util.Collections.EMPTY_LIST" %>
^-------------------------------------^
The generated Java file is not correct; the static import is split into multiple imports+
$ head /tmp/jsp/jsp_servlet/_web_45_inf/_jspf/__fragment_jspf.java
package jsp_servlet._web_45_inf._jspf;
import java.lang.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import static;
import java.util.Collections.EMPTY_LIST;
public final class __fragment_jspf extends weblogic.servlet.jsp.JspBase implements weblogic.servlet.jsp.StaleIndicator {

I'm not sure that JSPC supports static imports, I would open a support case to get clarification.

How to import existing jsp project into jdeveloper

can someone help me how to import existing jsp project into jdeveloper?
can give me step by step to import..cause i am new for jdeveloper..
thank you very much

Well there are two options - if you have a WAR file with the code in it, then you can use the file->import WAR.
Or you can use the new->Project from source code.
Note that you'll probably need to do some library settings and some directory setting after that.
Have a look at this demo for basic steps:
http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/NBtoJDevProject/NBtoJDevProject.html

Package not found when importing in JSP

          I'm now using Weblogic 6.0 SP 2 for development. I did a test application, containing
          EJBs, and a JSP. Package the applications to an EAR file. Then I deploy the test
          application using hot-deploy - just drop the EAR into the domain\application folder.
          When I call the JSP page, I get an error saying that the package I'm importing
          is not found. What is wrong?? The test application works on Weblogic 5.1
          My WAR file contains only the JSP and XML descriptor. Do I need to include classes
          inside??? Don't think that is correct.
          Please advise.


          It was a bad mistake. Made an error in the application.xml, which refer to an invalid
          JAR file. Made the correction and it works like magic.
          Thanks :)
          "Cameron Purdy" <[email protected]> wrote:
          >WL 60 is tolerant of class location in that you can put all classes in
          >the
          >EJB JAR inside the EAR and it will work as well (sometimes better if
          >there
          >are xrefs) as carefully splitting classes between JAR and WAR.
          >
          >Chances are your context is not set up correctly. What is the web.xml?
          >What
          >is the URL you used? In WL 51 you provided the context in the "register"
          >line in the weblogic.properties. Now that info is self-contained in the
          >app
          >itself.
          >
          >Peace,
          >
          >--
          >Cameron Purdy
          >Tangosol Inc.
          ><< Tangosol Server: How Weblogic applications are customized >>
          ><< Download now from http://www.tangosol.com/registration.jsp >>
          >
          >
          >"Moong" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> I'm now using Weblogic 6.0 SP 2 for development. I did a test application,
          >containing
          >> EJBs, and a JSP. Package the applications to an EAR file. Then I deploy
          >the test
          >> application using hot-deploy - just drop the EAR into the
          >domain\application folder.
          >>
          >> When I call the JSP page, I get an error saying that the package I'm
          >importing
          >> is not found. What is wrong?? The test application works on Weblogic
          >5.1
          >>
          >> My WAR file contains only the JSP and XML descriptor. Do I need to
          >include
          >classes
          >> inside??? Don't think that is correct.
          >>
          >> Please advise.
          >>
          >
          >

Impli?it import in JSP

Hi,
          Could anybody clear the following question? Which way does jsp compiler make
          import of packages on weblogic 6.0? I looked through JSP examples and did
          not find any import declaration in some of them, but there were some classes
          that do not belong to the default import list:
          java.lang.*,
          javax.servlet.*,
          javax.servlet.jsp.* and javax.servlet.http.*,
          for example java.util.Enumeration, java.util.Date.
          Andrey


Mettu Kumar <[email protected]> wrote:
          >>>Exactly. The fact that WebLogic JSP compiler imports java.util.* by default caused some
          > minor portability problems (on the other hand I believe that scriptlet tag should be
          > deprecated ;-)).
          > What portability problems did BEA importing java.util.* into generated java files caused
          > you?
          It is not a bug of anything like that - the problem was that JSP developers got used to the
          fact that java.util.* is always imported by the WebLogic JSP compiler and this created some
          very minor portability issues.
          > BTW who told you java.util.* package is imported for every jsp file unless you looked at
          > the generated java file? No one expects to you write your jsp files looking at generated
          > java code and making assumptions that are not part of JSP spec.
          > I do Agree with you completely regarding print bug.
          > Kumar.
          > Dimitri Rakitine wrote:
          >> Mettu Kumar <[email protected]> wrote:
          >> > Dimitri,
          >>
          >> > As mentioned by you as per spec they are only default packages imported. By
          >> > that spec doesn't mean jsp container can only import those packages. Every JSP
          >> > Container imports several other packages.
          >>
          >> > The only caution developers need to take is that they can assume only these
          >> > four packages are available to them.
          >>
          >> Exactly. The fact that WebLogic JSP compiler imports java.util.* by default caused
          >> some minor portability problems (on the other hand I believe that scriptlet tag
          >> should be deprecated ;-)).
          >>
          >> Minor things like this are definitely an issue when portability is important. Here is
          >> another minor example that I remember - WebLogic violates JspWriter contract
          >>
          >> ----------
          >> public abstract void print(java.lang.Object obj) throws java.io.IOException
          >> Print an object. The string produced by the String.valueOf(Object) method is translated
          >> into bytes according to the platform's default character encoding, and these bytes are
          >> written in exactly the manner of the Writer.write(int) method.
          >>
          >> public static String valueOf(Object obj)
          >> Returns the string representation of the Object argument.
          >> Parameters:
          >> obj - an Object.
          >> Returns:
          >> if the argument is null, then a string equal to "null"; otherwise, the value of
          >> obj.toString() is returned.
          >> ------------
          >>
          >> just a little: if the argument is null, in WebLogic the jsp page will display "" and
          >> "null" in all other containers.
          >>
          >> > Can you imagine how containers can provide JSP features without even import
          >> > java.io.* ?
          >>
          >> Yes - they generate java code automatically, so convinience is not important for
          >> them - they can always use fully qualified names.
          >>
          >> > Kumar.
          >>
          >> > Dimitri Rakitine wrote:
          >>
          >> >> WebLogic imports java.util.* by default - this is convinient, but
          >> >> will not work on other JSP engines (according to the spec the default imports
          >> >> are: java.lang.*, javax.servlet.*, javax.servlet.jsp.*, javax.servlet.http.*)
          >> >>
          >> >> Andrey Leskovoy <[email protected]> wrote:
          >> >> > Hi,
          >> >> > Could anybody clear the following question? Which way does jsp compiler make
          >> >> > import of packages on weblogic 6.0? I looked through JSP examples and did
          >> >> > not find any import declaration in some of them, but there were some classes
          >> >> > that do not belong to the default import list:
          >> >> > java.lang.*,
          >> >> > javax.servlet.*,
          >> >> > javax.servlet.jsp.* and javax.servlet.http.*,
          >> >>
          >> >> > for example java.util.Enumeration, java.util.Date.
          >> >>
          >> >> > Andrey
          >> >>
          >> >> --
          >> >> Dimitri
          >>
          >> --
          >> Dimitri
          Dimitri

Import statement in JSP

          Hi
          I am maintaining a system done by one of our vendors.
          Application is deployed in WLS 7.0.
          When I imported the Jsp's into my IDE , I got errors where java.util classes are
          used in the JSP's and the import statement is missing.
          Most of the Jsp's are like this,
          It is working fine in the production server.
          In the IDE i am forced to put the import statement and that is what I expect.
          But how can it work in the production server without any issue.
          Can someone advise me on this
          Thanks
          DN


<%@page import="java.util.calendar" %>
Oops... forgot the "page" in there ...That's what I get for using GUI's too much!!! :)

How to import jsp file in other jsp file

I am using JSP for a website and my database is in Oracle. I want to connect to Oracle database in one jsp file such as connection .jsp.
Then I want to use this same connection in all the jsp files by importing the jsp file. (I know in Core java we can do this by import statement e.g. import connection.java) but how can I do this in jsp. whwn i am importing connection.jsp using <%@ page import=connection.jsp%> It is showing errors.
Plz help me. It's very urgent.
Thanks in advance.

Thats because import is for importing packages as any jsp tutorial could have told you. You are looking for include:
<%@ include file="connection.jsp"%>

Problem when use multiple c:import jstl on jsp on Tomcat 5.0

I have jsp that use multipe import jstl tag. I was able to run on the Tomcat 5.5.9. When I deploy it on Tomcat 5.0.28, it is not working.
For example:
<c:import url="/jsp/page1.jsp" />
<c:import url="/jsp/page2.jsp" />
I look at Tomcat cache directory and I only see page1.jsp compiled but not page2.jsp. I look at the catalina.out log file and the error message shows below. I thought JSTL is working for Tomcat 5.x up. Do anyone have any idea? Please help.
Thanks.
java.lang.ArrayIndexOutOfBoundsException: 204
     at org.apache.jasper.compiler.JspReader.peekChar(JspReader.java:164)
     at org.apache.jasper.compiler.JspReader.isSpace(JspReader.java:357)
     at org.apache.jasper.compiler.JspReader.isDelimiter(JspReader.java:440)
     at org.apache.jasper.compiler.JspReader.parseToken(JspReader.java:405)
     at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1285)
     at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1560)
     at org.apache.jasper.compiler.Parser.parse(Parser.java:126)
     at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220)
     at org.apache.jasper.compiler.ParserController.parse(ParserController.java:101)
     at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:470)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
     at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
     at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
     at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
     at org.apache.taglibs.standard.tag.common.core.ImportSupport.acquireString(Unknown Source)
     at org.apache.taglibs.standard.tag.common.core.ImportSupport.doEndTag(Unknown Source)
     at org.apache.jsp.jsp.offermgmt.ajax.ajaxPromotion_jsp._jspx_meth_c_import_1(ajaxPromotion_jsp.java:218)
     at org.apache.jsp.jsp.offermgmt.ajax.ajaxPromotion_jsp._jspService(ajaxPromotion_jsp.java:70)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)

Can you access page1 and page2.jsp correctly on their own?
ie could the problem be with page2.jsp rather than the import command?

How to import jsp files into other jsp files ?

hi i have the following code mymainpage.jsp
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://richfaces.org/a4j" prefix="a4j"%>
<%@ taglib uri="http://richfaces.org/rich" prefix="rich"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;" >
<title>Sagem Module</title>
</head>
<body>
<f:view>
<rich:modalPanel id="panel" width="350" height="100">
        <f:facet name="header">
            <h:panelGroup>
                <h:outputText value="Modal Panel"></h:outputText>
            </h:panelGroup>
        </f:facet>
        <f:facet name="controls">
            <h:panelGroup>
                <h:graphicImage value="/images/modal/close.png" styleClass="hidelink" id="hidelink"/>
                <rich:componentControl for="panel" attachTo="hidelink" operation="hide" event="onclick"/>
            </h:panelGroup>
        </f:facet>
        <h:outputText value="This panel is called using Component Control Component"></h:outputText>
        <br/>
        <h:outputText value="Closure link (X) works also through Component Control"></h:outputText>
    </rich:modalPanel>
<h:form>
    <h:outputLink value="#" id="link">
        Show Modal Panel
        <rich:componentControl for="panel" attachTo="link" operation="show" event="onclick"/>
    </h:outputLink>
</h:form>
<f:view>
</body>
</html>can i put the model panel into another file for example modalpanel.jsp and then include it into my page mymainpage.jsp such
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://richfaces.org/a4j" prefix="a4j"%>
<%@ taglib uri="http://richfaces.org/rich" prefix="rich"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;" >
<title>Sagem Module</title>
</head>
<body>
<f:view>
//**** import modalpanel.jsp
<h:form>
    <h:outputLink value="#" id="link">
        Show Modal Panel
        <rich:componentControl for="panel" attachTo="link" operation="show" event="onclick"/>
    </h:outputLink>
</h:form>
<f:view>
</body>
</html>

Use jsp:include.
parent.jsp
<f:view>
    <h1>Parent</h1>
    <jsp:include page="child.jsp" />
</f:view>child.jsp
<f:subview id="child">
    <h2>Child</h2>
</f:subview>(note the f:subview!)

How to Import Custom Views and JSPs to ALBPM Enterprise

Hi,
I am using ALBPM 5.7. I have developed a custom view in Studio. When I publish and Deploy the Project in ALBPM Enterprise (WebLogic 9.2), I check true the Import Custom JSPs and Views (or similar terminology). But when I login to the portal after installing the EAR, the view is not listed in my work pane.
Also, in one of the Interactive Activity I am calling a JSP, which gives a Null Pointer Exception when execute the instance, In my opinion, the Custom JSP is not deployed.
I have also copied the JSP file in location \bea\ALPBM5.7\j2eewl\webapps\portal\customjsp\
Please suggest as how do I deploy the View and JSP
Thank you,
Regards
Jayant
Edited by jayantbit at 06/19/2008 8:01 AM
Edited by jayantbit at 06/19/2008 8:21 AM

Hi Mohamed,
Please check below link.
What is Drag and Relate in SAP Business One - YouTube
https://help.sap.com/saphelp_sbo882/helpdata/en/45/100314cf465d7ae10000000a11466f/content.htm
https://help.sap.com/saphelp_sbo882/helpdata/en/45/10ff71cf465d7be10000000a11466f/content.htm
SAP - SAP Business One: Your Solution for Generating Custom Reports
Hope this helps
Regards::::
Atul Chakraborty

Import jsp

How to import a jsp present in a different package into another jsp?

cncncn wrote:
How to import a jsp present in a different package into another jsp?I think you probably mean include another jsp.
http://java.sun.com/products/jsp/tags/11/syntaxref1112.html
JSP fragments that are not complete pages should always use the .jspf suffix and should always be placed in /WEB-INF/jspf.

Error in executing a process for compilation for jsp

We have an iView which has jsp pages in it. We deployed the par & try toaccess the iview & we get an exception. The issue is that the iview has a jsp page. At the run time, this jsp is converted into a .java file
without problem. But EP engine is having issues compiling this java fileinto .class file.
On the other hand this same iview works just fine on our windows installation. Only Solaris EP install is having problems. The version onwindows as well as on Solaris is EP6 SP9.
Here is the exact version on the solaris EP:
sap.com/SAP-JEECOR 6.40 SP9 (1000.6.40.9.0.20041119045253) 20041122132733
sap.com/SAP-JEE 6.40 SP9 (1000.6.40.9.0.20041119045409) 20041122132741
When I copy the .class file from windows to unix machine, the iView works fine. Here is the exception I am getting:
>>> JSPCompiler >>> error
[email protected]a188b
[EXCEPTION]
com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException:
Error in executing a process for compilation
at
com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:574)
at
com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:370)
at
com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:672)
at
com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2143)
at
com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:76)
at
com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:122)
at
com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:279)
at
com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:129)
at
com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
at
com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at
com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at
com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at
com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
at
com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at
com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at
com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at
com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at
com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at
com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at
com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at
com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
I am having the same issue with another iview which has jsp page in it.
The web dynpro iview works fine.

Hi, seems like there's some typo in your jsp. Check the .java file listed with a java editor (like eclipse or devstudio.). Maybe you'll find the typo this way faster.
Most often, a multiline page import hampers jsp compilation,
e.g.
<%@page import="java.util.List,
java.util.Map"%>
needs to be
<%@page import="java.util.List,java.util.Map"%>
Regards,
Armin

How can i get the values from one JSP to another JSP

Hi All,
I am very new to JSP technology, I have one jsp having radio button, i want to accecc the state of this radio button to another JSP page, How can i do this.
Could anybody help me.
with Regards
Suresh

Try page import <%@ page import ="index.jsp" %> or include <%@include file="index.jsp" %> methods perhaps they might work.

How to store a JSP file in the SAP Application server ?

Hello All,
My reqt. is as follows :
1. I need to store a JSP File on the SAP Application server .
How can I do this ?
2. I want to call the uploaded jsp file from the server and call this jsp from abap to view the result of it .
How can I achieve this ?
First of all is this possible ?
Regards,
Deepu.K

Hello Mike,
Thanks for ur reply.
I've imported the JSP as a mime object into the BSP.
Now I've created the page to show that Mime Object as an image.
But nothing is coming as an output.
But then,there is an option for that mime object. i.e when I right click on the mime object there is an option called " convert to BSP".
I selected that option and it created a view in my BSP .( My BSP is a page with flow logic application )
Now how should i make this view to be an output ?
I guess this shud be posted in the BSP Forum ...but still taking a chance here :)-
Regards,
Deepu.K

Import in JSP

Similar Messages

Maybe you are looking for