Eclipse -- jDeveloper ((why wont jsp compile))??

Error(6,20): Attribute 'xmlns:xalan' used but not declared.
Above error is given.... the xalan.jar in my class path..., but it still doesn't work..
I have a project that compiles great in Eclipse v3.0 but when I import the war into jDev i get several errors when compiling JSP's that use struts tag libraries.
(I thought migrating war's would be easier than this)
Pls help!!
Don Lykins

The xalan namespace attribute is used in a Stylesheet.
xmlns:xalan="http://xml.apache.org/xalan"Are you using taglibs?
If the <taglib> element in a tld has the xmlns:xalan attribute, remove the xmlns:xalan attribute.

Similar Messages

HELP!: JSP compile options ignored

Can anyone tell me why my JSP compile settings in weblogic.properties
          get ignored?
          I've got the following settings in the weblogic.properties:
          ===============================================
          <SNIP>
          weblogic.httpd.register.*.jsp=\
          weblogic.servlet.JSPServlet
          weblogic.httpd.initArgs.*.jsp=\
          keepgenerated=true,\
          pageCheckSeconds=1,\
          compileCommand=/usr/java1.2/bin/javac,\
          workingDir=/export/home/weblogic/webapps/fooapp/WEB-INF,\
          verbose=false
          weblogic.httpd.defaultWebApp=/export/home/weblogic/webapps/fooapp
          <SNIP>
          ===============================================
          When I run weblogic, and request a JSP I see the following on the console:
          ===============================================
          <SNIP>
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp: init
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          param verbose initialized to: true
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          param packagePrefix initialized to: jsp_servlet
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          param compileCommand initialized to: javac
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          param srcCompiler initialized to weblogic.jspc
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          param superclass initialized to null
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          param workingDir initialized to:
          /export/home/weblogic/webapps/fooapp/_tmp_war
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          param pageCheckSeconds initialized to: 1
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          initialization complete
          Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          pageCheckSeconds over-ruled in JSPServlet to : 1
          <SNIP>
          ===============================================
          Notice that none of my settings made it in!
          Any help appreciated.
          James


James
          I'm not sure why the properties don't get set from your weblogic.properties
          file definitions, but try adding <context-param> definitions for the
          weblogic properties in question to your web.xml file. Below is a code
          snippet of an example of some properties that we added to our web.xml file.
          The <context-param> definitions should be added in front of your <servlet>
          definitions. See the BEA online documentation for Developing a Web
          Application at
          http://www.weblogic.com/docs51/classdocs/webappguide.html#createdd for a
          description of the context parameter property names..
          <context-param>
          <param-name>weblogic.jsp.compileCommand</param-name>
          <param-value>/jdk1.2.2/bin/javac.exe</param-value>
          </context-param>
          <context-param>
          <param-name>weblogic.jsp.precompile</param-name>
          <param-value>false</param-value>
          </context-param>
          
          <context-param>
          <param-name>weblogic.jsp.compileCommand</param-name>
          <param-value>javac</param-value>
          </context-param>
          
          <context-param>
          <param-name>weblogic.jsp.verbose</param-name>
          <param-value>true</param-value>
          </context-param>
          
          <context-param>
          <param-name>weblogic.jsp.packagePrefix</param-name>
          <param-value>jsp_servlet</param-value>
          </context-param>
          
          <context-param>
          <param-name>weblogic.jsp.keepgenerated</param-name>
          <param-value>true</param-value>
          </context-param>
          
          <context-param>
          <param-name>weblogic.jsp.pageCheckSeconds</param-name>
          <param-value>1</param-value>
          </context-param>
          John J. Feigal Voice (651)766-8787 (main)
          Sr. Technical Consultant (651)766-7249 (direct)
          Ensodex, Inc. Fax (651)766-8792
          4105 N. Lexington Ave., Suite 150 email [email protected]
          Arden Hills, MN 55126 WebSite http://www.ensodex.com
          "James House" <[email protected]> wrote in message
          news:[email protected]...
          > Can anyone tell me why my JSP compile settings in weblogic.properties
          > get ignored?
          > I've got the following settings in the weblogic.properties:
          >
          > ===============================================
          > <SNIP>
          > weblogic.httpd.register.*.jsp=\
          > weblogic.servlet.JSPServlet
          > weblogic.httpd.initArgs.*.jsp=\
          > keepgenerated=true,\
          > pageCheckSeconds=1,\
          > compileCommand=/usr/java1.2/bin/javac,\
          > workingDir=/export/home/weblogic/webapps/fooapp/WEB-INF,\
          > verbose=false
          > weblogic.httpd.defaultWebApp=/export/home/weblogic/webapps/fooapp
          > <SNIP>
          > ===============================================
          >
          > When I run weblogic, and request a JSP I see the following on the console:
          >
          > ===============================================
          > <SNIP>
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          init
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > param verbose initialized to: true
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > param packagePrefix initialized to: jsp_servlet
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > param compileCommand initialized to: javac
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > param srcCompiler initialized to weblogic.jspc
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > param superclass initialized to null
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > param workingDir initialized to:
          > /export/home/weblogic/webapps/fooapp/_tmp_war
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > param pageCheckSeconds initialized to: 1
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > initialization complete
          > Wed Nov 15 12:29:55 MST 2000:<I> <WebAppServletContext-General> *.jsp:
          > ######
          > ########
          > ############
          > ##############
          > pageCheckSeconds over-ruled in JSPServlet to : 1
          > ##############
          > ############
          > ########
          > ######
          > <SNIP>
          > ===============================================
          >
          > Notice that none of my settings made it in!
          > Any help appreciated.
          >
          > James
          >

Eclipse question: why no compile?

hi,
i have my Eclipse workspace in:
c:\\.....\\java, in this java folder I have a project called FORS, with 2 folders in the
project, one called Site, the other called JFORLIBRARY. In the Site folder, when I
save the classes (in Eclipse) Eclipse automatically compiles them from
scratch.
However, in the FORS directory and in the Site directory when I save (in Eclipse)
i get no compile. Is there some setting I have to change to get it to compile any
path in this folder? Does anyone know how i can get all these classes to
compile when i save them in eclipse? thanks

Doesn't it compile or don't you just notice? If you
have incremental compiling turned on, you won't
notice anything on saving, because the class files
already exist.Aer you asking me or the OP? In my case, I know it wasn't compiling because I would change the code and the program would be unaffected. I deleted the binaries and they were never recreated by Eclipse. I have other projects that work fine so it's not that I don't understand how it works, it's that this one project is all jacked up.
The biggest beef I have with Eclipse is that when IBM wrote it, they used the asinine Microsoft-esque approach of depending on a clean application exit. If the program (or your OS) crashes, it can completely screw up your workspace. I don't know what they do at close but it would be better if they made incremental changes instead of waiting for the application to close. For the life of me, I can't understand why they haven't changed this after IBM open-sourced it.

Why do I get the JSP compilation error?

Why do I get the JSP compilation error?
          Envionment:
          AIX,WLS 5.1 sp10,.........
          Thu Jun 07 11:54:41 CDT 2001:<I> <ServletContext-dcms> Generated java
          file: /usr/local/weblogic/test-weblogic/weblogic/myserver/dcms
          web/app/tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java
          Thu Jun 07 11:54:42 CDT 2001:<E> <ServletContext-dcms> Compilation of
          /usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/a
          pp/_tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java
          failed: Exception in thread "main" java.lang.NoClassDefFoun
          dError: sun/tools/javac/Main
          java.io.IOException: Compiler failed
          executable.exec([Ljava.lang.String;[javac, -classpath,
          /usr/java_dev2/jre/sh/../lib/rt.jar:/usr
          /java_dev2/jre/sh/../lib/i18n.jar:/usr/java_dev2/jre/sh/../classes:./classes/boot:./eval/cloudscape/lib/cloudscape.jar:./anderson_co
          mmon/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db2java.zip::./lib/weblogic510sp8boot.jar:./license:./classes:./lib/weblogicau
          x.jar:./myserver/serverclasses:./anderson_common/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db2java.zip::./classes/dcms/com.ib
          m.mq.iiop.jar:./classes/dcms/com.ibm.mq.jar:./classes/dcms/com.ibm.mqbind.jar:./classes/dcms/com.ibm.mqjms.jar:./classes/dcms/com_au
          th.jar:./classes/dcms/com_auth_server.jar:./classes/dcms/com_io.jar:./classes/dcms/com_jms.jar:./classes/dcms/com_jndi.jar:./classes
          /dcms/com_system.jar:./classes/dcms/com_system_server.jar:./classes/dcms/com_util.jar:./classes/dcms/dcms_common.jar:./classes/dcms/
          dcms_common_server.jar:./classes/dcms/dcms_dl_render_server.jar:./classes/dcms/dcms_finalresting_server.jar:./classes/dcms/dcms_fulf
          illment.jar:./classes/dcms/dcms_fulfillment_server.jar:./classes/dcms/dcms_fulfillment_walmart_server.jar:./classes/dcms/dcms_lookup
          _server.jar:./classes/dcms/dcms_media_server.jar:./classes/dcms/dcms_order.jar:./classes/dcms/dcms_order_server.jar:./classes/dcms/d
          cms_order_session.jar:./classes/dcms/dcms_product.jar:./classes/dcms/dcms_product_server.jar:./classes/dcms/dcms_render_client.jar:.
          /classes/dcms/dcms_render_server.jar:./classes/dcms/dcms_talent_server.jar:./classes/dcms/dcms_talent.jar:./classes/dcms/dcms_walmar
          t.jar:./classes/dcms/dcms_walmart_server.jar:./classes/dcms/dcms_jms.jar:./classes/dcms/xreport_pro.jar:./classes/dcms/xtools.jar:./
          classes/dcms/jms.jar:./classes/dcms/dcms_sql.jar:./classes/dcms/dcms_product_sql.jar::/usr/local/weblogic/test-weblogic/weblogic/mys
          erver/tmp_deployments/ejbjar-4971.jar:/usr/local/weblogic/test-weblogic/weblogic/lib/persistence/WebLogic_RDBMS.jar:/usr/local/weblo
          gic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4970.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployme
          nts/ejbjar-4969.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4968.jar:/usr/local/weblogic/test-web
          logic/weblogic/myserver/tmp_deployments/ejbjar-4967.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4
          966.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4965.jar:/usr/local/weblogic/test-weblogic/weblog
          ic/myserver/tmp_deployments/ejbjar-4964.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4963.jar:/usr
          /local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4962.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/
          tmp_deployments/ejbjar-4961.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4960.jar:/usr/local/weblo
          gic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4959.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployme
          nts/ejbjar-4958.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4957.jar:/usr/local/weblogic/test-web
          logic/weblogic/myserver/tmp_deployments/ejbjar-4956.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4
          955.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4954.jar:/usr/local/weblogic/test-weblogic/weblog
          ic/myserver/tmp_deployments/ejbjar-4953.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4952.jar:/usr
          /local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4951.jar:/usr/local/weblogic/test-weblogic/weblogic/./myserve
          r/dcms_web/app/WEB-INF/classes:/usr/local/test-weblogic/weblogic/myserver/dcms_web/app/WEB-INF/classes:/usr/local/weblogic/test-webl
          ogic/weblogic/./myserver/dcms_web/app/_tmp_war:/usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/app/_tmp_war,
          -d, /usr/l
          ocal/weblogic/test-weblogic/weblogic/myserver/dcms_web/app/_tmp_war,
          /usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/ap
          p/_tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java])
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:396)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:202)
          at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:284)
          at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:174)
          at
          weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
          at
          weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java(Compiled
          Code))
          at com.web.CommonWebUtils.forward(CommonWebUtils.java(Compiled
          Code))
          at com.web.PageNavServlet.service(PageNavServlet.java:76)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          ----------------------Caught exception while forwarding to page
          /report/walmart_prod_proof_report.jsp------------------------
          ----------------------Exception java.io.IOException: Compiler failed
          executable.exec([Ljava.lang.String;[javac, -classpath, /usr/jav
          a_dev2/jre/sh/../lib/rt.jar:/usr/java_dev2/jre/sh/../lib/i18n.jar:/usr/java_dev2/jre/sh/../classes:./classes/boot:./eval/cloudscape/
          lib/cloudscape.jar:./anderson_common/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db2java.zip::./lib/weblogic510sp8boot.jar:./li
          cense:./classes:./lib/weblogicaux.jar:./myserver/serverclasses:./anderson_common/3rd_party_jars/jt400.jar:/usr/lpp/db2_07_01/java/db
          2java.zip::./classes/dcms/com.ibm.mq.iiop.jar:./classes/dcms/com.ibm.mq.jar:./classes/dcms/com.ibm.mqbind.jar:./classes/dcms/com.ibm
          .mqjms.jar:./classes/dcms/com_auth.jar:./classes/dcms/com_auth_server.jar:./classes/dcms/com_io.jar:./classes/dcms/com_jms.jar:./cla
          sses/dcms/com_jndi.jar:./classes/dcms/com_system.jar:./classes/dcms/com_system_server.jar:./classes/dcms/com_util.jar:./classes/dcms
          /dcms_common.jar:./classes/dcms/dcms_common_server.jar:./classes/dcms/dcms_dl_render_server.jar:./classes/dcms/dcms_finalresting_ser
          ver.jar:./classes/dcms/dcms_fulfillment.jar:./classes/dcms/dcms_fulfillment_server.jar:./classes/dcms/dcms_fulfillment_walmart_serve
          r.jar:./classes/dcms/dcms_lookup_server.jar:./classes/dcms/dcms_med
          rder_server.jar:./classes/dcms/dcms_order_session.jar:./classes/dcm
          es/dcms/dcms_render_client.jar:./classes/dcms/dcms_render_server.jar:./classes/dcms/dcms_talent_server.jar:./classes/dcms/dcms_talen
          t.jar:./classes/dcms/dcms_walmart.jar:./classes/dcms/dcms_walmart_server.jar:./classes/dcms/dcms_jms.jar:./classes/dcms/xreport_pro.
          jar:./classes/dcms/xtools.jar:./classes/dcms/jms.jar:./classes/dcms/dcms_sql.jar:./classes/dcms/dcms_product_sql.jar::/usr/local/web
          logic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4971.jar:/usr/local/weblogic/test-weblogic/weblogic/lib/persistence/Web
          Logic_RDBMS.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4970.jar:/usr/local/weblogic/test-weblogi
          c/weblogic/myserver/tmp_deployments/ejbjar-4969.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4968.
          jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4967.jar:/usr/local/weblogic/test-weblogic/weblogic/m
          yserver/tmp_deployments/ejbjar-4966.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4965.jar:/usr/loc
          al/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4964.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_
          deployments/ejbjar-4963.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4962.jar:/usr/local/weblogic/
          test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4961.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/
          ejbjar-4960.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4959.jar:/usr/local/weblogic/test-weblogi
          c/weblogic/myserver/tmp_deployments/ejbjar-4958.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4957.
          jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4956.jar:/usr/local/weblogic/test-weblogic/weblogic/m
          yserver/tmp_deployments/ejbjar-4955.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4954.jar:/usr/loc
          al/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4953.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_
          deployments/ejbjar-4952.jar:/usr/local/weblogic/test-weblogic/weblogic/myserver/tmp_deployments/ejbjar-4951.jar:/usr/local/weblogic/
          test-weblogic/weblogic/./myserver/dcms_web/app/WEB-INF/classes:/usr/local/test-weblogic/weblogic/myserver/dcms_web/app/WEB-INF/class
          es:/usr/local/weblogic/test-weblogic/weblogic/./myserver/dcms_web/app/_tmp_war:/usr/local/weblogic/test-weblogic/weblogic/myserver/d
          cms_web/app/_tmp_war, -d,
          /usr/local/weblogic/test-weblogic/weblogic/myserver/dcms_web/app/_tmp_war,
          /usr/local/weblogic/test-weblog
          ic/weblogic/myserver/dcms_web/app/_tmp_war/jsp_servlet/_report/_walmart_95_prod_95_proof_95_report.java])------------------------


Hi, im getting the same thing,
Been tryin to download it for days but keeps saying "Invalid signature"
I even went into ADD REMOVE PROGRAMS hit Apple software update and change and then repair but this did not work.
Help much appreciated. Thanks

JSP compilation error, IOException, can not output (Urgent)

          Hi,
          I met the error that Weblogic can compile the jsp to a temporary java file but can
          not compile the temporary java file to class file, it said java.io.IOException, anybody
          can tell why?
          Thanks a millon!


          Your system does not have enough swap space to run the JSP compiler.
          Add swap space.
          Mike
          "dai shui" <[email protected]> wrote:
          >
          >Hi,
          >I met the error that Weblogic can compile the jsp to a
          >temporary java file but can
          >not compile the temporary java file to class file, it
          >said java.io.IOException, anybody
          >can tell why?
          >
          >Thanks a millon!

Javelin JSP compilation error

Hello Everyone,
I've a some JSP's that work some times and fail sometime with
<head>
<title>Javelin JSP compilation error</title>
</head>
<body>
<b>Compilation of JSP File '/jsp/temp/Index.jsp' <font color=#FF0000>failed</font>:</b><HR>
<pre>
I tried restarting the server, removing .wlnotdelete and couple of other things.
Why the JSP is compiled everytime(even if the server is not restarted) and Why a good looking no error JSP failis loading everytime.
Can anyone please help.
~ALAPATI

I'm using bea weblogic 8.1 SP5.
Java - jrockit81sp5_142_08
<head>
<title>Javelin JSP compilation error</title>
</head>
<body>
<b>Compilation of JSP File '/jsp/output/Index.jsp' <font color=#FF0000>failed</font>:</b><HR>
<pre>
Errors found in <PATH TO THE FILE>/Index.jsp:
Error at line 397 column 55:
Description: Type <MyClass> contains no field with this name.
Error at line 399 column 13:
Description: Type <Another Class> contains no methods with this name.
Found 2 error(s) and 0 warning(s).
</pre>
</body></html>
>
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /jsp/output/Index.jsp<html>
<head>
<title>Javelin JSP compilation error</title>
</head>
<body>
<b>Compilation of JSP File '/jsp/output/Index.jsp' <font color=#FF0000>failed</font>:</b><HR>
<pre>
Errors found in <PATH TO FILE>/Index.jsp:
Error at line 397 column 55:
Description: Type <MyClass> contains no field with this name.
Error at line 399 column 13:
Description: Type <Another Class> contains no methods with this name.
Found 2 error(s) and 0 warning(s).
</pre>
</body></html>
at weblogic.servlet.jsp.WlwJspStub.compilePage(WlwJspStub.java:208)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:246)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:196)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:598)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:406)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:526)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:265)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
2 errors javelin complaining is because of this.
1) I'm trying to access MyClass.SHOW_ME_TEXT
2) I'm trying to create an object of AnotherClass by new AnotherClass();
Please let me know if you want more details.

JSP compile warnings

Folks !
I have been getting this nuisance warning for ages and I though it was time to get rid of them. Compiling any JSP in JDeveloper I get:
Warning: package name _jsp.xxxx does not match source file name xxxx
What is it ?
Also, anyway to suppress Java compiler warnings so I can look at errors only ?
thanks a lot,
-Sanjay

I have the same problem (many warnings....), but it hasn't cause any problem while running.
I thing this is becasuse I use uppercase letters inside names of directories.
Example:
- my page: public_html/BP/Aplikace.jsp
- compiled to .java: classes\.jsps\_BP\_Aplikace.java
- third line of Aplikace.java: package bp;
So there is the problem: "_BP" (name of directory) versus "_bp" (name of package)!!!
I thing this is a bug.
If I am right, I have question for JDevTeam - will it be fixed?

Why wont Turbo Tax 2012 run on my mac?

Why wont Turbo Tax 2012 run on my Intel Mac running OS10.6.8?
My Mac:
   Intel Core Duo
   OS 10.6.8
   2GHz processor
Box and online specs indicate it should work but it does not...
Can Anyone help...

Hi eston,
well, the bad news for you is that the specs do indicate that it will not run on your computer.
Why, you ask.
If you look at the TurboTax 2012 specs for Mac, it states that for Mac OS X 10.6.8, one needs to run 64-bit.
from Intuit site, TurboTax Deluxe 2012 computer requirements (http://turbotax.intuit.com/personal-taxes/cd-download/deluxe.jsp):
Processor:Intel-based Processor
Operating System:
Mac OS X v10.6.8 or later
Mac OS X v10.7.5 or later
Mac OS X v10.8.0 or later
Note: 64-bit required for Mac OS 10.6.8
the "64-bit required" link takes one to the Apple kb page....
My Mac:
   Intel Core Duo
   OS 10.6.8
   2GHz processor
your spec list above states that you have an Intel Core Duo. The Apple kb article (http://support.apple.com/kb/HT3696) shows a list of which processors are 64-bit and which are 32-bit. Unfortunately for you, the Intel Core Duo is 32-bit. This is why TurboTax 2012 will not run on this computer.
The next processor, Intel Core 2 Duo, is 64-bit, as are the later Xeon and "i" series.
cheers, and good luck,
Roy

HELP.....!!!!! Chinese jsp compilation problem.....

Hi,
Could someone please help on the above mentioned?
I'm using JDeveloper 3.2.3 for my program development under Chinese windows platform. I have created a simple JSP page, which contains few static Chinese words and I have included the line
<%@ page contentType="text/html;charset=UTF-8"%>
at the top of the page. When I tried to compile it using encoding "UTF8" (under compiler option), the compiler gave me this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Error: (0) sun.io.MalformedInputException.
Btw, when I have removed the line <%@ page contentType="text/html;charset=UTF-8"%> from the page and compile, I've got this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Warning: (0) ISO-8859-1 character set may not match project compiler setting.
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java
Error: (0) malformed input character in C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java.
I do appreciate your help on this. Thank you.

Here's some info one of the JSP Developers sent me:
1. HELP.....!!!!! Chinese jsp compilation problem.....
The customer is trying to parse a document generated by
Windows's notepad. When saved in UTF-8, the byte
order mark is saved too. We have a know bug that
JSP parser doesn't recognize Byte Order Mark. The
bug is : 1915285.
2. CHINESE CHARACTER ON JSP
. SQLPLUS depends on NLS_LANG setting. If you
check the windows registry, the default of NLS_LANG
depends on the OS. The user environment is Traditional
Chinese, so does NLS_LANG. If we set NLS_LANG
to .UTF8, SQLPLUS dumps the data in UTF8, however,
the command prompt will have problem displaying them.
. For JSP, as mentioned in a previous mail:
<%@ page contentType="text/html;charset=UTF-8" %> for all languages
<%@ page contentType="text/html;charset=GB2312" %> for simplified Chinese
<%@ page contentType="text/html;charset=Big5" %> for traditional Chinese
. When you enter Chinese characters on a browser,
the data is automatically converted to page encoding
(UTF-8 in your case) before sent back to the server.
But your receiving servlet/JSP needs to have request
encoding set correctly.
    I'm not sure about the JDeveloper environment,
but here is a simple JSP you may try to verify your
OC4J environment:
a.    To set up the schema:
connect scott/tiger
create table tab01(col varchar2(100));
b. Edit the connect string in nls.jsp
c. Run the nls.jsp in oc4j instance.

<%@ page contentType="text/html; charset=UTF-8" %>
<%@ page import="oracle.jdbc.*,java.sql.*,java.io.*"%>
<HTML>
<HEAD>
<TITLE>Hello</TITLE></HEAD>
<BODY>
<%
request.setCharacterEncoding("UTF-8");
String sampledata="\u7D20";
String paramValue = request.getParameter("myparam");
String connStr = "jdbc:oracle:thin:@dlsun478:5521:j2ee01";
String user = "scott";
String passwd = "tiger";
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(connStr, user, passwd);
if (paramValue == null || paramValue.length() == 0) { %>
   <FORM METHOD="GET">
   Please input your name: <INPUT TYPE="TEXT" NAME="myparam"
value="<%=sampledata%>" size=20>
<BR>
   <INPUT TYPE="SUBMIT" value="Insert Data">
   </FORM>
<%
selectData(conn, out);
else
%>
   <H1> Insert Data: <%= paramValue %> </H1>
   <br/>
<%
insertData(conn, paramValue);
%>
<a href="nls.jsp">back</a>
<%
%>
</BODY>
</HTML>
<%!
public void insertData(Connection aConn, String myval)
    try {
      PreparedStatement stmt = aConn.prepareStatement("insert into tab01
values(?)");
      stmt.setString(1, myval);
      stmt.executeUpdate();
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
public void selectData (Connection aConn, JspWriter out)
    try {
      Statement stmt = aConn.createStatement( );
      ResultSet r = stmt.executeQuery("SELECT col FROM tab01");
      out.println("<H1>List of Data:</H1>");
      while (r.next()) {
        out.println(r.getString(1)+"<br/>");
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
    catch (IOException e) {
      e.printStackTrace();
%>

JSP Compile

Hello,
          I have a problem compiling jsp files with weblogic server 6.1 sp3. The
          Server runs on AIX 5.1 using java 1.3.1 (ca131-20030329).
          Sometimes the jsp compiling stops and the process (javac) hangs until
          it is killed. You can see, that the spawned javac process has never
          taken any cpu time.
          Can someone explain what the problem is?


i just found a bug on weblogic 9.1/9.2...
          cool compiler...I wonder why weblogic didn't do any QA on this......
          if you have a bean MyBean with
          public Set<org.MyObject> getSomething();
          public void setSomething(java.util.Set<org.MyObject> );
          and u do a useBean/setProperty * on this bean...mr javelin
          generates a java file with:
          javelin.jsp.utils.JspRuntimeUtils.convertType(__value, java.util.Set<org.MyObject> .class))
          that is why it doesn't compile...oh the joy......

11g turn off JSP Compilation

How do I turn off JSP Compilation in jdeveloper 11g ?
I have set the params in weblogic.xml but jdeveloper seems to ignore it.
<jsp-descriptor>
<precompile>false</precompile>
<precompile-continue>true</precompile-continue>
</jsp-descriptor>
Also there was an option in 10g under Run Configurations to say "Run Project Despite Compiler Errors" how do I set this in 11g?
thanks in advance
Arun

Can't seem to find the JSP option.
Project Properties --> Compiler has 3 options "Options" "SQLJ" and "XML"
I checked the technologies and Scope, Servlets and JSP is slelected and i can see the runtime libraries in the libraries section.
thanks
Arun

JSP Compiler and ClassCastException

Have been using JDK1.2.2 from sun since day one and I've been seeing
          ClassCastException since day 1 too.
          Don't think it had anything to do with the compiler.
          "Jun Ying" <[email protected]> wrote in message
          news:[email protected]...
          > I noticed something that might be causing the ClassCastException and has
          not
          > been mentioned: the compiler that is used for jspc. I remember seeing a
          few
          > people mentioning extra classes in the workDir (ie, the bean class that is
          > being used). This is caused by using a smart compiler such as jikes or
          sj.
          > While those compilers will get you more speed for newly modified jsp's,
          they
          > resolve dependencies and recompile all the referenced classes. The result
          > is that the bean class gets recompiled and put into workDir. So no matter
          > where you put the workDir, you end up getting a new copy of the bean class
          > file, which is reloaded by the classloader that loads the newly compiled
          > JSP. That copy of the class file is considered "different" from the one
          > from the normal system classpath or the weblogic.class.path. Thus the
          > ClassCastException. So if you see java classes other than the jsp's in
          the
          > workDir, make sure you are using javac from the sun jdk. So to answer
          > Anish's question, WebLogic is not sticking a copy of the bean class.
          > Rather, it's the java compiler that you are using.
          >
          > Jun Ying
          > Meritsoft, Inc
          >
          >
          > "Michael Boudreau" <[email protected]> wrote in message
          > news:[email protected]...
          > > Hello,
          > >
          > > Well we ran into the same problem here at my company, and we have been
          > > pulling our hair out. I was reading through the jsp 1.1 spec, and
          > > thought I might try using the <jsp:useBean ...> tag instead of the <%@
          > > page import ...> tag. After careful inspection of the resulting .java
          > > file, I found that the <jsp:useBean ...> tag does not put insert any
          > > import statements, but simply declares the bean with the fully
          > > qualified package name. I am sure that this is not new news to anyone;
          > > however, the class cast exception went away (knock on wood, cross
          > > fingers, whatever).
          > >
          > > Basically, my statement looked like this:
          > > <jsp:useBean id="beanname" type="com.company.Class" scope="session" />
          > >
          > > My question is: is there something that I am missing or have not
          > > thought of? Because so far, this "seems" to be working, but I have
          > > been reading posts that say this does not work.
          > >
          > > Oh, one last quick note to BEA. While I was looking at the
          > > generated .java file from the jsp file, I found that weblogic's jspc is
          > > still generating getValue and setValue methods for HttpSession....
          > > which has been deprecated as of the servlet 2.2 spec.
          > >
          > > Michael
          > >
          > >
          > >
          > >
          > > Anish Parvataneni wrote:
          > >
          > > > Hi,
          > > >
          > > > I have a JSP which uses two different classes. Whenever, I change the
          > > > JSP and save it to recompile, there is a ClassCastException. ( I store
          > > > them in the session and load them) . Thats common ! The solution to
          this
          > > > as per documentation is to get rid of the classes in the workingDir of
          > > > JSP. However, I can find ONLY ONE of the classes in the workingDir. I
          > > > delete that class and the JSP works. I change the JSP , problem
          recurrs.
          > > >
          > > > 1. Why does weblogic stick a copy of the class in the workingDir,
          > > > everytime the JSP compiles, although it is available in the weblogic
          > > > classpath ?
          > > > 2. Why is it happening to only one of the classes I use in the JSP ?
          > > > 3. How can I make sure that this class is not available in the
          > > > workingDir, other than deleting it EVERYTIME.
          > > >
          > > > Thanks
          > > > Anish
          > >
          >
          >

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]

Why wont my iphone 4s let me download ios 6?

why wont my iphone 4s allow me to download ios 6? it keeps coming up with an error message.

What error did it say their way. See this support document for troubleshooting iMessage and Facetime activation. http://support.apple.com/kb/TS4268

Why wont apple let me download apps without a credit card?

Why wont apple let me get an apple ID without a "no credit card" suggestion in the payment method?
I dont buy my apps and I dont understand why my sister (and other people) were able to make an apple ID without putting a credit card.
Though I can enter my apple ID account when it comes to the game center, when I try to download an app that problem always appears. So now I'm using my sister's ID, but I really want to have my own.

Follow it through to the payment methods and choose None if it is available.

Eclipse -- jDeveloper ((why wont jsp compile))??

Similar Messages

Maybe you are looking for