korolevc

Members
 View Profile  See their activity

  • Content count

    4

  • Joined

  • Last visited

Posts posted by korolevc

  1. Posted · Report reply

    I'm not compiling the jsps from an IDE. I've tried compiling it from our Ant build, calling the weblogic appc task and also by just copying the jsp files into the war of a running server and trying to access the jsp and force a compilation. Both instances failed.

     

     

     

    As I mentioned, I did get around the compilation error, but I have encountered something else now. I don't want to put those jsp files in the root of my war. Let's say I want them in a subdirectory of my war called graph. So, the graph directory contains FCExporter.jsp, FCExporterError.jsp and the Resources directory. The export no longer works. It seems that somewhere in the export code, it is looking for the Resources directory in the root of the war. I figured this out because I was able to export after copying the Resource directory from my graph directory to the root of the war. And if I then remove the Resource directory from my graph directory, the export also fails because there is code elsewhere that tries to access the resource jsps relative to FCExporter.jsp. I don't want to have two Resources directories in my war. Can someone look into this? I can send in a support request if that is necessary.

     

     

     

    Thanks.

  2. Posted · Edited by Guest · Report reply

    Stupid question, but how do you check the compliance level? And also, how do you set it? Actually, I was able to get around the compilation error by modifying the FCExporter.jsp file. Here's what I did:

     

     

     

    <jsp:useBean id="exportBean" scope="request" class="com.fusioncharts.exporter.beans.ExportBean">

     

    <jsp:setProperty name="exportBean" property="metadata" value="<%=localExportBean.getMetadata()%>"/>

     

    <jsp:setProperty name="exportBean" property="stream" value="<%=localExportBean.getStream()%>"/>

     

    <%--<jsp:setProperty name="exportBean" property="exportParameters" value="<%=localExportBean.getExportParameters()%>"/>--%>

     

    &lt/jsp:useBean>

     

    <% // TODO: commented out setProperty above and replaced with this statement.

     

    exportBean.setExportParameters(localExportBean.getExportParameters());

     

    %>

     

     

     

    As you can see, I commented out the last setProperty jsp tag and manually called the setExportParameters in the exportBean. This worked, but I don't like having to modify your files.

  4. Posted · Report reply

    When trying to precompile the FCExporter.jsp using weblogic 10.3, I get the following error:

    [jspc] Compiling /fusionCharts/FCExporter.jsp

    [jspc] Compiling /fusionCharts/FCExporterError.jsp

    [jspc] Compiling /fusionCharts/Resources/FCExporter_IMG.jsp

    [jspc] Compiling /fusionCharts/Resources/FCExporter_PDF.jsp

     

    There are 1 nested errors:

    weblogic.utils.compiler.ToolFailureException: jspc failed with errors :weblogic.

    servlet.jsp.CompilationException: FCExporter.jsp:183:46: This property is not wr

    itable.

      <jsp:setProperty name="exportBean" property="exportParameters" value="<%

    =localExportBean.getExportParameters()%>"/>

      ^----------------^

     

      at weblogic.servlet.jsp.jspc20.runBodyInternal(jspc20.java:431)

      at weblogic.servlet.jsp.jspc20.runJspc(jspc20.java:202)

      at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:236)

      at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:362

    )

      at weblogic.application.compiler.WARModule.compile(WARModule.java:236)

      at weblogic.application.compiler.flow.CompileModuleFlow.compileModules(C

    ompileModuleFlow.java:103)

      at weblogic.application.compiler.flow.CompileModuleFlow.compile(CompileM

    oduleFlow.java:58)

      at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDri

    ver.java:69)

      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD

    river.java:37)

      at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36

    )

      at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)

      at weblogic.application.compiler.EARCompiler.compile(EARCompiler.java:49

    )

      at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCo

    mpilerFlow.java:118)

      at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompile

    rFlow.java:43)

      at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDri

    ver.java:69)

      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD

    river.java:37)

      at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36

    )

      at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)

      at weblogic.application.compiler.Appc.runBody(Appc.java:181)

      at weblogic.utils.compiler.Tool.run(Tool.java:158)

      at weblogic.utils.compiler.Tool.run(Tool.java:115)

      at weblogic.application.compiler.Appc.main(Appc.java:192)

      at weblogic.appc.main(appc.java:14)

    I was also getting errors when compiling the two jsp files in the Resources subdirectory on the following line:

      String pathToWebAppRoot = getServletContext().getRealPath("/");

    I was able to get by those errors by changing the line to:

      String pathToWebAppRoot = session.getServletContext().getRealPath("/");

     

    I just don't know how to get around the error compiling FCExporter.jsp.  Any help would be appreciated.

    Thanks,

    Charles