JSP-Descriptor

I am not exactly a JSP pro. So I have a question which may sound pretty
          basic.
          I want to pass some configuration information to my jsp. I would like to
          specify the parameter names and values in web.xml or weblogic.xml. Is the
          <jsp-descriptor> the right place for such purposes ?
          Also how can I read those values from within my JSP ?
          Regards,
          Adarsh
          

          You can use init params per jsp or context params available to the entire context's
          pages.
          <servlet>
          <servlet-name>snoop</servlet-name>
          <jsp-file>/snoop.jsp</jsp-file>
          <init-param>
          <param-name>myinitparam</param-name>
          <param-value>paramvalue</param-value>
          </init-param>
          </servlet>
          this code:
          from servlet:
          getServletContext().getInitParameter("myinitparam")
          from jsp:
          application.getInitParameter("myinitparam")
          or context params
          <context-param>
          <param-name>mycontextparam</param-name>
          <param-value>paramvalue</param-value>
          </context-param>
          from servlet:
          getServletContext().getAttribute("mycontextparam")
          from jsp:
          application.getAttribute("mycontextparam")
          "Adarsh Dattani" <[email protected]> wrote:
          >I guess I mis-phrased my question. I do not want to pass not from the
          >browser. I want to define configuration settings in the deployment
          >desciptors (like connection pool names or jms queue jndi names etc.).
          > I
          >want to be able to read those values from my JSP.
          >TIA,
          >Adarsh
          >
          >"Deepak Vohra" <[email protected]> wrote in message
          >news:[email protected]...
          >> Speciify the parameters & their values with the Jsp.
          >> For example
          >>
          >http://localhost:7001/ExampleJsp.jsp?parameter1=value¶meter2=value¶m
          >eter3=value
          >>
          >> Retrieve the parameter values in the jsp.
          >>
          >> String param1=request.getParameter("parameter1");
          >> String param2=request.getParameter("parameter2");
          >> String param3=request.getParameter("parameter3");
          >>
          >>
          >> Adarsh Dattani wrote:
          >>
          >> > I am not exactly a JSP pro. So I have a question which may sound
          >pretty
          >> > basic.
          >> > I want to pass some configuration information to my jsp. I would
          >like
          >to
          >> > specify the parameter names and values in web.xml or weblogic.xml.
          > Is
          >the
          >> > <jsp-descriptor> the right place for such purposes ?
          >> > Also how can I read those values from within my JSP ?
          >> > --
          >> > Regards,
          >> > Adarsh
          >>
          >
          >
          

Similar Messages

  • Jsp-descriptor jsp-param jspCheckSeconds weblogic.xml?

    For some reason I can't get weblogic to recompile my jsp's when I change
              them. I am using Weblogic 6sp1 on NT4. I place my weblogic.xml in the
              d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam\Web-inf
              directory.
              When I change one of the jsps I copy it into the
              d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam directory
              and expect weblgoic to notice it changed. I use ant to copy the jsp's and I
              confirmed that it is actually copying correctly.
              The jsp's use custom tags, but I tried a simple jsp, not using custom tags,
              that doesn't get recompiled either. What could I be doing wrong? Has
              anybody else run into this problem? Restarting weblogic on every change to
              a jsp takes way too long.
              please help.
              -Scot
              <-------here is my weblogic.xml--------------------------->
              <?xml version="1.0" encoding="ISO-8859-1"?>
              <!DOCTYPE weblogic-web-app
              PUBLIC "-//BEASystems, Inc.//DTD Web Application 6.0//EN"
              "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd">
              <weblogic-web-app>
              <description>
              CAM - Customer Account Management
              </description>
              <session-descriptor>
              <session-param>
              <param-name>
              TimeoutSecs
              </param-name>
              <param-value>
              900
              </param-value>
              </session-param>
              <session-param>
              <param-name>
              URLRewritingEnabled
              </param-name>
              <param-value>
              false
              </param-value>
              </session-param>
              </session-descriptor>
              <jsp-descriptor>
              <jsp-param>
              <param-name>
              pageCheckSeconds
              </param-name>
              <param-value>
              1
              </param-value>
              </jsp-param>
              <jsp-param>
              <param-name>
              verbose
              </param-name>
              <param-value>
              true
              </param-value>
              </jsp-param>
              <jsp-param>
              <param-name>
              keepgenerated
              </param-name>
              <param-value>
              true
              </param-value>
              </jsp-param>
              </jsp-descriptor>
              </weblogic-web-app>
              

    This is correct. I started my web-app under a new directory which was not
              the default web-app originally and was not able to refresh the jsp's upon a
              change to the jsp. Next I tried it as the default web-app and I was able to
              refresh the jsp's as described in the weblogic.xml. Thank you for your
              help.
              Is this a known bug? Or should you not be able to use the weblogic.xml
              properites in a web application that is not the default application?
              "cheenle" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Are you start a new server for you own application?
              > I met the same problem, but I found it only appear under a new server
              >
              > "Scot Hale" <[email protected]> wrote:
              > >For some reason I can't get weblogic to recompile my jsp's when I change
              > >them. I am using Weblogic 6sp1 on NT4. I place my weblogic.xml in the
              > >d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam\Web-inf
              > >directory.
              > >
              > >When I change one of the jsps I copy it into the
              > >d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam
              directory
              > >and expect weblgoic to notice it changed. I use ant to copy the jsp's
              > >and I
              > >confirmed that it is actually copying correctly.
              > >
              > >The jsp's use custom tags, but I tried a simple jsp, not using custom
              > >tags,
              > >that doesn't get recompiled either. What could I be doing wrong? Has
              > >anybody else run into this problem? Restarting weblogic on every change
              > >to
              > >a jsp takes way too long.
              > >
              > >please help.
              > >
              > >-Scot
              > >
              > >
              > ><-------here is my weblogic.xml--------------------------->
              > >
              > ><?xml version="1.0" encoding="ISO-8859-1"?>
              > >
              > ><!DOCTYPE weblogic-web-app
              > > PUBLIC "-//BEASystems, Inc.//DTD Web Application 6.0//EN"
              > > "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd">
              > >
              > ><weblogic-web-app>
              > > <description>
              > > CAM - Customer Account Management
              > > </description>
              > >
              > > <session-descriptor>
              > > <session-param>
              > > <param-name>
              > > TimeoutSecs
              > > </param-name>
              > > <param-value>
              > > 900
              > > </param-value>
              > > </session-param>
              > > <session-param>
              > > <param-name>
              > > URLRewritingEnabled
              > > </param-name>
              > > <param-value>
              > > false
              > > </param-value>
              > > </session-param>
              > > </session-descriptor>
              > >
              > > <jsp-descriptor>
              > > <jsp-param>
              > > <param-name>
              > > pageCheckSeconds
              > > </param-name>
              > > <param-value>
              > > 1
              > > </param-value>
              > > </jsp-param>
              > >
              > > <jsp-param>
              > > <param-name>
              > > verbose
              > > </param-name>
              > > <param-value>
              > > true
              > > </param-value>
              > > </jsp-param>
              > >
              > > <jsp-param>
              > > <param-name>
              > > keepgenerated
              > > </param-name>
              > > <param-value>
              > > true
              > > </param-value>
              > > </jsp-param>
              > > </jsp-descriptor>
              > >
              > ></weblogic-web-app>
              > >
              > >
              >
              

  • Weblogic.xml: jsp-descriptor element (working-dir)

    Hi all,
    In order to define correct deployment directory, we want to modify the weblogic.xml with jsp-descriptor as followed (e.g.):
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
    <security-role-assignment>
    <role-name>PrivilegedUser</role-name>
    <principal-name>Administrators</principal-name>
    </security-role-assignment>
    <jsp-descriptor>
    <page-check-seconds>60</page-check-seconds>
    <precompile>false</precompile>
    <precompile-continue>false</precompile-continue>
    <keepgenerated>true</keepgenerated>
    <verbose>true</verbose>
    *<working-dir>D:\Oracle\Middleware</working-dir>*
    </jsp-descriptor>
    <charset-params>
    <input-charset>
    <resource-path>/*</resource-path>
    <java-charset-name>UTF-8</java-charset-name>
    </input-charset>
    </charset-params>
    </weblogic-web-app>
    My questions:
    1- Is the solution (using weblogic.xml and modify working-dir) correct?
    2- What is the best approach:
    a- preparing <working-dir>D:\Oracle\Middleware</working-dir> via development phase and responsiblity of developer team?
    b- adjust and modify application(s) via adminstrators
    3- I find the following doc:
    http://docs.tpu.ru/docs/Oracle/en/fmw/11.1.1.6.0/web.1111/e13712/weblogic_xml.htm#i1038490
    Is there more doc/sample/info available regarding this matter?
    Regards,
    Moh

    Hi all,
    In order to define correct deployment directory, we want to modify the weblogic.xml with jsp-descriptor as followed (e.g.):
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
    <security-role-assignment>
    <role-name>PrivilegedUser</role-name>
    <principal-name>Administrators</principal-name>
    </security-role-assignment>
    <jsp-descriptor>
    <page-check-seconds>60</page-check-seconds>
    <precompile>false</precompile>
    <precompile-continue>false</precompile-continue>
    <keepgenerated>true</keepgenerated>
    <verbose>true</verbose>
    *<working-dir>D:\Oracle\Middleware</working-dir>*
    </jsp-descriptor>
    <charset-params>
    <input-charset>
    <resource-path>/*</resource-path>
    <java-charset-name>UTF-8</java-charset-name>
    </input-charset>
    </charset-params>
    </weblogic-web-app>
    My questions:
    1- Is the solution (using weblogic.xml and modify working-dir) correct?
    2- What is the best approach:
    a- preparing <working-dir>D:\Oracle\Middleware</working-dir> via development phase and responsiblity of developer team?
    b- adjust and modify application(s) via adminstrators
    3- I find the following doc:
    http://docs.tpu.ru/docs/Oracle/en/fmw/11.1.1.6.0/web.1111/e13712/weblogic_xml.htm#i1038490
    Is there more doc/sample/info available regarding this matter?
    Regards,
    Moh

  • How can i catch the jsp checking event ?

    As we know, there are three parameters which is about checking in the weblogic.xml, pageCheckSeconds,*servlet-reload-check-secs*,*resource-reload-check-secs*, but how can i catch the checking event when the webapp is active.
    The fellowing is my simple test, i deployed a webapp on a weblogic server instance, and it was actived. I wrote a simple bash shell to try to catch the event, but fail. i througnt it may be dependent on the webapp's stage mode. but i change the mode, and try again, it was fail too.
    [weblogic@tdy218 ~]$ ls
    getLastAccessTime.sh webapps
    [weblogic@tdy218 ~]$ ./getLastAccessTime.sh ~/webapps/Test/login.jsp
    The file's last access time is: 2011-05-22 11:10:21.000000000 +0800
    The file's last access time is: 2011-05-22 11:10:21.000000000 +0800
    The file's last access time is: 2011-05-22 11:10:21.000000000 +0800
    The file's last access time is: 2011-05-22 11:10:21.000000000 +0800
    The file's last access time is: 2011-05-22 11:10:21.000000000 +0800
    The file's last access time is: 2011-05-22 11:10:21.000000000 +0800
    The file's last access time is: 2011-05-22 11:10:21.000000000 +0800
    [weblogic@tdy218 ~]$ ./getLastAccessTime.sh
    /bea/wls924/user_projects/domains/base_domain/servers/AdminServer/stage/Test/Test/login.jsp
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    The file's last access time is: 2011-05-22 11:11:37.000000000 +0800
    [weblogic@tdy218 ~]$ stat
    /bea/wls924/user_projects/domains/base_domain/servers/AdminServer/stage/Test/Test/login.jsp
    File: `/bea/wls924/user_projects/domains/base_domain/servers/AdminServer/stage/Test/Test/login.jsp'
    Size: 634 Blocks: 8 IO Block: 4096 regular file
    Device: 804h/2052d Inode: 583725 Links: 1
    Access: (0644/-rw-r--r--) Uid: ( 502/weblogic) Gid: ( 500/ bea)
    Access: 2011-05-22 11:11:37.000000000 +0800
    Modify: 2010-05-24 14:49:08.000000000 +0800
    Change: 2011-05-22 11:10:21.000000000 +0800
    The jsp file's last access time didn't changed in the past.
    [weblogic@tdy218 ~]$ more getLastAccessTime.sh
    #!/bin/bash
    declare -i m=1
    declare -i n=100
    while [ $m -le $n ]; do
    echo "The file's last access time is: $(stat -c %x $1)"
    m=m+1
    sleep 3
    done
    weblogic.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.oracle.com/technology/weblogic/servers/wls810/dtd/weblogic810-web-jar.dtd">
    <weblogic-web-app>
    <jsp-descriptor>
    <jsp-param>
    <param-name>pageCheckSeconds</param-name>
    <param-value>2</param-value>
    </jsp-param>
    </jsp-descriptor>
    <container-descriptor>
    <servlet-reload-check-secs>2</servlet-reload-check-secs>
    <resource-reload-check-secs>2</resource-reload-check-secs>
    </container-descriptor>
    <context-root>/jdbc</context-root>
    </weblogic-web-app>
    env :
    WebLogic 9.2 MP4、Redhat Linux AS 4 Update 8 x86.

    I tested on WLS 11g ps2(10.3.3) which is running in Development Mode also, but it was the same as WLS 9.2 MP4.
    During the weblogic server running, it don't check the application resources , but it will check the $Domain_Home/autodeploy directory every three seconds in Development Mode , the following is the result.
    [weblogic@tdy218 ~]$ ./getLastAccessTime.sh /bea/wls924/user_projects/domains/base_domain/autodeploy
    The file's last access time is: 2011-05-22 12:01:43.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:43.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:43.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:46.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:46.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:46.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:49.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:49.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:49.000000000 +0800
    The file's last access time is: 2011-05-22 12:01:52.000000000 +0800
    Ctrl + ^
    [weblogic@tdy218 ~]$ ./getLastAccessTime.sh ~/webapps/Test
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    The file's last access time is: 2011-05-22 17:26:25.000000000 +0800
    Ctrl + ^
    [weblogic@tdy218 ~]$ ./getLastAccessTime.sh ~/webapps/Test/
    insert.jsp login.jsp query.jsp tdy218.sql WEB-INF/
    [weblogic@tdy218 ~]$ ./getLastAccessTime.sh ~/webapps/Test/login.jsp
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    The file's last access time is: 2011-05-22 11:44:31.000000000 +0800
    Ctrl + ^
    I set the frequency to every one seconds this time by using sleep method in my Bash Shell script.
    #!/bin/bash
    declare -i m=1
    declare -i n=100
    while [ $m -le $n ]; do
    echo "The file's last access time is: $(stat -c %x $1)"
    m=m+1
    sleep 1
    done

  • How do I setup in wls 6.1 a jsp file that has a different extension (not *.jsp)

    I have a jsp file with extension *.abc. The browser is showing the files as text instead of sending it to be processed as a jsp file.
              I have the following settings in the web.xml but it is not picking it up.
              <servlet-mapping>
              <servlet-name>
              jsp
              </servlet-name>
              <url-pattern>
              *.abc
              </url-pattern>
              </servlet-mapping>     
              

    This is kind of a hack and not officially supported, but you might try...
              <servlet>
              <servlet-name>ABC</servlet-name>
              <servlet-class>weblogic.servlet.JSPServlet</servlet-class>
              <init-param>
              <param-name>compileCommand</param-name>
              <param-value>javac</param-value>
              </init-param>
              <init-param>
              <param-name>workingDir</param-name>
              <param-value>WEB-INF/classes</param-value>
              </init-param>
              </servlet>
              Since this isn't the default JSPServlet registration, it doesn't pick up the
              default JSPServlet init arguments, so after some experimentation I figured
              out that you have to at least define these two. Others that you may want to
              configure are...
              defaultFileName
              compileCommand
              compilerClass
              compileFlags
              workingDir
              verbose
              keepgenerated
              precompileContinue
              pageCheckSeconds
              encoding
              packagePrefix
              superclass
              noTryBlocks
              compilerSupportsEncoding
              These are all defined as jsp-descriptor args in the weblogic.xml file, but
              you can equally use them as servlet-args for your custom JSP registration
              Good luck,
              Alex
              P.S.
              Why don't you want to use jsp files anyway?
              "shelley otero" <[email protected]> wrote in message
              news:[email protected]...
              > I have a jsp file with extension *.abc. The browser is showing the files
              as text instead of sending it to be processed as a jsp file.
              >
              > I have the following settings in the web.xml but it is not picking it up.
              >
              > <servlet-mapping>
              > <servlet-name>
              > jsp
              > </servlet-name>
              > <url-pattern>
              > *.abc
              > </url-pattern>
              > </servlet-mapping>
              >
              

  • Precompilation of JSPs

    Hi all....
              we have a problem regarding the precompilation of the JSP pages. In
              development mode we don't want the jsps top get precompiled when the
              Server is restarted or app is redeployed as it takes a lot of time to
              see a minor change working.
              For this we have modified our weblogic.xml file in the WAR
              descriptors as:
              <jsp-descriptor>
              <jsp-param>
              <param-name>precompile</param-name>
              <param-value>false</param-value>
              </jsp-param>
              </jsp-descriptor>
              but for some reason it does not seem to work..
              any pointers to correct it...????
              thanx
              aseem
              

    I never found a fix for this.
              In the end I just wrote an ant script using basic ant tasks i.e. no weblogic ant tasks - and used the weblogic.xml file to get the server to precompile jsps at deploy time.
              My experience with the weblogic ant tasks has been less than satisfactory.
              Good luck - and let me know if you have any major breakthroughs.

  • JSP precompilation and my .java files compilation issues /  building WAR file using ANT

    Hello.
    I am new to working with WAR files and the whole process of it. A little
    background on what we are using. We are using, WLS 6.1 SP3. I am using the
    ant.bat that is supplied in the bin directory of the WLS install.
    I am trying to work with ANT and getting it to build the file. I am making
    progress, but at a point where I am having trouble getting my java code
    files to compile using ant. I am having one issue and looking to do one
    other item.
    1) I would like to precompile the JSPs if possible prior to putting into the
    WAR file. Not sure if this is done or not, but there was a utility when I
    was working with ibm's app server that gave us the ability to do a batch
    complile. Was thinking that maybe a similair concept is possibly here.
    2) Having issue getting ant to compile code properly. In the compile
    section of the build.xml file for ant, I tell it where the source files are,
    and the destionation folder for the compiled class files. I then try to set
    the classpath so that it finds the .jar files that are necessary for my
    source files to complile. But, it won't find them. And not sure how come.
    I may be going about this all wrong, but dont know. Here is the compile
    section of the build.xml I am using:
    <target name="compile" depends="prepare">
    <javac srcdir="classes" destdir="${deploy.home}/WEB-INF/classes"
    classpath="$(lib.home)"
    debug="on" optimize="on" deprecation="off"/>
    </target>
    One note, I've tried many different items in the classpath line, which
    don't work. if I do *.jar it fails at complie time, invalid argument. As
    well as if I use *.* and so on. if I list the explicit file names, it still
    doesn't seem to find them.
    I was wondering if anyone could help, if you need anymore information let me
    know, I can send the entire build.xml if necessary. I may be missing
    items, seeing that this is my first try at using ANT.
    Any help is appreciated and thanks in advance. Hopefully not sounding too
    off the wall. Hopefully get some clarification and understanding.
    Thank you.
    Kevin.

    Kevin Price wrote:
    Hello.
    I am new to working with WAR files and the whole process of it. A little
    background on what we are using. We are using, WLS 6.1 SP3. I am using the
    ant.bat that is supplied in the bin directory of the WLS install.
    I am trying to work with ANT and getting it to build the file. I am making
    progress, but at a point where I am having trouble getting my java code
    files to compile using ant. I am having one issue and looking to do one
    other item.
    1) I would like to precompile the JSPs if possible prior to putting into the
    WAR file. Not sure if this is done or not, but there was a utility when I
    was working with ibm's app server that gave us the ability to do a batch
    complile. Was thinking that maybe a similair concept is possibly here.you can use weblogic.jspc
    http://e-docs.bea.com/wls/docs70/jsp/reference.html#57794
    or just set the precompile flag in weblogic.xml
    You can configure WebLogic Server to precompile your JSPs when a Web
    Application is deployed or re-deployed or when WebLogic Server starts up
    by setting the precompile parameter to true in the <jsp-descriptor>
    element of the weblogic.xml deployment descriptor.
    >
    2) Having issue getting ant to compile code properly. In the compile
    section of the build.xml file for ant, I tell it where the source files are,
    and the destionation folder for the compiled class files. I then try to set
    the classpath so that it finds the .jar files that are necessary for my
    source files to complile. But, it won't find them. And not sure how come.
    I may be going about this all wrong, but dont know. Here is the compile
    section of the build.xml I am using:
    <target name="compile" depends="prepare">
    <javac srcdir="classes" destdir="${deploy.home}/WEB-INF/classes"
    classpath="$(lib.home)"
    debug="on" optimize="on" deprecation="off"/>
    </target>
    maybe because you are not using curly braces there on lib.home??
    if you do it the way above, you would have to list all your jars
    classpath="$(lib.home)\lib1.jar:$(lib.home)\lib2.jar"
    or you can nest
    <javac srcdir="classes" destdir="${deploy.home}/WEB-INF/classes"
    debug="on" optimize="on" deprecation="off">
         <classpath>
              <fileset dir="${lib.home}" includes="*.jar" />
         </classpath>
    </javac>
    One note, I've tried many different items in the classpath line, which
    don't work. if I do *.jar it fails at complie time, invalid argument. As
    well as if I use *.* and so on. if I list the explicit file names, it still
    doesn't seem to find them.
    I was wondering if anyone could help, if you need anymore information let me
    know, I can send the entire build.xml if necessary. I may be missing
    items, seeing that this is my first try at using ANT.
    Any help is appreciated and thanks in advance. Hopefully not sounding too
    off the wall. Hopefully get some clarification and understanding.
    Thank you.
    Kevin.

  • JSP compiler obfuscates generated servlet debug line numbers

              Here's something that's been baffling me for a couple of days now.
              When WebLogic parses a JSP into servlet Java source, and then compiles the Java
              source into a class, it seems to perform a further step to obfuscate debug line
              numbers in the _jspService method. This converts the debug line numbers from Java
              source code line numbers into JSP line numbers.
              At first sight, this may appear to be useful- it means that when an exception
              is thrown then it references a line number in the original JSP rather than one
              in the generated servlet. However, it actually makes life more difficult when
              you consider included JSPs.
              Suppose you have a file loginresult.jsp, which uses @include to include a header.jsp
              and footer.jsp, both of which contain dynamic content. When WebLogic converts
              line numbers, it ignores the JSP that the code came from, so this causes a many-to-one
              mapping of line numbers. When an error occurs, the exception will tell you the
              line number that it came from, but it won't tell you which JSP caused it. The
              many-to-one mapping ensures a loss of information- and no way of retrieving the
              real line numbers.
              This is an even bigger nuisance when trying to debug JSPs- the debugger hops around
              in the generated servlet file without giving any clue as to whereabouts it really
              is in the code.
              My question is: is there any way of switching off this post-processor behaviour?
              One obvious way would be to locate the WebLogic class that does this post-processing,
              stub it out and run WebLogic with this class higher up in the classpath. But that's
              a last resort.
              Secondly, would there be any other impact in turning off this behaviour? Do other
              parts of WebLogic rely on this?
              Thanks in advance,
              Kevin.
              

    Actually, this option turns line-number table replacement on and off, for example,
              with jsp like this:
              test.jsp
              <%
              throw new Exception();
              %>
              and weblogic.xml:
              <!DOCTYPE weblogic-web-app PUBLIC "-//BEA
              Systems, Inc.//DTD Web Application 7.0//EN"
              "http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd">
              <weblogic-web-app>
              <jsp-descriptor>
              <jsp-param>
              <param-name>debug</param-name>
              <param-value>true</param-value>
              </jsp-param>
              </jsp-descriptor>
              </weblogic-web-app>
              the stacktrace looks like this (note line number 2 - this is JSP line number):
              java.lang.Exception
              at jsp_servlet.__test._jspService(test.jsp:2)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:945)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:332)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:376)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
              at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5360)
              at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              and with debug option turned off:
              <!DOCTYPE weblogic-web-app PUBLIC "-//BEA
              Systems, Inc.//DTD Web Application 7.0//EN"
              "http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd">
              <weblogic-web-app>
              <jsp-descriptor>
              <jsp-param>
              <param-name>debug</param-name>
              <param-value>false</param-value>
              </jsp-param>
              </jsp-descriptor>
              </weblogic-web-app>
              exception stacktrace looks like this (note that line number now is from generated .java file):
              java.lang.Exception
              at jsp_servlet.__test._jspService(__test.java:87)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:945)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:332)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:376)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
              at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5360)
              at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              Kevin Thomas <[email protected]> wrote:
              > But this isn't useful, as you don't know which JSP the line number is referring
              > to! (did it come from the main JSP, or one of the files that it included?)
              > Turning debug off is not an answer- because that will lose other useful information
              > that is useful to the debugger.
              > Kevin.
              > "Dimitri I. Rakitine" <[email protected]> wrote:
              >>Actually, this is useful when you want to debug .jsp's and not generated
              >>..java files. Did you try setting 'debug' jsp-param in the weblogic.xml
              >>to
              >>false? I think it turns class postprocessing on and off.
              >>
              >>Kevin Thomas <[email protected]> wrote:
              >>
              >>> Here's something that's been baffling me for a couple of days now.
              >>
              >>> When WebLogic parses a JSP into servlet Java source, and then compiles
              >>the Java
              >>> source into a class, it seems to perform a further step to obfuscate
              >>debug line
              >>> numbers in the _jspService method. This converts the debug line numbers
              >>from Java
              >>> source code line numbers into JSP line numbers.
              >>
              >>> At first sight, this may appear to be useful- it means that when an
              >>exception
              >>> is thrown then it references a line number in the original JSP rather
              >>than one
              >>> in the generated servlet. However, it actually makes life more difficult
              >>when
              >>> you consider included JSPs.
              >>
              >>> Suppose you have a file loginresult.jsp, which uses @include to include
              >>a header.jsp
              >>> and footer.jsp, both of which contain dynamic content. When WebLogic
              >>converts
              >>> line numbers, it ignores the JSP that the code came from, so this causes
              >>a many-to-one
              >>> mapping of line numbers. When an error occurs, the exception will tell
              >>you the
              >>> line number that it came from, but it won't tell you which JSP caused
              >>it. The
              >>> many-to-one mapping ensures a loss of information- and no way of retrieving
              >>the
              >>> real line numbers.
              >>
              >>> This is an even bigger nuisance when trying to debug JSPs- the debugger
              >>hops around
              >>> in the generated servlet file without giving any clue as to whereabouts
              >>it really
              >>> is in the code.
              >>
              >>> My question is: is there any way of switching off this post-processor
              >>behaviour?
              >>> One obvious way would be to locate the WebLogic class that does this
              >>post-processing,
              >>> stub it out and run WebLogic with this class higher up in the classpath.
              >>But that's
              >>> a last resort.
              >>
              >>> Secondly, would there be any other impact in turning off this behaviour?
              >>Do other
              >>> parts of WebLogic rely on this?
              >>
              >>> Thanks in advance,
              >>
              >>> Kevin.
              >>
              >>--
              >>Dimitri
              >>
              Dimitri
              

  • WebLogic Server - Problem encoding file MS Word in jsp

    Hi, i'm new in this forum...sorry for my english but i don't speak it very well...
    I have a problem with encoding of a MS Word file (with WebLogic Server 8.1.4).....I have this file stored in a DB Oracle like a BLOB...then I extract this file and I obtain the bytes of this file....than i write this byte in my ServletOutputStream so that i can see this word document from my jsp page in word format....until now everithing is ok...MS Word is open....but in the file the character are not encoded....are like this
    "ÐÏ à¡± á ÿÿÿÿÿÿÿÿÿÿ "....... why i can't see it correctly???
    What I don't understand is thas:
    1)in the same page with a pdf (even this extract as byte from oracle column BLOB) works fine
    2)with the same web application deployed on a tomcat server everithings work fine (with doc,xls....)
    3)I think that every settings is ok....
    in the jsp file
    response.setContentType("application/msword");
    response.setHeader("Content-Disposition", "attachment; filename=test.doc");
    in web.xml
    <mime-mapping>
    <extension>doc</extension>
    <mime-type>application/msword</mime-type>
    </mime-mapping>
    in weblogic.xml (I have read this in a forum)
    <jsp-descriptor>
    <jsp-param>
    <param-name>encoding</param-name>
    <param-value>UTF-8</param-value>
    </jsp-param>
    <jsp-param>
    <param-name>compilerSupportsEncoding</param-name>
    <param-value>false</param-value>
    </jsp-param>
    </jsp-descriptor>
    The file that i obtain is not encode but is corret....infact if i make a compare (with a program "Beyond Compare" that meka a compare with the character not encoded like "ÐÏ à¡± á ÿÿÿÿÿÿÿÿÿÿ ") between the file that I obtain and the original file....everithing is equal...so the file is ok....but i can't open this correctly and visualize it correctly in word format!
    Please help me.....thanks so much

    i was able to solve it by clearing the output stream (jsp page - out.clear() ) before using it, even resetting the jsp response does the trick..
    thanks,
    prakash.m
    Edited by message2prakash at 02/08/2008 10:35 AM
    Edited by message2prakash at 02/08/2008 10:36 AM

  • Jsp compile error in weblogic 10.3

    When i run the project, an error has occured. The jsp page only contains few words.
    weblogic.servlet.jsp.CompilationException: Failed to compile JSP /deployed/SYSTEM/Function_List/1/resources/List Functions.jsp
    List Functions.jsp:1:1: The public type __list_32_functions must be defined in its own file
    This is a JSP page.
    ^-----------------^
    at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:328)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:237)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:182)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
    at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    Could somebody help me.

    Add this tag to your weblogic.xml file and deploy the application and check it ,it should work
    <jsp-descriptor>
    <jsp-param>
    <param-name>
    compileCommand
    </param-name>
    <param-value>
    sj
    </param-value>
    </jsp-param>
    </jsp-descriptor>

  • Deployment descriptor "weblogic.xml" is malformed. in managed server

    Hi All,
              Appreciate if anyone can help.
              I have set up a cluster containing two nodes - one local and other
              remote machine on weblogic 8.1.4
              then i install my application this cluster setup its working fine.
              for my requirement i upgrade the the weblogic version from 8.1.4 to
              8.1.6 .
              i upgrade through the smart update from the bea site . i upgraded both
              the node.
              i started the admin server.it started with no issue.
              my problem comes when i start the my managed server on the cluster .it
              gives me this exception.
              <HTTP> <BEA-101296> <Unable to load the default compiler class
              "com.sun.tools.javac.Main". Using the default javac compiler to compile
              JSPs.>
              i checked the classpath it has the same jdk that i used for 8.1.4
              (jdk1.4.05 from sun.)
              should i used new jdk that comes with the upgrade package of 8.1.6 like
              (jdk1.4.11)
              my class path having the weblogic jar also.
              this is my class path.:
              E:\bea\weblogic81\server\lib\weblogic.jar and other my application
              jars.
              complete exception it is shown like :
              <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
              <Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
              Module: 'Nexaweb': Public ID references the old version of the Servlet
              DTD. You must change the public ID in web.xml file to "-//Sun
              Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
              <[Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
              Check against the DTD: org.xml.sax.SAXParseException: The content of
              element type "weblogic-web-app" must match
              "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
              (line 26, column 20).>
              Compiler class: 'com.sun.tools.javac.Main', not found
              java.lang.ClassNotFoundException: com.sun.tools.javac.Main
              at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
              at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
              at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:141)
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
              <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
              will have better performance if it is enabled. To enable
              call-by-reference, set the enable-call-by-reference element to True in
              the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
              <Failed to initialize the application Xellerate due to error
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
              <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
              to initialize due to failed deployments.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
              <The deployment framework was unable to resume accepting requests.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
              <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
              deployment framework was unable to resume accepting
              requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
              is unable to initialize due to failed deployments.>
              hope the scope of the questions is not too broad. Kindly let me know
              if you need more information.
              Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • Precompile JSP's in Weblogic 5.1/SP6

              Hello,
              How do you get the precomplilation of JSP's to work in 5.1? I have
              seen some emails on this mailing list about how to precompile the
              JSP's in 6.0 but I would like to know how to do it in 5.1. looking
              at the documentation here: http://www.weblogic.com/docs51/classdocs/API_jsp.html#register
              In the weblogic properties file we have them set as follows:
              weblogic.httpd.documentRoot=htdocs/
              # WEBLOGIC JSP PROPERTIES
              # Sets up automatic page compilation for JSP. Adjust init argsfor
              # directory locations and uncomment to use.
              weblogic.httpd.register.*.jsp=weblogic.servlet.JSPServlet
              weblogic.httpd.initArgs.*.jsp=\
              pageCheckSeconds=1,\
              keepgenerated=true,\
              compileCommand=d:/jdk1.2.2/bin/javac.exe,\
              workingDir=D:/Mediaprise/mpsite/WebLogicServer,\
              verbose=true
              that should be picking up any JSP's underneath the document root
              folder (htdocs, in this case) and precompile them to the working
              dir. now we have JSP's in the htdocs folder and a whole stucture
              of JSP's underneath the htdocs folder in a folder called JSP with
              it's own file and directory structure. The weblogic.log file shows
              that the above properties are being set correctly on startup but
              no precompilation seems to be happening to the working dir. any
              ideas on how to make this work in 5.1??
              I am working on Weblogic 5.1 with SP6.
              Thanks,
              Gagan
              

    In WebLogic 6.0 register each jsp in the web.xml with a <servlet-name>, <jsp-file>
              and <load-on-startup>. For example:
              <web-app>
              <servlet>
              <servlet-name></servlet-name>
              <jsp-file></jsp-file>
              <load-on-startup></load-on-startup>
              </servlet>
              <servlet-mapping>
              <servlet-name></servlet-name>
              <url-pattern></url-pattern>
              </servlet-mapping>
              </web-app>
              The optional value of load-on-startup element must be a positive integer indicating
              the order in which the servlet should be loaded.
              In WebLogic 6.1 set the precompile parameter in weblogic.xml.
              <jsp-descriptor>
              <jsp-param>
              <param-name>
              precompile
              </param-name>
              <param-value>
              true
              </param-value>
              </jsp-param>
              </jsp-descriptor>
              Vaibhav wrote:
              > This solution is with web.xml, if I am
              > using weblogic.properties only and no web.xml, How do I specify precompile=true ?
              

  • Info on JSP caching in WebLogic 5.1

              Hi,
              I found your name in the Weblogic newsgroup and hence decided to post this
              question to you. Hope you do'nt mind my asking it.
              I would like to know something about caching of Java Server Pages in WebLogic
              5.1. How effective is it for developing and deploying applications on WebLogic
              Server ? Has caching in WebLogic been tried out extensively in deploying applications
              before ? How successful have they been ?
              In particular, I would like to know if any deadlock occurrs in Java Server
              Page caching in WebLogic.
              Also can I force a cache to refresh within the timeout period (i.e., before
              the elapse of the timeout for the particular cache) ?
              Also, how is the async attribute used in <wl:cache> tag ? Is there any performance
              bottleneck occurring due to its usage ?
              I would love to have answers to all my questions. However even if I get some
              answers it will be highly appreciated.
              Regards,
              Sumantu
              

    In WebLogic 6.0 register each jsp in the web.xml with a <servlet-name>, <jsp-file>
              and <load-on-startup>. For example:
              <web-app>
              <servlet>
              <servlet-name></servlet-name>
              <jsp-file></jsp-file>
              <load-on-startup></load-on-startup>
              </servlet>
              <servlet-mapping>
              <servlet-name></servlet-name>
              <url-pattern></url-pattern>
              </servlet-mapping>
              </web-app>
              The optional value of load-on-startup element must be a positive integer indicating
              the order in which the servlet should be loaded.
              In WebLogic 6.1 set the precompile parameter in weblogic.xml.
              <jsp-descriptor>
              <jsp-param>
              <param-name>
              precompile
              </param-name>
              <param-value>
              true
              </param-value>
              </jsp-param>
              </jsp-descriptor>
              Vaibhav wrote:
              > This solution is with web.xml, if I am
              > using weblogic.properties only and no web.xml, How do I specify precompile=true ?
              

  • !!! Jsp compilation error in deploying : in migrating from WLS 8.1 to 9.2

    Hi,
    We are trying to migrate a .war file from WLS 8.1 to WLS 9.2. After other changes are done, while deploying the .war file in in WLS 9.2 we are getting errors for a jsp file:
    1&gt; Syntax error near 'import' ^-------------------^
    2&gt; at Line 6 ;The qualifier of this name is a package,which cannot contain methods ^---------------------^
    the jsp is simple one & goes like this:: (this jsp file also included in another jsp file .... not sure if this causing the problem ?)
    &lt;%@ page import="com.src.config.ConfigurationManager" %&gt; // this class is properly present in /WEb-INF/classes/com/src/config/ .... causing error 1
    &lt;%
    String sRequestURI = request.getRequestURI();
    String sBaseURI = sRequestURI.substring(0, sRequestURI.lastIndexOf("/"));
    ConfigurationManager configMan = ConfigurationManager.getInstance(); // Line 6 .. causing error 2
    String sOraRoot = configMan.getProperty("OraRoot");
    %&gt;
    any help please !!
    Edited by: user10284044 on Dec 10, 2008 10:54 PM

    Hi,
    You can get rid of JSP version specific problems by using the following weblogic.xml file:-
    <weblogic-web-app>
    <jsp-descriptor>
    <jsp-param>
    <param-name>backwardCompatible</param-name>
    <param-value>true</param-value>
    </jsp-param>
    </jsp-descriptor>
    <weblogic-web-app>
    It will also confirm if the error you are seeing is due to JSP version differences in 8.1 and 9.x.
    Regards.

  • Precompiling jsp's in weblogic

    Hi ,
    I want to precompile my jsp's when I start the server. I don't want wait for long time when the page start's loading. Can we do this in weblogic.
    Any help will be appreciated.
    Thanks
    Anitha

    hi anitha,
    yes you can do that in Weblogic by setting up the precompile parameter for <jsp-descriptor> element to be true in weblogic.xml descriptor file when the web application gets deployed or re-deployed !!
    cheers
    abhijeet

Maybe you are looking for