Compilation error in jsp script with weblogic 9.1 server

Hi All,
          i am using weblogic 9.1 compiler to compile my jsp code.
          it gives me compilation error.
          The root cause of the error is %% which comes in the code.
          for e.g take this code:-
          <%
          System.out.println("%%abc");
          %>
          this code will give error while error.
          here it is identifing %% as termination tag!
          same code works in tomcat & weblogic 8.1
          can anyone give any information in this regard.
          Reagrds
          Rahul

I am also getting the same error. If you have solved this issue please share the solution.
Thanks,
Dikshit

Similar Messages

Pre_compiling jsp's with weblogic.jspc error

Hi all,
Im using weblogic 11g weblogic.jspc to try to pre-compile JSP's that were created with struts 1.2.x under OC4J 9.0.x.
The jsp's do compile under OC4J's jsp compiler.
Im getting many errors that seem to be related to the version difference between struts1.2.x used with OC4J and the struts bundled with weblogic.
I'm trying to "force" the weblogic.jspc to use the older version of struts but have not been successful.
This is on Windows XP SP4 box.
So far I've tried:
adding the -classpath option
adding the -d option to specify a directory
adding the -backwardcompatible option
adding the -librarydir option
here's my command line format:
java weblogic.jspc -classpath .;c:\...\struts.jar;WEB-INF\struts-bean.tld;c:\...\struts-validator.jar;c:\...\struts-nested.jar;c:\...\strutstest2.0.0.jar...
-backwardcompatible -d WEB-INF addNote.jsp
heres a sample of output:
jspc failed with errors :weblogic.servlet.jp.CompilationException:
addNote.jsp:11:57 The method setContent(String) in the type PutTag is not applicable for the arguments (Object)
<template:put name="title" direct="true" content="<%=request.getAttribute(Constants.TITLE)%>"/>
addNote.jsp:15:31: Th method setAction(String) in the type FormTag is not applicable for the arguments (Object)
<html:form action="<%=request.getAttribute(Constants.ACTION)%>" focus="notBean.subject">
I couldn't add the jsp snippets becuase this input form is complaining about the tags.
Any help would be greatly appreciated.

Hi all,
Im using weblogic 11g weblogic.jspc to try to pre-compile JSP's that were created with struts 1.2.x under OC4J 9.0.x.
The jsp's do compile under OC4J's jsp compiler.
Im getting many errors that seem to be related to the version difference between struts1.2.x used with OC4J and the struts bundled with weblogic.
I'm trying to "force" the weblogic.jspc to use the older version of struts but have not been successful.
This is on Windows XP SP4 box.
So far I've tried:
adding the -classpath option
adding the -d option to specify a directory
adding the -backwardcompatible option
adding the -librarydir option
here's my command line format:
java weblogic.jspc -classpath .;c:\...\struts.jar;WEB-INF\struts-bean.tld;c:\...\struts-validator.jar;c:\...\struts-nested.jar;c:\...\strutstest2.0.0.jar...
-backwardcompatible -d WEB-INF addNote.jsp
heres a sample of output:
jspc failed with errors :weblogic.servlet.jp.CompilationException:
addNote.jsp:11:57 The method setContent(String) in the type PutTag is not applicable for the arguments (Object)
<template:put name="title" direct="true" content="<%=request.getAttribute(Constants.TITLE)%>"/>
addNote.jsp:15:31: Th method setAction(String) in the type FormTag is not applicable for the arguments (Object)
<html:form action="<%=request.getAttribute(Constants.ACTION)%>" focus="notBean.subject">
I couldn't add the jsp snippets becuase this input form is complaining about the tags.
Any help would be greatly appreciated.

JSP issue with WebLogic 9.1 but not with 8.1

I am getting the following errors when i am trying to build an existing web application. I was able to build it successfully using weblogic 8.1.
          Below are the versions i am using
          Weblogic 9.1
          Ant1.6.2
          JDK 1.5.0_04
          ===================================================
          Results.jsp:596:63: The qualifier of this name is a package, which cannot contai
          n methods.
          onclick="PopupURLMenu('<%=ResultsUtil.getMyDoc(oDocs,cou
          nt).getUrl()%>',
          ^------^
          Results.jsp:598:28: No match was found for method getDisplayName() in type <erro
          r>.
          <%=ResultsUtil.getMyDoc(oDocs,count).getDisplayName()%>
          ^------------------------------------------------^
          Results.jsp:598:40: The qualifier of this name is a package, which cannot contai
          n methods.
          <%=ResultsUtil.getMyDoc(oDocs,count).getDisplayName()%>
          ^------^
          Results.jsp:606:55: No match was found for method getUrl() in type <error>.
          onclick="PopupURLMenu('<%=ResultsUtil.getMyDoc(oDocs
          ,count+1).getUrl()%>',
          ^-------------------------
          -----------------^
          Results.jsp:606:67: The qualifier of this name is a package, which cannot contai
          n methods.
          onclick="PopupURLMenu('<%=ResultsUtil.getMyDoc(oDocs
          ,count+1).getUrl()%>',
          ^------^
          Results.jsp:608:32: No match was found for method getDisplayName() in type <erro
          r>.
          <%=ResultsUtil.getMyDoc(oDocs,count+1).getDisplayNam
          e()%>
          ^------------------------------------------------
          --^
          Results.jsp:608:44: The qualifier of this name is a package, which cannot contai
          n methods.
          <%=ResultsUtil.getMyDoc(oDocs,count+1).getDisplayNam
          e()%>
          ^------^
          Results.jsp:638:21: No match was found for method getDisplayName() in type <erro
          r>.
          if (ResultsUtil.getMyDoc(oDocs,q).getDisplayName().equals("") )
          ^--------------------------------------------^
          Results.jsp:638:21: No match was found for method equals(java.lang.String) in ty
          pe <error>.
          if (ResultsUtil.getMyDoc(oDocs,q).getDisplayName().equals("") )
          ^-------------------------------------------------------^
          Results.jsp:638:33: The qualifier of this name is a package, which cannot contai
          n methods.
          if (ResultsUtil.getMyDoc(oDocs,q).getDisplayName().equals("") )
          ^------^
          at weblogic.servlet.jsp.jspc20.runBodyInternal(jspc20.java:424)
          at weblogic.servlet.jsp.jspc20.runJspc(jspc20.java:195)
          at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:239)
          at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:348
          at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:74
          at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCo
          mpilerFlow.java:113)
          at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompile
          rFlow.java:43)
          at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDri
          ver.java:55)
          at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
          river.java:26)
          at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:24)
          at weblogic.application.compiler.Appc.runBody(Appc.java:151)
          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:162)
          at weblogic.appc.main(appc.java:14)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
          java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
          sorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:585)
          at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:
          290)
          at weblogic.ant.taskdefs.j2ee.Appc.privateExecute(Appc.java:243)
          at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:154)
          at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
          at org.apache.tools.ant.Task.perform(Task.java:364)
          at org.apache.tools.ant.Target.execute(Target.java:341)
          at org.apache.tools.ant.Target.performTasks(Target.java:369)
          at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
          at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
          at org.apache.tools.ant.Main.runBuild(Main.java:673)
          at org.apache.tools.ant.Main.startAnt(Main.java:188)
          at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
          at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
          ====================================
          Is this a problem with the classpath ?
          Thanks in advance,
          Bye

I am also getting the same error. If you have solved this issue please share the solution.
          Thanks,
          Dikshit

How do I see javac compiler errors during JSP precompile?

          I played with all the options that "weblogic.jspc"
          supports. I couldn't get the javac compiler errors to
          show up when there is a problem with the generated
          Java file.
          Interestingly the same JSP when compiled automatically
          by the weblogic server, the javac errors show up in
          the output.
          Any tricks? or ideas?
          thanks


          In WL 5.1, earlier service packs would sometimes not show the errors. Get sp6 or later.
          mike
          "Mahesh Vellanki" <[email protected]> wrote:
          >
          >
          >I played with all the options that "weblogic.jspc"
          >supports. I couldn't get the javac compiler errors to
          >show up when there is a problem with the generated
          >Java file.
          >
          >Interestingly the same JSP when compiled automatically
          >by the weblogic server, the javac errors show up in
          >the output.
          >
          >Any tricks? or ideas?
          >
          >thanks
          >

Compiler error: Missing JSP library?

Hi All,
I am really new at this, and I know that I'm making some sort of simple mistake.
I have an existing application running on a 9i middle tier. I want to make a couple of simple changes to a .JSP. So I downloaded the EAR file, loaded it into JDeveloper (10.1.3.0.4 SU4), made my changes and tried to run it locally. I got 241 compiler errors. So I reverted to the original EAR, and I still get 241 compiler errors.
The errors are:
Error(1,5): illegal forward reference
Error(1,14): duplicate definition of class _index
Error(1,48): HttpJsp not found in class _index
Error(1,62): method getPageContext(_index, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, null, boolean, int, boolean) not found in class javax.servlet.jsp.JspFactory
The code is:
<sample>
import oracle.jsp.runtime.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
public class _index extends oracle.jsp.runtime.HttpJsp {
public final String _globalsClassName = null;
public void _jspService(HttpServletRequest request, HttpServletResponse response) throws java.io.IOException, ServletException {
response.setContentType( "text/html;charset=windows-1252");
/* set up the intrinsic variables using the pageContext goober:
** session = HttpSession
** application = ServletContext
** out = JspWriter
** page = this
** config = ServletConfig
** all session/app beans declared in globals.jsa
PageContext pageContext = JspFactory.getDefaultFactory().getPageContext( this, request, response, null, true, JspWriter.DEFAULT_BUFFER, true);
// Note: this is not emitted if the session directive == false
HttpSession session = pageContext.getSession();
if (pageContext.getAttribute(OracleJspRuntime.JSP_REQUEST_REDIRECTED, PageContext.REQUEST_SCOPE) != null) {
pageContext.setAttribute(OracleJspRuntime.JSP_PAGE_DONTNOTIFY, "true", PageContext.PAGE_SCOPE);
JspFactory.getDefaultFactory().releasePageContext(pageContext);
return;
</sample>
So, I read the forums, etc and decided that I need ojsp.jar included in my project libraries. So I went to libraries under project properties, and I already have "Jsp Runtime" as my first library and it claims to include ojsp.jar. I've tried removing and re-adding the library, adding other libraries ("J2EE","Servlet Runtime","OC4J Deployment Plugin"...), and a dozen other things, none of which have allowed my to compile.
Any ideas on what I should do?
Steven

you might need to post more code, but basically the
compiler is complaining because you do not have a
return statement at the end of your method.
if you do not have a return statement (with a matching
return type) then the compiler will complain. If you
don't understand this then post the code to your
method and we can get it fixed.
public String[] read(InputStream list) throws
Exception {
String[] stringArray;
return stringArray;
The code is the most complex I have written so far but here is some of it. (the begining and the end)
public String[] read(InputStream list) throws Exception {
if (list != null) {
String[] stringArray = null;
try {
while {
//add strings to string array
}//end of while
return stringArray;
}// end try
catch{
}//end of method

Error while deploying application with WebLogic server

Hi,
I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
"There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
Plz help me.
Thx

I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
Cheers!

Error while using TXDataSource with Weblogic 6.1 & Oracle 8.1.6

Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver. These are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I am not sure where the problem is as I have configured Connection Pool and TXDataSource as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'myXAPool' Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

Hi Sudhir,
If you do not know if upgrade or not, have a look here :
http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html
Note that at the end of June SP3 will be released...
Sergi
"Sudhir Babu" <[email protected]> wrote:
>
Hi Sergi,
Thanks a lot for the class file, I figured out what the problem was. Actually
the
database version I was working with was 8.0.6.0. The Oracle driver doesn't
work with
this but the JDriver worked. This is the output of running CheckDriver..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8 Enterprise Edition Release 8.0.6.0.0 -
Production
With the Partitioning and Objects options
PL/SQL Release 8.0.6.0.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.1.0
Then I tried on using the Oracle Driver on another instance which has the
version
8.1.7.1.0 and it worked. The JDriver and Oracle driver both work with this
database.
The output of CheckDriver for this Oracle instance is..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8i Enterprise Edition Release 8.1.7.1.0 -
Production
With the Partitioning option
JServer Release 8.1.7.1.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.0.0
By the way I am working on WLS 6.1 SP1. What is the advantage of SP2 ? Should
I upgrade
Thanks once again,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir ,
JDriver works well, you can work with it.
Just for curiosity, can you run the class I attached using the "exact"classpath
of your WL instance (with Oracle drivers in front of weblogic.jar) ? What
is the
output ?
On which platform are you running your WLSP2 ?
Thanks
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
I just checked the things you mentioned. The connection pool starts correctly
without
any errors. I also made sure SELECT previlege was granted to DBA_PENDING_TRANSACTIONS.
I do have the JAVA_XA package installed and it has EXECUTE permission
to
PUBLIC.
I actually tried using the Weblogic JDriver (weblogic.jdbc.oci.xa.XADataSource)
and
it works perfect without any issue. The only consideration is that itis
a Type 2
Driver and needs to have the Oracle Client installed. But right now Ido
have it
installed on the same machine.
Do you know any known issues with Weblogic JDriver. Do you think it'sa
good idea
to go with it ?
Thanks,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
does your connection pool start correctly ?
Check the setup of your Oracle server too:
1) grant select on DBA_PENDING_TRANSACTIONS table to PUBLIC
2) package JAVA_XA installed (with grant execute to PUBLIC)
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
Thanks for the response. I downloaded the driver for 8.1.7 from Oraclesite
and put
it in classpath in front of weblogic.jar. I still get the same problem.
Is there
another location where we can download the Oracle driver with the bug
fixed
Regards, Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
I think you are using Oracle JDBC drivers 8.1.6.
They have a bug, they do not accept a foreign XID.
Use 8.1.7 or higher to solve this problem.
Sergi
Sudhir Babu <[email protected]> wrote:
Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver.
These
are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I amnot
sure where the problem is as I have configured Connection Pool and
TXDataSource
as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured in the transaction branch start() failed on resource 'myXAPool'
Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

BPEL Compilation Error: Load of wsdl "with Message part element undefined..

Hi Friends,
I am getting following error while compiling my BPEL process:
Error: Load of wsdl "FTPWrite.wsdl with Message part element undefined in wsdl [file:/D:/MyData/_MyProjects/052_Amazon_MetadataInterface/001_SVN/002_Intl/trunc/MetadataInterfaceIntl_2013Apr15_WorkingCode/MetadataInterface_Intl/MetadataInterface_Intl.wsdl] part name = reply type = {http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types}processResponse" failed
However the reply message is already defined in the MetadataInterface_Intl.wsdlas shown below:
Code for MetadataInterface_Intl.wsdl::::
"<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions
name="MetadataInterface_Intl"
targetNamespace="http://xmlns.oracle.com/MetadataInterfaceIntl/MetadataInterface_Intl/MetadataInterface_Intl"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:inp1="http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types"
xmlns:tns="http://xmlns.oracle.com/MetadataInterfaceIntl/MetadataInterface_Intl/MetadataInterface_Intl"
>
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types" schemaLocation="xsd/Metadata_Interface.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="request" element="inp1:process"/>
</wsdl:message>
*<wsdl:message name="replyMessage">*
*<wsdl:part name="reply" element="inp1:processResponse"/>*
*</wsdl:message>*
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
<wsdl:output message="tns:replyMessage"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>"
Surprisingly, this same code was compiling file last week and now I have no clue why I am getting this error. Can someone please shade some light on this issue?
Thanks,
Sachin.

Hello
I have had the same problem in Oracle BPM and solved it using the following steps:
1- In your application navigator window, expand the project that contains the business rule.
2- In the SOA Content, double click on your wsdl file.
3- When the file opens, select the schema view from the bottom of the page.
4- In the schema view, expand all the schema nodes and check if you see any values in red. If you see one, that value has probably caused the error and you should correct it using the property inspector window.
In my case, the schema location value was set to a wrong path, so I changed it and the error resolved.
Also, some error that appear as warning in the rule editor will show as compile error later, such as input types not being used and such, so those must be resolved before compiling.
Hope that was helpful
good luck

Compile error: Eclipse confuses Type with Window.Type

Hi there,
I'm using Eclipse Luna (Version: Luna Service Release 1a (4.4.1)) and JDK 1.8.0_31.
Our projects are build with Maven. Maven build works without any problems and also our Netbeans users do not have any issues.
But Eclipse shows compile errors and it seems, that it confuses the generic Java Type with java.awt.Window.Type which was introduced with Java 1.7.
I created the following minimized example, which reproduces the compile problem.
This class creates a instance of MyDialog which uses the generic Java Type:
public class TypeTest {
public static void main(String[] args) {
String str = new String();
MyDialog<String> dialog = new MyDialog<String>();
String x = dialog.getValue(str);
And this is the implementation of the dialog of type Type:
import javax.swing.JDialog;
public class MyDialog<Type> extends JDialog {
public MyDialog() {
super();
public Type getValue(Type value) {
return value;
Eclipse persists that for getValue in MyDialog the Type is a Window.Type, which is wrong!
This is the compile error message:
The method getValue(Window.Type) in the type MyDialog<String> is not applicable for the arguments (String)
Since it works without any issues for the maven build and the netbeans users, it seems to me that this is an Eclipse issue or bug? Or can someone give me a hint, how this can be solved?
Thanks and kind regards,
Daniel

I just found that this question has never been answered, and from a cursory look I wasn't actually sure if this is a bug or not.
Turns out I already wrote a little "essay" on what seems to be the same issue, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=396378#c6
Bottom line: JLS doesn't seem to specify how to interpret / handle a conflict between an inherited member type and a same-named type parameter.
This seems to impliy that both implementations, javac and ecj - although different - are both valid wrt JLS.

How To Get Off The Dime With WebLogic 8.1 Server

I'm just getting started with WebLogic 8.1 and I'm already having an embarrassing problem. I'm running on Windoze XP.
I've been to the docs and seen that I have two choices on how to start the server:
(1) Navigate to the domain for an application and run the startWebLogic.cmd file,
(2) Start->BEA WebLogic Platform 8.1->WebLogic Workshop 8.1->Tools->WebLogic Server->Start WebLogic Server
The app I'm working on doesn't have a startWebLogic.cmd file. When I try to start it via Workshop, the "Start WebLogic Server" choice is grayed out. There are no messages in the log file to tell me why.
What am I missing? I feel like the village eejit. Can a WebLogic guru get me off the mark? Thanks - %

Hi Maris,
Quite right, thank you. Thanks to some local help I've got this app up and running.
I'm so used to the Tomcat model of putting everything in WAR and deploying simply by moving it into into the /webapps directory. I hand edit everything into my web.xml. I like that feeling of control. Wizards make me a bit nervous. I've got to get to that same level of comfort with WL.
Just one way to do that: sit down and pore through the WL docs.
%

Odd Compiler Error in JSPs

I found a really odd compiler problem today in my JSPs. When I tried to do a rebuild on my JSPs, all of them came up with the exact same error. Basicall it said that I could not have a -- within a comment. This error was reported on three lines and the editor showed three sections as having problems (using a squiggly yellow line). However, none of the pages had anything like what was mentioned on those lines.
It turned out that the real problem was that the web.xml file had the error. I had put some '--' in a comment section and when the compiler parsed the web.xml file and found the problem, it failed to tag that file as the source but rather ended up showing the JP as being the source.
Took a bit if time to figure that one out.
Bill Berks

You can file a bug at http://bugs.sun.com/services/bugreport/index.jsp

Unable to run simple empty jsp page with weblogic 10.3.6.0.

Dears,
I have a simple war with simple empty welcome jsp page, when i deploy my project on AdminServer domain, jsp displays correctly, but if i deploy it on other domain i got this exception :
java.lang.ClassCastException: org.apache.jasper.runtime.JspWriterImpl cannot be cast to weblogic.servlet.jsp.ByteWriter
     at jsp_servlet.__index._jspService(__index.java:63)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
     at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:416)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:327)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
I'm using weblogic 10.3.6, any help will be appreciated.
regards.

dunnsoftinc wrote:
During the initial pass, I decided to leave this password null in both places, which is documented within the peopletools 8.53.00 installation guide. Maybe, it's time to further test. Thank you Nicolas.To be honest I've never tried to leave it blank in previous releases, thought that was mandatory (it was not prompted in psadmin menu as it is with PT8.53).
I don't have a PTools 8.53 instance in hands right now, but after a quick test over here on PT8.51, I have the same issue as yours.
Let me also remind you that there are two separate scenarios that may be received via the sign-on page:
1.) "The application server is down" status message without the "bea.jolt.ServiceException: TPESVCERR - server error while handling request" error.
2.) "The application server is down" status message including the "bea.jolt.ServiceException: TPESVCERR - server error while handling request" error.As I said earlier, you should get more clue in the webserver logfiles.
Nicolas.

URGENT: Error while deploying ear with weblogic service control

We have build an ear within workshop and deployed to another server. When accessing the application we are getting the following error:
'com.bea.control.ServiceControlException: Could not find service ref in jndi: java:comp/env/service/hhs_wc_controls_SearchServiceControl[javax.naming.NameNotFoundException: While trying to look up comp/env/service/hhs_wc_controls_SearchServiceControl in /app/webapp/WCWeb/5120123.; remaining name 'comp/env/service/hhs_wc_controls_SearchServiceControl'] '
The service control is connecting a WSDL to consume a web service.
Does the service control create a JNDI entry or some file is not getting built into the ear?
We are using WLP 10.3
Your help is much appreciated.
Thanks,
- Shankar
Edited by: user1269940 on Nov 6, 2009 12:39 PM

Hi Shankar
When a WebService Control is created based on .wsdl file, it generates a .JAR file with all jaxb generated classes and .java files with service and port classes. This .jar file will be under web-inf/lib folder. Then I guess you are using this WebService control in your Pageflow and invoke webservice operations. So do you have like a portlet for this pageflow and testing from a portal. I have a similar scenario but I did not get any error that you are seeing. I consume SOA BPEL webservices in one of my pageflows using Service Controls.
To debug, first test if the wsdl is working by directly invoking the wsdl operations using a utility servlet by name "wls_utc" which you can invoke from any of your wls/wlp domain. Start your domain assuming localhost and port is 7001. The url for testing webservices is:
http://localhost:7001/wls_utc. This works if domain is in Dev Mode only. This page opens a jsp page, where you can type your wsdl url (http://host:port/context/a/b/xyx?wsdl). This page parses that wsdl and shows all operations and for each operation the fields for input parameters. See if this wsdl works fine.
As for deployment, there is no additional step required. Just ear your application that has .war file and that has web-inf/lib folder with actual webservice control generate .jar file. I did no tconfigure any additional JNDI lookups like that.
Thanks
Ravi Jegga

Why not perform the ${attribute} syntax in the jsp context with weblogic?

In the action an attribute has been put in request object, example request.setAttribute("userName","Xue Chen").
in the forward jsp , use the syntax ${userName}, can not get the attribute "Xue Chen" from request, but the "${userName}" be printed in the page.
The same code with Tomcat, it work well.
It maybe the syntax ${userName} in jsp is not standard for all application server, only work in Tomcat, or it need special confiugre in weblogic, this syntax can work.
Does anyone do me a favors?

Hi,
go to the context of your view,
to the attribute of your date,
and set the attribute input help mode to disabled
grtz,
Koen

Trigger Compilation Errors after Full Import with Datapump

Hello All,
We did a full import with Oracle Datapump, and encountered some errors related to triggers:
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT" created with compilation warningsWe are wondering if there is some bug with the datapump on oracle 10.2.0.2. What caused such errors and how to resolve this trigger issue?
Thanks!

Hello,
Show errors / at the end of the trigger and see if any of the dependent objects is missing resulting in error at compilation.
Also you can try manually fixing the issue
CREATE OR REPLACE TRIGGER table1_trg
   AFTER INSERT
   ON TABLE1    REFERENCING NEW AS new OLD AS old
   FOR EACH ROW
DECLARE
   tmpvar   NUMBER;
BEGIN
Trigger code
EXCEPTION
   WHEN OTHERS
   THEN
      -- Consider logging the error and then re-raise
      RAISE;
END table1_trg;
SHOW ERRORS;Regards

Compilation error in jsp script with weblogic 9.1 server

Similar Messages

Maybe you are looking for