Access problem in a web application

I have a web application with JSP, and in my pages, at the top, there is a sliding text (applet) from right to left, which has dynamic content from a database. The pages using the applet is at the root of the site, and the applet class located in the "WEB-INF/classes/WebClasses " directory. When I start the application, the pages using the applet complain that the class cannot be found. Pages' code and codebase attributes are fine, there is nothing wrong with these. What can be the problem?..

What could be a good solution while keeping
this connection class available to both of them (the
sliding text class and the beans in the
'WEB-INF/classes/WebBeans' directory) ?You would need two copies, one in the WEB-INF/classes/WebBeans directory for the server to access, the other in the JAR or directory structure you use for the applet. Remember what malcolmmc said, the applet runs on the client and the JSP/servlets run on the server. That means you have to provide the code for each of the server and the client.
And this is besides the point that malcolmmc made that applets usually aren't able to make DB connections...

Similar Messages

I am facing a caching problem in the Web-Application that I've developed us

Dear Friends,
I am facing a caching problem in the Web-Application that I've developed using Java/JSP/Servlet.
Problem Description: In this application when a hyperlink is clicked it is supposed to go the Handling Servlet and then servlet will fetch the data (using DAO layer) and will store in the session. After this the servlet will forward the request to the view JSP to present the data. The JSP access the object stored in the session and displays the data.
However, when the link is clicked second time then the request is not received by our servlet and the cached(prev data) page is shown. If we refresh the page then request come to the servlet and we get correct data. But as you will also agree that we don't want the users to refresh the page again and again to get the updated data.
We've included these lines in JSPs also but it does no good:
<%
response.setHeader("Expires", "0");
response.setHeader("Cache-Control" ,"no-cache, must-revalidate");
response.setHeader("Pragma", "no-cache");
response.setHeader("Cache-Control","no-store");
%>
Request you to please give a solution for the same.
Thanks & Regards,
Mohan

However, when the link is clicked second time then the request is not received by our servlet Impossible mate.. can you show your code. You sure there are no javascript errors ?
Why dont you just remove your object from the session after displaying the data from it and see if your page "automatically" hits the servlet when the link is clicked.
cheers..
S

Problem deploying a web application (war)

Hello,
I am having a problem deploying a web application in Tomcat.
Here is what happens:
-I copied the war file into the webapps directory.
-I started Tomcat.
-Tomcat automatically expanded the war file into a directory of the same name.
The problem is that I get the following error: "The requested resource (/jadmin) is not available." when I try to access my web application
Can anyone please help?
Thanks in advance,
Balteo.

Hi,
check the Tomcat log file <tomcat_dir>/logs/localhost_log.yyyy-mm-dd.txt and see if there is an error corresponding to the deployement of the (/jadmin) context.

Problem deploying a web application to oc4j in Unix

Hi! I would like to ask for someone's help on a problem I encountered while accessing a web app deployed to oc4j in Unix. Before deploying the application in Unix, I tried it on a Windows2000 server and it worked fine. I copied the same files (classes, jsps, js, css) to the Unix server and modified the same xml files (data-sources, global-web-application, http-web-site, server). I could access index.jsp of my application but I get a HTTP 404 error on the other pages. Also, the css applied on index.jsp doesn't seem to reflect on the page. Could someone share some insights on this and if you have experienced the same problem, kindly post your suggestions/solutions.
Thanks a lot,
Mildred

Reposting... css problem has been resolved (case sensitivity issue)
Hi! I would like to ask for someone's help on a problem I encountered while accessing a web app deployed to oc4j in Unix. Before deploying the application in Unix, I tried it on a Windows2000 server and it worked fine. I copied the same files (classes, jsps, js, css) to the Unix server and modified the same xml files (data-sources, global-web-application, http-web-site, server). I could access index.jsp of my application but I get a HTTP 404 error on the other pages. Could someone share some insights on this and if you have experienced the same problem, kindly post your suggestions/solutions.
Thanks a lot,
Mildred

Acces key problem in Mobile web application

Hi experts,
I am just trying a mobile web application according to the link given below:
/people/john.moy3/blog/2010/11/21/build-your-first-mobile-web-app-using-jquery-mobile-and-abap--part-2
tutorial by John Moy.
While reimplementing the controller class i am getting one message "Method DO_INIT is implemented in class CL_BSP_CONTROLLER" and asking for Access key.
Why this is happening and how i can overcome this problem?
Please help me.
Arun

Use REDEFINE key....

Connection problems in a Web Application

hi everybody.
I'm developing a struts-based Web Application to investigate an Oracle 9.2 DB, using Exadel Studio / Eclipse and Tomcat 5.0.
Here is the problem: I've made a class to test data-displaying, which simply connects to db using oci8 and returns a resultset, using the base procedure:
// load driver
Class.forName("oracle.jdbc.driver.OracleDriver");
// open connection
Connection conn=DriverManager.getConnection(...);
Statement st = conn.createStatement();
rs = st.executeQuery(sql);Now, everytime I call this method from my Action, to get back the resultset and display it in my jsp, I get a ClassNotFoundException on the Class.forName instruction.
Note that classes12.jar is correctly mounted, in fact if I run stand-alone the class containing this method, it connects without problems and returns the expected results. The exception is raised ONLY when the entire web application is running and the method is triggered by the struts Action.
Can anyone help me please?
Thank you in advance, I'm crushing my head on this for 2 weeks!
Emanuele

This means that your driver jar is unavailable to your web application; I'm pretty sure that Tomcat overrides the classpath set by your IDE. You can add application jars to the WEB-INF/lib of your web application. You can also set a container classpath that points to the jars...
here's some instructions for add the jars for cactus to Tomcat; just substitute your driver jars in these instructions.
http://jakarta.apache.org/cactus/integration/howto_tomcat.html
Also, classes12.jar is for Java 1.2 and Java 1.3 Since you are using Struts, I suspect you're also using Java 1.4 or Java 1.5 and you should probably be developing with the appropriate driver (classes12.jar does mostly work with Java 1.4, but Oracle doesn't support it.)

Is it possible to access Pages from an web application running in Safari in i-Pad?

Is it possible to access Pages application from an web application running on safari browser in iPad ?

Since you control the application AND the plugin - you can define ANY method of communication you want. Shared files, shared memory, IPC, named pipes, etc.

Problem with BEx Web Application Designer

Hi,
we use since last week the Web Application Designer with the SAP GUI 7.2.
Now I have a big problem since last week. I can call existing templates but unfortunately not change! I make a change in the template and save it. When I viewed the template again but no change is saved!
A new template I can create and change
Does anyone know the problem? The behavior also occurs with the old Gui 7.1.
Regards
Edited by: Jana VOGL on Oct 18, 2010 10:14 AM

Hi Jana,
Do you get any error before opening of an existing template in WAD? Doesn't look to be a problem with the different SAP GUI versions. Maybe somethings gone wrong with the Java - ABAP config settings or Java Portal communication settings. Maybe you should check with your BASIS team on the same. Tell them what the problem is & they will run a trace to figure out.
--Priya

How to restrict access to a deployed web application

I have a web application (ear-file) and i want to configure NetWeaver so that only certain users can use the web application.
How/where to configure the Application server to reach that goal?

Hi Ludger,
You can create J2EE Security Roles:
http://help.sap.com/saphelp_nw04/helpdata/en/c2/e13e4045796913e10000000a1550b0/frameset.htm
Regards,
Siddhesh

Problem running any web applications in netbean

I receive this error message whenever i wanted to run any web applications in my netbeans. The following messages usually come up and I want people to help me:
init:
deps-module-jar:
deps-ear-jar:
deps-jar:
library-inclusion-in-archive:
library-inclusion-in-manifest:
compile:
compile-jsps:
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
C:\usr\JavaProjects\LtlProjects\nbproject\build-impl.xml:568: Deployment error:
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
See the server log for details.
BUILD FAILED (total time: 1 minute 1 second)

Netbeans is unable to deal with alias host name "localhost". But it isn't the only local server.
Search for *::1 localhost* in your host file.
I have Windows OS so host file is in this folder
C:\Windows\System32\drivers\etc\hosts
add *127.0.0.1 localhost* to the hosts file above the existing entry
Should look like this:
127.0.0.1 localhost
::1 localhost
Stop server and close netbeans (if not already done).
Restart and test. Server startup should be quicker.

Problems with deployed web applications

Hi,
          currently we use Weblogic 6.0 and i decided to try Weblogic 6.1 beta. So i deployed our application which was working on Weblogic 6.0 on the newly installed Weblogic 6.1 beta. Now when i try to access my application i recieve the following error page:
          Compilation of 'D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java' failed:
          D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java:165: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable)
          (No more information available, probably caused by another error)
          Full compiler error(s):
          D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java:165: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable)
          pageContext.handlePageException(__ee);
          ^
          1 error
          Wed Jun 20 17:27:28 EEST 2001
          Does anyone know what could cause the problem ?
          Any help will be appreciated.
          Bybye.
          [att1.html]


          I have the same problem. My apps work in WebLogic 6.0, but not in 6.1 beta. Is
          it compatibility issue?
          Andi
          "Michael Li" <[email protected]> wrote:
          >Hi all,
          >
          >Anybody resolve this problem yet? We are experiencing the same problem
          >here.
          >
          >Thanks,
          >Michael
          >
          >===
          >"Evgenya Borisenko" <[email protected]> wrote in message
          >news:[email protected]...
          >Sure,
          >here goes:
          >
          >####<10:23:37 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.html: init>
          >####<10:23:37 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.html: Using standard I/O>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >init>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >param verbose initialized to: true>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >param packagePrefix initialized to: jsp_servlet>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >param compilerclass initialized to: javac>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >param srcCompiler initialized to weblogic.jspc>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >param superclass initialized to null>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >param workingDir initialized to:
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >param pageCheckSeconds initialized to: 1>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >initialization complete>
          >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >*.jsp:
          >pageCheckSeconds over-ruled in JSPServlet to : 1>
          >####<10:23:45 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >Generated java file:
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
          >ervlet\_ngroot\_web\__index.java>
          >####<10:23:53 EEST 24/06/2001> <Error> <HTTP> <evgenya> <evgyServer>
          ><ExecuteThread: '11' for queue: 'default'> <> <> <101046>
          ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
          >Compilation of
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
          >ervlet\_ngroot\_web\__index.java failed:
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
          >ervlet\_ngroot\_web\__index.java:165:
          >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext
          >cannot be applied to (java.lang.Throwable)
          > pageContext.handlePageException(__ee);
          > ^
          >1 error
          >>
          >java.io.IOException: Compiler failed
          >executable.exec(java.lang.String[d:\bea\jdk131\bin\javac.exe, -classpath,
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotd
          >elete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_
          >evgyServer\WEB-INF\lib\993367393172activation.jar;D:\bea\wlserver6.1_beta\.\
          >config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_t
          >mp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367393212ant.j
          >ar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyS
          >erver\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\
          >WEB-INF\lib\993367393532bsf.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\ap
          >plications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_
          >evgyServer_WebApp_evgyServer\WEB-INF\lib\993367393613concurrent_classes.jar;
          >D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServ
          >er\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB
          >-INF\lib\993367393673cos.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\appli
          >cations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evg
          >yServer_WebApp_evgyServer\WEB-INF\lib\993367393763dbConnBroker.jar;D:\bea\wl
          >server6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_com
          >p51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\
          >993367393773jasper.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\application
          >s\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServe
          >r_WebApp_evgyServer\WEB-INF\lib\993367393823java40.jar;D:\bea\wlserver6.1_be
          >ta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-I
          >NF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394103
          >jaxp.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete
          >_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyS
          >erver\WEB-INF\lib\993367394133jsdt.jar;D:\bea\wlserver6.1_beta\.\config\mydo
          >main\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgy
          >Server_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394263junit.jar;D:\bea
          >\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_
          >comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\l
          >ib\993367394324Jwap-0.7.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applic
          >ations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgy
          >Server_WebApp_evgyServer\WEB-INF\lib\993367394354log.jar;D:\bea\wlserver6.1_
          >beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB
          >-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\9933673943
          >74mail.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdele
          >te_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evg
          >yServer\WEB-INF\lib\993367394404orajdbc816-12.jar;D:\bea\wlserver6.1_beta\.\
          >config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_t
          >mp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394484parse
          >r.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_ev
          >gyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServ
          >er\WEB-INF\lib\993367394514servlet.jar;D:\bea\wlserver6.1_beta\.\config\mydo
          >main\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgy
          >Server_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394544webserver.jar;D:
          >\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-I
          >NF\lib\993367394584xalan.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\appli
          >cations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evg
          >yServer_WebApp_evgyServer\WEB-INF\lib\993367394634xerces.jar;D:\bea\wlserver
          >6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442
          >\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367
          >394914_log.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnot
          >delete_evgyServer\wl_comp51442\WEB-INF\classes;D:\bea\wlserver6.1_beta\confi
          >g\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_wa
          >r_evgyServer_evgyServer_WebApp_evgyServer;D:\bea\wlserver6.1_beta\.\config\m
          >ydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_e
          >vgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\jaxp.jar;D:\bea\wlserver6
          >..1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\
          >WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\xerces.
          >jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgy
          >Server\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer
          >\WEB-INF\lib\crimson.jar;d:\bea\jdk131\jre\lib\rt.jar;d:\bea\jdk131\jre\lib\
          >i18n.jar;d:\bea\jdk131\jre\lib\sunrsasign.jar;d:\bea\jdk131\jre\classes;.;D:
          >\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_evgyServer\WEB-INF
          >\lib\xerces.jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_
          >evgyServer\WEB-INF\lib\xalan.jar;D:\bea\wlserver6.1_beta\config\mydomain\app
          >lications\WebApp_evgyServer\WEB-INF\lib\mail.jar;D:\bea\wlserver6.1_beta\con
          >fig\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\activation.jar;.\lib
          >\weblogic_sp.jar;.\lib\weblogic.jar;D:\bea\wlserver6.1_beta\config\mydomain\
          >applications\WebApp_evgyServer\WEB-INF\lib\bsf.jar;D:\bea\wlserver6.1_beta\c
          >onfig\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\concurrent_classes
          >..jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_evgyServer\
          >WEB-INF\lib\cos.jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\Web
          >App_evgyServer\WEB-INF\lib\dbConnBroker.jar;D:\bea\wlserver6.1_beta\config\m
          >ydomain\applications\WebApp_evgyServer\WEB-INF\lib\log.jar;D:\bea\wlserver6.
          >1_beta\config\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\orajdbc816
          >-12.jar;D:\bea\wlserver6.0\config\mydomain\applications\WebApp_evgyServer\WE
          >B-INF\classes, -d,
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer,
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
          >ervlet\_ngroot\_web\__index.java])
          > at
          >weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.jav
          >a:575)
          > at
          >weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:354)
          > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:360)
          > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:181)
          > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:149)
          > at
          >weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:34
          >4)
          > at
          >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >:240)
          > at
          >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >:284)
          > at
          >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >:200)
          > at
          >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          >ntext.java:2279)
          > at
          >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          >:1923)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          >
          >hope that helps.
          >10x alot.
          >"Srinagesh Susarla" <[email protected]> wrote in message
          >news:[email protected]...
          >can u send the server side error-message!
          >thanks
          >nagesh
          >Evgenya Borisenko wrote:
          >Hi, currently we use Weblogic 6.0 and i decided to try Weblogic 6.1 beta.
          >So
          >i deployed our application which was working on Weblogic 6.0 on the newly
          >installed Weblogic 6.1 beta. Now when i try to access my application
          >i
          >recieve the following error page: Compilation of
          >'D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServe
          >r\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_
          >servlet\_ngroot\_web\__index.java' failed:
          >
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
          >ervlet\_ngroot\_web\__index.java:165:
          >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext
          >cannot be applied to (java.lang.Throwable)
          >(No more information available, probably caused by another error)
          >
          >
          >Full compiler error(s):
          >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
          >\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
          >ervlet\_ngroot\_web\__index.java:165:
          >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext
          >cannot be applied to (java.lang.Throwable)
          > pageContext.handlePageException(__ee);
          > ^
          >1 error
          >
          >
          >Wed Jun 20 17:27:28 EEST 2001 Does anyone know what could cause the problem
          >? Any help will be appreciated.Bybye.
          >
          >

Accessing files from custom web application

I have created a JSP application using UIX components that you can search for files within in IFS. After searching for the files I want the user to click a link and access the document, much like the webui interface in the out of the box IFS. I'm able display the list of files found but I'm not able to allow the user to click the in MY APPLICATION to see the files. What would be the url to access these files that are stored in IFS. PLEASE HELP.
Jeff

Hi,
I also have the same problem .
I have to open the document from the repository after clicking on the link and end user should be able to edit and save it in the same place in the repository.
Can you suggest me any solution if you have found?

EJB accessing web application classes

Hi,
what is the right method to enable packaged EJB to access classes of a
web application? Packaging both the EJB and web application in same
ear is not possible in this situation. We are running WebLogic 6.0 and
ejb is in
wlserver6.0/config/mydomain/applications/EJB.jar
and the classes it should use are in
wlserver6.0/config/mydomain/applications/application_name/WEB-INF/classes,
i.e. not packed into war -package. adding
wlserver6.0/config/mydomain/applications/application_name/WEB-INF/classes
to WebLogic's CLASSPATH enables the ejb to deploy but seems to screw
other deployments.

Please address calling and EJB from a JSP using the EJB to JSP tags...?I'm throwing
ClassCast errros on Object...
William Kemp <[email protected]> wrote:
This is addressed numerous times in this newsgroup and others. So, if
you are
insterested in additional explanations, a search of the newsgroups will
be
productive.
The WLS 6.x classloading scheme for enterprise apps, ejbs, and webapps
does
not permit and ejb to access webapp classes in the WEB-INF/classes directory
unless those classes are placed in the java system classpath, which,
you have
found, creates other problems.
If classes are needed by both webapp and ejb, place them in a utility
jar file
that is packaged in the ear with the ejb, or webapp, or both, and refer
to
them with the Class-Path manifest directive in the ejb jar file or the
webapp
war file.
For the details, see:
http://e-docs.bea.com/wls/docs61/programming/packaging.html#1029830
and the 7.0 stuff is good, too:
http://edocs.bea.com/wls/docs70/programming/classloading.html#1029830
Bill
janne wrote:
Hi,
what is the right method to enable packaged EJB to access classes ofa
web application? Packaging both the EJB and web application in same
ear is not possible in this situation. We are running WebLogic 6.0and
ejb is in
wlserver6.0/config/mydomain/applications/EJB.jar
and the classes it should use are in
wlserver6.0/config/mydomain/applications/application_name/WEB-INF/classes,
i.e. not packed into war -package. adding
wlserver6.0/config/mydomain/applications/application_name/WEB-INF/classes
to WebLogic's CLASSPATH enables the ejb to deploy but seems to screw
other deployments.

Authentication in clustered web application without sticky session

I have built JSP/Servlet/Struts application in the past on a cluster of app servers. Each app server has its own JVM running the Servlel Container. All of the HTTP requests come into a hardware load balancer, which directs the requests to one of the app servers in the cluster.
I have wanted to use the Java HttpSession management without any kind of distributed session provided by the app server. We have used "sticky" sessions. The application writes a cookie to the client on the first request. The load balancer looks for that cookie on subsequent requests and directs the request to the server that originally wrote the cookie. This ensures that all requests within the same session are handled by the same application server. This also means that if I do request.getSession().setAttribute("authenticated",true) on one request, when I do request.getSession().getAttribute(authenticated) on subsequent requests in the same session, I can be sure the value will not be null. This allows me to create a filter that checks for that session attribute on each request, and if it is false or null, redirect the request to some sort of login page. Otherwise I can be sure the user has logged in.
I want to build a stateless/non-session based application that can still handle authentication. What I mean by that is that I don't want the load balancer to have to send requests for the same session all to the same server. I would like the load balancer to send each request where ever it wants. That means the simple authentication example I explained in the last paragraph would not work. The user could login on server A, but then on a subsequent request during the same "session", the user's request could be handled by server B. In that case, the session attribute would be null, and the app would think that the user has not logged in.
My application can require that users have cookies enabled, so therefore I can assume the user is accepting cookies (I would have something to check that and redirect the user to an error page saying "turn cookies on" if cookies weren't on). I think one thing that I could do is use encrpytion with a key that is shared between all the servers in the cluster. For example, user logins in on server A, server A writes a cookie with the contents "username,1109272102009". The first part being the username that the user successfully authenticated as and the second part being a timestamp for when the cookie was created. The contents of the actual cookie would be encrypted and I would send the ciphertext as the value of the cookie. When server B gets the cookie, it can decrypt the ciphertext (using the same key as was used to encrypt the data on server A), and check that the username is valid and that the timestamp does not exceed some timeout. The timestamp in the cookie would then have to be updated for the next request.
So my question is (thanks for sticking with me and reading this really long post), has anyone done anything like this before? Is what I have described totally ridiculous or insecure? Are there any books or articles that describe a pattern similar to this that has been know to work well?

I have worked on a web site that did exactly that.
The cookie contained a little bit more information - there was a small amount of user data that were needed on heavily accessed pages.
You'll have a problem if your web application uses attributes. We solved this by keeping most stuff in hidden inputs (backed up by hidden input cryptographic checksums in places where forgery was a concern.) HttpSession attributes have some problems and gotchas.
A few possible fine tunings:
Add a random number to the cookie. Should make known plaintext attacks harder.
Add some extra stuff to the cookie, so that any random hex string that happens to decode to "xZoiyqw,15" isn't accepted. It's easy to try a million cookies until you get "<something>,<integer>" but getting "<something>,<integer>,HelloHowAreYou" is a lot harder.
Be paranoid in checking the format of the cookie. If you add a random number, check that it is all digits etc. Belt and suspenders: also check that the time stamp isn't in the future (allow e.g. 15 seconds future time, in case different servers' clocks are a bit off.)
Don't update the cookie at every hit, only if the time stamp is older than a couple of minutes. Saves encryption CPU power.
After encrypting, prepend a short version number to the cookie. E.g. if the hex cookie is ABCDEF, make it 1ABCDEF. If you later e.g. change the encryption algorithm, change version to 2 and you can easily skip any obviously non-decipherable cookies. A second version number within the cookie might or might not be useful.
Even though you can make random load balancing, consider not doing that. E.g. a server might pull the user's name from the database into memory cache. You get less database traffic and smaller caches if the user still goes to the same server. If a server goes down, only then switch him elsewhere. Downside though: if one server is "half alive" (doesn't respond to requests but alive enough so the load balancer doesn't notice the malfunction), all users bound to that server see a 100% failure.
Benchmark cookie decryption time when selecting the crypto algorithm. How many hits per second you can get and how many you need.
Guard your crypto keys like the crown jewels. Change them periodically and whenever someone in your company (especially IT department) gets the pink slip.

Web Application Designer - Columns and Navigation Block

Hello,
I have problems concerning a web application.
The names of the columns are not displayed and the columns are not displayed in the navigation block.
Maybe you have experience with this problem and can give me some hints.
I'm looking forward to your answer!
Best regards.

Hi,
see this thread for getting colum names:
Re: Accessing table column names from WAD
thnks.

Access problem in a web application

Similar Messages

Maybe you are looking for