Jsp:plugin problem

hi,
i am using jsp:plugin to handle applets.when i am placing the applet class file in the same jsp files directory itself its working.but,when i am placing the applet class file in the WEB-INF/classes directory it couldn't point the class file and its not working.here is the tag,
<jsp:plugin type="applet" code="SampleAppletExample" codebase="WEB-INF/classes" height="400" width="500">
</jsp:plugin>
what is the problem with the tag.how can i pont the class file from jsp:plugin tag.
any one knows please help me.
regards,
j.mouli

Hi,
Please check your codebase parameter again. That part of the directory (web-inf\classes is not visible to client i.e he cann't access it. By default the classes stored under web-inf\classes directory can be accessed from the jsp.
Please find the extract from apache site related to this.
"WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
For further information on this, please browse through the 'Standard Directory Layout' section at http://jakarta.apache.org/tomcat/tomcat-3.3-doc/appdev/deployment.html
Hope this helps.
Good Luck.
Gayam.Srinivasa Reddy
Developer Technical Support
Sun Micro Sysytems
http://www.sun.com/developers/support/

Similar Messages

  • Jsp:plugin codebase problem

    suppose the applet class is in
    TOMCAT_HOME/webapps/myapp/WEB-INF/classes/mypackage/applet.class
    what the corresponding codebase for the jsp:plugin should be?
    Thanks

    The WEB-INF/lib and WEB-INF/classes directories are off limits cannot be referenced.
    You must create and use another directory (I usually use jars) in your application's context to supply the applet.

  • Help for jsp plugin

    The applet is not showing image on applet when running through following url. Remember It runs by simple applet tag in html but not through <jsp:plugin tag in jsp file.
    the following two links for same inker.jar file.
    not ok not running=====>"http://mycgiserver.com/~aftmycgijsp/jhan3.jsp"
    ok runing==============>"http://mycgiserver.com/~aftmycgijsp/jhan3.html"
    a) Tum.class in inker.jar with Image.jpg contain following code:
    image2 = getImage(getCodeBase(),"Image.jpg");
    g.drawImage(image2,0,0,this);
    b) I am using following tags in my jsp file,
    jhan3.jsp
    <html>
    <head>
    <jsp:plugin type="applet" code="Tum.class" codebase="http://www.mycgiserver.com/~aftmycgijsp/applets/jhan" jreversion="1.2" archive="inker.jar" width="171" height="185" >
    <jsp:fallback>
    Plugin tag OBJECT or EMBED not supported by browser.
    </jsp:fallback>
    </jsp:plugin>
    </body>
    </html>
    c) and the source file in my browser appears for above jsp is translated as to me as,
    <html>
    <head>
    <object classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93" codebase="http://java.sun.com/products/plugin/1.2.2/jinstall-1_2_2-win.cab#Version=1,2,2,0" height="185" width="171">
    <param name="java_archive" value="inker.jar">
    <param name="java_codebase" value="http://www.mycgiserver.com/~aftmycgijsp/applets/jhan">
    <param name="java_code" value="Tum.class">
    <param name="type" value="application/x-java-applet;version=1.2">
    <comment><embed type="application/x-java-applet;version=1.2" codebase="http://java.sun.com/products/plugin/" height="185" width="171" java_archive="inker.jar" java_codebase="http://www.mycgiserver.com/~aftmycgijsp/applets/jhan" java_code="Tum.class">
    <noembed></comment>
    Plugin tag OBJECT or EMBED not supported by browser.
    </noembed></embed></object>
    </body>
    </html>
    please send any suggestions.

    This jsp:plugin tag should work. BUt the problem is that not showing image from jar file. but ok when used with html applet tag.

  • Is jsp:plugin supported in weblogic 5.1 or 6.0?

    I tried to compile %WEBLOGIC_ROOT%\examples\applets\phonebook12.jsp in WLS5.1.The generated servlet class(using a java decompiler to generate a source code or using anotepad to view the class file directly) still has <jsp:plugin> tag in it.jspc does NOT generate <object> or <embed> tag.weblogic6.0 jsp trouble shooting document says "If you see <jsp:plugin> ... anywhere in the (HTML) page, the syntax of the tag(original <jsp:plugin> tag) is not correct."For weblogic 5.1, this is the ONLY example jsp file containing <jsp:plugin> tag. In weblogic 6.0, there is NO jsp example which contains the <jsp:plugin> tag.I tried very simple jsp page with <jsp:plugin> tag (and a simple applet), I always see <jsp:plugin> tag in the generated HTML. Should it be <object> or <embed> tag??Could anyone tell me whether <jsp:plugin> is really supported in Weblogic5.1 and/or 6.0? If it is not supported yet or there are bugs to fix, please let me know, so I stop trying for now. I will appreciate greatly any help.ChenpingSoftware ArchitectBEZ Systems, Inc.
              

    hi, i have the same problem in WL5.1
              At last i have to use <applet> tag
              "Chenping Ni" <[email protected]> wrote in message
              news:3aa01e55$[email protected]..
              > I tried to compile %WEBLOGIC_ROOT%\examples\applets\phonebook12.jsp in
              WLS5.1.The generated servlet class(using a java decompiler to generate a
              source code or using anotepad to view the class file directly) still has
              <jsp:plugin> tag in it.jspc does NOT generate <object> or <embed>
              tag.weblogic6.0 jsp trouble shooting document says "If you see <jsp:plugin>
              ... anywhere in the (HTML) page, the syntax of the tag(original <jsp:plugin>
              tag) is not correct."For weblogic 5.1, this is the ONLY example jsp file
              containing <jsp:plugin> tag. In weblogic 6.0, there is NO jsp example which
              contains the <jsp:plugin> tag.I tried very simple jsp page with <jsp:plugin>
              tag (and a simple applet), I always see <jsp:plugin> tag in the generated
              HTML. Should it be <object> or <embed> tag??Could anyone tell me whether
              <jsp:plugin> is really supported in Weblogic5.1 and/or 6.0? If it is not
              supported yet or there are bugs to fix, please let me know, so I stop trying
              for now. I will appreciate greatly any help.ChenpingSoftware ArchitectBEZ
              Systems, Inc.
              

  • Jsp:plugin seems broken on WL 8.1

              Hi.
              I've tried using the <jsp:plugin> tag in a JSP page, conforming to Sun's JSP
              1.2 spec. It works alright with Tomcat, but it fails on WL8.1: the tag is passed
              as is into the resulting HTML.
              After hours of investigations, it seems that the WL server only transforms correctly
              the <jsp:plugin> tag, as long as there is no nested JSP syntax in it. However,
              the JSP 1.2 spec explicitely states that some parts of the <jsp:plugin> tag can
              be JSP expressions of the form <%=xxx%>. It is allowed, for instance, in the height
              and width attributes, and as applet attribute values in <jsp:param>.
              Is it a known problem? I have found no reference to this limitation in any BEA
              documentation.
              Thanks.
              Laurent Vaucher.
              

              Hi.
              I've tried using the <jsp:plugin> tag in a JSP page, conforming to Sun's JSP
              1.2 spec. It works alright with Tomcat, but it fails on WL8.1: the tag is passed
              as is into the resulting HTML.
              After hours of investigations, it seems that the WL server only transforms correctly
              the <jsp:plugin> tag, as long as there is no nested JSP syntax in it. However,
              the JSP 1.2 spec explicitely states that some parts of the <jsp:plugin> tag can
              be JSP expressions of the form <%=xxx%>. It is allowed, for instance, in the height
              and width attributes, and as applet attribute values in <jsp:param>.
              Is it a known problem? I have found no reference to this limitation in any BEA
              documentation.
              Thanks.
              Laurent Vaucher.
              

  • Is Tomcat 4's jsp:plugin tag hardwired to 1.2?

    Is Tomcat 4's <jsp:plugin > tag hardwired to version 1.2 of the JPI?
    I was absolutely horrified today at a job interview when, proudly navigating to the page containing the 1.4-demanding applet I embedded in the page using <jsp:plugin ...> the plugin installation dialogue came up -- asking whether they wanted to install the 1.2 plugin (up until recently, I had the applet's object tag embedded manually... switching to jsp:plugin was fairly recent).
    As it turns out, the <object> tag generated by Tomcat was specifying the download path for the 1.2 plugin, even though I specified jreversion="1.4" in the <jsp:plugin> tag:
    <OBJECT
       classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
       name="theApplet"
       width="550" 
       height="400" 
       align="middle" 
       codebase="http://java.sun.com/products/plugin/1.2.2/jinstall-1_2_2-win.cab#Version=1,2,2,0">The "clsid" value can be changed in web.xml by changing the jsp servlet's "ieClassId" initParam, but as far as I can tell there's NO mechanism for changing the "codebase" value anywhere.
    Is the <jsp:plugin> tag (under Tomcat 4, at least) just useless for Applets that must have 1.4, or is there a configuration parameter somewhere to set the "codebase" value generated by the tag?
    I know I could always put the manually-specified code back in, but I'd prefer to stay with the <jsp:plugin> tag if possible just because it makes the jsp source cleaner. What's strange is that nobody seems to have complained about that problem on the usual places (Usenet/dejanews/Google, jguru.com, etc). Whether that's just because nobody writes applets that actually demand 1.4, or whether everybody who does just embeds the <object> tag manually, I'm not sure.
    In any case, I'm trying to figure out how to make <jsp:plugin> generate the right HTML for 1.4-using applets... or whether it's even possible.

    Sigh. I found it. It's actually specified as the "iepluginurl" property of the <jsp:plugin> tag.
    <emotion:frustration variation="anger">
    Now I just need to figure out what *$%!# value to use for it.
    The JPI's developer guide has to be the worst document I've ever seen from Sun. Normally, Sun's documents are good. Often, exceptionally so. But the JPI guide... well, after reading http://java.sun.com/j2se/1.4.1/docs/guide/plugin/developer_guide/using_tags.html multiple times, I'm still not sure what #$%^&* URL corresponds to "The newest released JPI equal to or newer than 1.4.0". The only URL on the whole page that they even imply works is hardwired to 1.4.0, and in the same breath they imply that every other codebase URL on the page is wrong, hypothetical, and shouldn't be used... oh, and for that matter, the 1.4_0 one shouldn't really be used ether, because it might change in the future. Grrrrr.
    If there's a pattern to the following URLs (all used on the same page) that's supposed to illustrate something besides abyssmally bad editing and apparent indecision, I haven't seen it yet:
    http://java.sun.com/products/plugin/autodl/jinstall-1_4-windows-i586.cab#Version=1,4,0,0
    http://java.sun.com/products/plugin/1.4/jinstall-14-win32.cab#Version=1,4,0,mn
    http://java.sun.com/products/plugin/autodl/jinstall-1_4-windows-i586.cab#Version=1,4,1,mn
    http://java.sun.com/products/plugin/autodl/jinstall-1_4_0-win.cabHmmm. Let's see here. They're all the same up to http://java.sun.com/products/plugin, but from that point one diverges into /1.4/, while the others continue into /autodl/. But even past that point, two imply that the filename follows the pattern jinstall-1_4-windows-i586.cab#Version=1,4,x,* ... but whether developers who really, truly, don't care about the specific maintenance release should use "0" or "mn" is left up in the air.
    Furthermore, the ONE URL on the entire page that they come halfway close to implying will work is the last one I listed above, which itself goes totally against whatever hypthetical pattern they were trying to imply with the other three. For now I'll probably stick the last one listed as the parameter because it's the only one they actually come out and say will work, but I suspect the first one is probably the "right" one.
    Of course, there's always the matter of Macintosh users running IE. Or Windows users running Mozilla (which is technically Netscape, but uses MSIE ActiveX plugins). Does Mozilla get fed the value of "iepluginurl", or the value of "nspluginurl"? Sigh.
    </emotion:frustration>

  • Weired behavior of jsp:plugin tag

    Hi.
    When I use <jsp:plugin type="applet".....></jsp:plugin> tag, jsp page shows a applet correctly in IE but not in mozilla(1.7). I've tried to solve this problem and found that if I use <applet></applet> tag it works fine both of them.
    Does anyone have idea? the reason of this, and isn't there anyway to use jps:plugin tag to work correctly in both browers?

    What version of Jdk are you using? The Java plugin is not consistent across browsers and browser versions.
    The jsp:plugin tag gets coverted to the OBJECT tag after compliation.
    Just go through this page to find out which tag suits your need.
    http://java.sun.com/products/plugin/versions.html
    This link might also be helpful to you.
    http://www.mail-archive.com/[email protected]/msg32719.html

  • JSP Plugin tag for applets with codebase - WLS 6.1 sp2

              Could someone please tell me what I am doing wrong?
              I have the following Plugin tag in my JSP.
              <jsp:plugin type="applet"
              code="com.xxx.efm.frontend.view.EFMApplet"
              codebase="/lib"
              archive="applets/EFMFrontend.jar, EfmCommon.jar, TrimmedWeblogic.jar, dom4j-full.jar,
              /classes/"
              jreversion="1.3"
              nspluginurl="http://java.sun.com/products/plugin/1.3/plugin-install.html"
              iepluginurl="http://java.sun.com/products/plugin/1.3/jinstall-131-win32.cab">
                   <jsp:params>
                        <jsp:param name="Delimiter" value="<%=delimiter%>" />
                        <jsp:param name="ComponentMap" value="<%=componentMapValues%>" />
                        <jsp:param name="ServerConfig" value="<%=serverConfigValues%>" />
                        <jsp:param name="GUIConfig" value="<%=guiConfigValues%>" />
                   </jsp:params>
              </jsp:plugin>
              I am trying to load the JSP using Netscape 4.7. When I don't have a plug-in installed
              the page
              displays "Click here to get the plugin". On clicking on it the browser pops up
              a "Plugin not loaded" dialog.
              All this is fine except that the dialog says it can retrieve the plugin from "/lib".
              When I click on
              "Get the plugin" button the new browser window tries to load the URL: http://localhost:2002/lib/?application/x-java-applet;version=1.3.
              It totally ignores the netscape URL for plugin. Something similar happens with
              IE as well.
              I tried the same JSP without the codebase tag and all worked fine (except for
              my applets). Yeah, I can append a "/lib" to each of
              my jars in my archive and it just might work. But should I be doing anything different?.
              Any help is appreciated.
              Thanks,
              Gopal
              

    I am facing the same problem with netscape (4.7x). Gopal, did you find any
              solution?
              IE works fine for me. I use the foll pluginurl
              iepluginurl="http://java.sun.com/products/plugin/1.3/jinstall-13-win32.cab#V
              ersion=1,3,1,1"
              _Jp
              "Gopal" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Could someone please tell me what I am doing wrong?
              >
              > I have the following Plugin tag in my JSP.
              >
              > <jsp:plugin type="applet"
              > code="com.xxx.efm.frontend.view.EFMApplet"
              > codebase="/lib"
              > archive="applets/EFMFrontend.jar, EfmCommon.jar,
              TrimmedWeblogic.jar, dom4j-full.jar,
              > /classes/"
              > jreversion="1.3"
              >
              nspluginurl="http://java.sun.com/products/plugin/1.3/plugin-install.html"
              >
              iepluginurl="http://java.sun.com/products/plugin/1.3/jinstall-131-win32.cab"
              >
              >
              > <jsp:params>
              > <jsp:param name="Delimiter" value="<%=delimiter%>" />
              > <jsp:param name="ComponentMap" value="<%=componentMapValues%>" />
              > <jsp:param name="ServerConfig" value="<%=serverConfigValues%>" />
              > <jsp:param name="GUIConfig" value="<%=guiConfigValues%>" />
              > </jsp:params>
              > </jsp:plugin>
              >
              > I am trying to load the JSP using Netscape 4.7. When I don't have a
              plug-in installed
              > the page
              > displays "Click here to get the plugin". On clicking on it the browser
              pops up
              > a "Plugin not loaded" dialog.
              > All this is fine except that the dialog says it can retrieve the plugin
              from "/lib".
              > When I click on
              > "Get the plugin" button the new browser window tries to load the URL:
              http://localhost:2002/lib/?application/x-java-applet;version=1.3.
              > It totally ignores the netscape URL for plugin. Something similar happens
              with
              > IE as well.
              >
              > I tried the same JSP without the codebase tag and all worked fine (except
              for
              > my applets). Yeah, I can append a "/lib" to each of
              > my jars in my archive and it just might work. But should I be doing
              anything different?.
              > Any help is appreciated.
              >
              > Thanks,
              > Gopal
              

  • Jsp plugin error ----

    Hi
    I want to display applet in a browser ,which is in a remote system ...for that i am using jsp to display it..
    in the code i wrote like the following .... but i am getting error ...any help would be appreciated....error msg also pasted below...
    <%@ page language ="java" contentType = "text/html" %>
    <html> <head>
    <title>Plugin Example</title>
    </head>
    <body>
    <h3> I have done it ...</h3>
    <jsp:plugin type = "applet" code = "ViewerApplet.class"
    codebase = "http://javasystem:8080/JViewer1/viewer/paragon" width = "500" heigth ="500">
    <jsp:fallback>There is a problem with your browser ...</jsp:fallback>
    <jsp:params >
    <jsp:param name="numpages" value="3" />
    <jsp:param name="fileurl" value="" />
    <jsp:param name="pageurls"
    value="http://javasystem:8080/examples/images/testimages/anim-[p].tif" />
    <jsp:param name="defaultzoom" value="75%" />
    </jsp:params>
    </jsp:plugin>
    </body></html>
    Error .....................
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException: /view.jsp(9,0) jsp:plugin not closed
         at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94)
         at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:428)
         at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:126)
         at org.apache.jasper.compiler.Parser.parsePlugin(Parser.java:643)
         at org.apache.jasper.compiler.Parser.parseAction(Parser.java:669)
         at org.apache.jasper.compiler.Parser.parseElements(Parser.java:803)
         at org.apache.jasper.compiler.Parser.parse(Parser.java:122)
         at org.apache.jasper.compiler.ParserController.parse(ParserController.java:199)
         at org.apache.jasper.compiler.ParserController.parse(ParserController.java:153)
         at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:227)
         at org.apache.jasper.compiler.Compiler.compile(Compiler.java:369)
         at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
         at java.lang.Thread.run(Thread.java:536)

    "org.apache.jasper.JasperException: /view.jsp(9,0) jsp:plugin not closed"
    Looks like you did not close the jsp:plugin tag. Double check your quotes, make sure you do not have an extra one, or are missing one (although the code you posted looks okay)... also, try removing the space between the attribute = "value" pairs in the tag, ie:
        <jsp:plugin type="applet" code="ViewerApplet.class"
                    codebase="http://javasystem:8080/JViewer1/viewer/paragon"
                    width="500" heigth="500">
    //instead of:
        <jsp:plugin type = "applet" code = "ViewerApplet.class"
                    codebase = "http://javasystem:8080/JViewer1/viewer/paragon"
                    width = "500" heigth = "500">

  • How can I return some values from an applet invoked by jsp:plugin tag

    My JSP is something like that:
    <html>
         <head>
                 <title> . . . </title>
         </head>
         <script>
              function getValueFromApplet()
                   var src = document.pinApplet.checkPin();
                   document.myForm.j_username.value = document.pinApplet.tokenizeName(src);
                   alert(document.myForm.j_username.value);
                   document.myForm.j_password.value = document.pinApplet.tokenizePassword(src);
                   alert(document.myForm.j_password.value);
         </script>
            <body>
                    <jsp:plugin type="applet"
                          code="PinApplet.class"
                       codebase="/idp"
                       name="pinApplet"
                                width="300"
                                height="300">
                         <jsp:fallback> Authentication Form is not supported by the browser </jsp:fallback>
              </jsp:plugin>
                    <form action="https://xxx.xxx.xxx"
                   name="myForm"
                   method="post" onSubmit="return getValueFromApplet()">
              <table>
                   <td><input type="submit" value="OK" >
                   <td><input type="hidden" id="j_username" name="j_username" value=""></td>
                   <td><input type="hidden" id="j_password" name="j_password" value=""></td>
              </table>
              </form>
         </body>checkPin() returns "alice--alice"
    tokenizeName() returns the first token: alice
    tokenizePassword() returns the second token: alice
    When I test the applet in the IDE, it returns the values properly, but not in the JSP invokation.

    evnafets wrote:
    javascript will not be executing on the server. You can rule that one out.
    Is your Applet being initialised correctly?
    Where have you got the classes for it? I think the applet doesn't need any kind of initialization, because it doesn't have any variables and all the process is made in the method called by onsubmit()
    The applet is composed only by one class and I'm totally sure that the class is placed in the correct place.
    evnafets wrote:
    I would say put in a couple more alerts - one before the call to the applet, one after.
    put some logging statements in your applet to see if it gets there.In the javascript, there are two alerts between the three calls to the applet. Where do you advise me to put more alerts?
    I don't understand what do you refer when you say "logging statements"
    I am going to test again the call to the applet in order to find some kind of code that can be invalid or that can make the function to "crash"

  • Re: [iPlanet-JATO] sp3 jsp compiler problem

    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text
    substitution situations, and as a completely independent tool its use is not
    restricted to migration situations (or file types for that matter).
    Second, I sympathize with the unfortunate trouble you are experiencing due to
    Jasper's (perhaps more strict) compilation, but in what way did the iMT
    automated translation contribute to these inconsistencies that you cited?
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a
    translation situation, the only way "OnClick" would have been introduced was if
    it had been part of the pre-existing project's "extraHTML" (which was written
    by the original customer and just passed through unchanged by the iMT) or if it
    was added manually by the post-migration developer.
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
    similar to the OnClick situation described above?
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no
    equivalent in the NetDynamics world, so any content tags in your code must have
    been introduced by your developers manually. Its a shame that jasper is so
    particular, but the iMT could not help you out here even if we wanted to. The
    constants that are used by the iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
    only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    [Non-text portions of this message have been removed]

    Thanks a lot Matt and Mike for your prompt replies.
    I agree completely that iMT doesn't introduce the inconsistencies.
    About the three cases I mentioned, the third one happens only in
    manually created JSPs. So it has nothing to do with iMT. The first
    two are mainly due to the existing HTML code, as you rightly pointed
    out.
    The reason I made the suggestion is since we know that case 1 and 2
    won't pass the japser compiler in sp3, we have to do something about
    it. The best place to do this, in my mind, is iMT. Of course, there
    might be some twists that make it impossible or difficult to do this
    kind of case manipulation or attribute discard.
    Weiguo
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
    tool its use is not restricted to migration situations (or file types
    for that matter).
    >
    Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
    in what way did the iMT automated translation contribute to these
    inconsistencies that you cited?
    >
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
    introduced was if it had been part of the pre-existing
    project's "extraHTML" (which was written by the original customer and
    just passed through unchanged by the iMT) or if it was added manually
    by the post-migration developer.
    >
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
    >
    >
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
    in your code must have been introduced by your developers manually.
    Its a shame that jasper is so particular, but the iMT could not help
    you out here even if we wanted to. The constants that are used by the
    iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
    see, the only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    >
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as
    what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    >>
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Expressions not evaluating properly in jsp:plugin tag

    Hi there, running OC4J as Oracle9iAS (1.0.2.2.1)
    In the JSP1.1 spec dynamic expressions in the jsp:plugin <param> tag are clearly specified as below:
    <jsp:params>
    [ <jsp:param name="parameterName" value="{parameterValue | <%= expression %>}" /> ]+ </jsp:params>
    Unfortunately, attempting this in OC4J, the expression is simply displayed as a static String, for example the following JSP source:
         <jsp:params>
              <jsp:param name="rootSubAssembly" value="<%=rootSubAssembly%>" />
         </jsp:params>
    Would output "<%=rootSubAssembly%>" as the parameter value, rather than the dynamic value specified in the JSP above.
    Any ideas? We'd like to benefit from using the plugin tag over object/applet if at all possible.

    Hi there, running OC4J as Oracle9iAS (1.0.2.2.1)
    In the JSP1.1 spec dynamic expressions in the jsp:plugin <param> tag are clearly specified as below:
    <jsp:params>
    [ <jsp:param name="parameterName" value="{parameterValue | <%= expression %>}" /> ]+ </jsp:params>
    Unfortunately, attempting this in OC4J, the expression is simply displayed as a static String, for example the following JSP source:
         <jsp:params>
              <jsp:param name="rootSubAssembly" value="<%=rootSubAssembly%>" />
         </jsp:params>
    Would output "<%=rootSubAssembly%>" as the parameter value, rather than the dynamic value specified in the JSP above.
    Any ideas? We'd like to benefit from using the plugin tag over object/applet if at all possible.

  • Can't get jsp:plugin to work with jb5

    I am trying to get a Swing applet compiled with JDK 1.3.1 to run on a jsp page using the <jsp:plugin> tag. At this stage it is a ridiculously simple applet (just some JLabels and JTextFields) but I can't get it to work. Here is the jsp code:
    <jsp:plugin type="applet" code="nz.astarte.ganttapplet.GanttApplet"
    codebase="./WEB-INF/classes" jreversion="1.3.1"
    width="400" height="175">
    <jsp:fallback>
    Plugin support could not be determined
    </jsp:fallback>
    </jsp:plugin>
    When I run it in the jb5 ide nothing shows up at all. OK, I figured the ide doesn't support the plugin, so leaving the ide running (which provides me with a web server) I go into IE (version 5) and enter the url to the page, which is http://localhost:8080/AppletCommunications/GanttApplet.jsp
    I get the page, and the gray box saying loading the applet but the plugin console tells me:
    load: class nz.astarte.ganttapplet.GanttApplet not found.
    java.lang.ClassNotFoundException: java.io.FileNotFoundException: http://localhost:8080/AppletCommunications/WEB-INF/classes/nz/astarte/ganttapplet/GanttApplet.class
    Why not? Under the directory where the jsp page is located is the directory structure WEB-INF/classes/nz/astarte/ganttapplet and in that directory is a GanttApplet.class file.
    I cannot understand why it isn't found. Do applets work with the jb5 ide? Is there something blindingly obvious that I've missed?
    Thanks, Andrew

    I appear to have solved it, but it is not clear to me why.
    I created a jar file of the required classes, and placed it in the same directory as the jsp file. My jsp code then looked like:
    <jsp:plugin type="applet" code="nz.astarte.ganttapplet.GanttApplet"
    codebase="."
    archive="GanttApplet.jar"
    jreversion="1.3.1"
    width="400" height="175">
    <jsp:fallback>
    Plugin support could not be determined
    </jsp:fallback>
    </jsp:plugin>
    This works fine. However I would expect to be able to move the jar file to some other directory, so that the jar file and jsp files are separated. I spent hours trying to work out why it wouldn't work when I had the jar
    file in WEB-INF/classes (under the jsp file directory) and had codebase="WEB-INF/classes/". In the end I put the jar file into a directory I defined separately called wotnot and defined codebase="wotnot/"
    Now it works. However I still think I should be able to have the jar file anywhere, including WEB-INF/classes and would love for someone to tell me why not!
    Thanks, Andrew

  • How to use jsp:plugin type="applet" in jsp

    Hi ,
    I have a JSP File.
    How to use jsp:plugin tag in that.
    When I specify the file name in code="applet.class" Then it is giving an error saying that It could not find the class.
    What is the solution for this.

    its not working.. it shows exception class not found exception.
    i have placed the jsp and applet class in the same folder. but its not working.
    jsp file path : OracleSpatial\mypackage\webmap.jsp
    applet class : OracleSpatial\mypackage\demoApplet.class
    demoApplet class inside package "mypackage".
    code inside JSP is :
    <jsp:plugin type="applet"
    code="mypackage.demoApplet.class" width = "100%" height = "100%" >
    </jsp:plugin>

  • How to use jsp:plugin action with type = bean

    Hi everybody,
    I'm new to JSP so it could be a stupid question but I'm wondering how can I use a jsp:plugin action with a type equal to "bean".
    Everyone is talking about type equal to applet so the browser can display this applet but if the type will be a bean so then
    does it mean I can send a javaBean class to the client?
    If yes, then can the javaBean object be executed on a client machine?
    Or maybe I'm wrong. I don't know how it works.
    Please give me a resolution.
    Thanks,
    Rafal.

    its not working.. it shows exception class not found exception.
    i have placed the jsp and applet class in the same folder. but its not working.
    jsp file path : OracleSpatial\mypackage\webmap.jsp
    applet class : OracleSpatial\mypackage\demoApplet.class
    demoApplet class inside package "mypackage".
    code inside JSP is :
    <jsp:plugin type="applet"
    code="mypackage.demoApplet.class" width = "100%" height = "100%" >
    </jsp:plugin>

Maybe you are looking for

  • Apps wont open all photos album

    Since updating to the new software whenever I want to send a picture from my 'All Photos' album via whats app, imessage or upload to instagram or instacollage etc, my phone freezes. Any help with this would be great as it is really frustrating! I am

  • HT1677 Pop-up Blocker still prompting to Allow

    I have pop-up blocker disabled in Safari for iPad.  However, I still get prompts to "Allow" or decline popups.  I don't want to prompted. I just want the popups to open.  How do I do this?

  • Controlling VI from inside the Sub-Panel

    I have a prog which is used as the Main prog and has a sub-panel in it,whenever an event is occured iam popping up an VI,which should be inside the sub-panel,when i press the stop button which is inside the sub-panel,the vi should stop

  • Stamps slow or freeze

    I work for a firm where we are using stamps in Adobe for 'tick marks', which give the reader certain information about the document. We have been using the stamps for a while and just updated our Adobe Professional with the 8.1.2 update. I am not sur

  • Is there a picture which indicates that something is still running?

    I need a small picture to indicate that my experiment is still running, something like a time dial with something moving. Is there a java versioned code for such a thing? Thank you.