JSP 2.0 JSTL in weblogic 8.1

Has anyone successfully using JSP 2.0 & JSTL in weblogic 8.1? We built a project using tomcat 5 and work well. The problem is weblogic 8.1 does seem to support the code. Is there any work around? Thanks
          

          "Chi Mok" <[email protected]> wrote in message
          news:4028ea91$[email protected]..
          > Has anyone successfully using JSP 2.0 & JSTL in weblogic 8.1? We built a
          project using tomcat 5 and work well. The problem is weblogic 8.1 does seem
          to support the code. Is there any work around? Thanks
          WebLogic 8.1 doesnt support JSP2.0 & Servlet 2.4 (or any of the J2EE 1.4
          apis) The next version (an upcoming release) will support J2EE 1.4 and thus
          jsp20 + JSTL 1.1
          JSTL 1.0 and JSP1.2 gel pretty well on weblogic 81
          --Nagesh
          

Similar Messages

  • Jstl and weblogic 7.0

              Has anyone used the new jstl with Weblogic 7.0.
              I am unable to get any of the tags to work.
              Weblogic keeps giving me the error message:
              The taglib validator rejected the page: "org.xml.sax.SAXParseException: The root
              element is required in a well-formed document.
              I even get this error message for the examples included in the
              standard-examples.war file.
              If I edit the .tld file and comment out the validator, the tags work fine.
              

    What if you need to access more than one data source?
              <sql:query var="myQuery" dataSource="myDataSource">
              </sql:query>
              <sql:query var="myOtherQuery" dataSource="myOtherDataSource">
              </sql:query>
              If you specify one data source as the default, how do you access the other
              one?
              -- Craig
              "thanh nguyen" <[email protected]> wrote in message
              news:3fa18529$[email protected]..
              > I believe you can set up a default datasource for the application context
              in the web.xml and weblogic.xml. That way, on your JSP, you will not need to
              set the datasource. The connection pool will handle all of that for you.
              >
              > 1. modified weblogic.xml
              > <reference-descriptor>
              > <resource-description>
              > <res-ref-name>jdbc/hr</res-ref-name>
              > <jndi-name>jdbc/hr</jndi-name>
              > </resource-description>
              > </reference-descriptor>
              > 2. modified web.xml
              > <context-param>
              > <param-name>javax.servlet.jsp.jstl.sql.dataSource</param-name>
              > <param-value>jdbc/hr</param-value>
              > </context-param>
              >
              > <resource-ref>
              > <res-ref-name>jdbc/hr</res-ref-name>
              > <res-type>javax.sql.DataSource</res-type>
              > <res-auth>CONTAINER</res-auth>
              > </resource-ref>
              > 3. redeploy app
              

  • One JSP Coded in JSTL with an Action Link and a Form

    My JSP written in JSTL with an action link works fine. The checkboxes are well recognized ( I have a "form" specified in both the action mapping and form bean).
    <%@ page import="......common.pojo.user.User" %>
    <!-- Create a variable in scope called userRows from the Users object -->
    <c:set var="userRows" value="${requestScope.Users}" />
    <c:choose>
         <c:when test="${not empty userRows}">
              <!-- create a "user" object for each element in the userRows -->               
              <c:forEach var="user" items="${userRows}" varStatus="idx">
                      <c:choose>
                              <c:when test="${( idx.count+1 )%2==0}">
                                 <tr class="contentCell1">
                              </c:when>
                              <c:otherwise>
                                 <tr class="contentCell2">
                              </c:otherwise>
                      </c:choose>
                                           <td align="center">
                                                              <html-el:checkbox property="selectedUsers[${idx.index}].selected" />
                                                              <html-el:hidden property="selectedUsers[${idx.index}].id" value="${user.id}"/>
                                           </td>
                                           <td align="center"><c:out value="${user.createdByUserID}" /></td>
                                           <td align="center"><c:out value="${user.firstName}" /></td>
                                           <td align="center"><c:out value="${user.lastName}" /></td>
                             </tr>
              </c:forEach>
                        <tr>
                             <td colspan="6" align="left">
                                      <html-el:link action="/admin/selectUsers.do">Edit Selected Users</html-el:link>
                             </td>
                           </tr>
                   </table>
              </c:when>
              <c:otherwise>
                   <center><H1>No User Found.</H1></center>
              </c:otherwise>
         </c:choose>
    ......But, if I add another form (form B) with some textfield(s) and a submit button in between the opening <c:when ...> and <c:forEach ... > tag, I get the "runtime" JSP error: "cannot find bean: "org.apache.struts.taglib.html.BEAN" in any scope".
    The form B also works well. And varStatus="idx" and var="user" still work. The complaint points specifically to the <html-el:checkbox property="selectedUsers[${idx.index}].selected" />. The getter method for selectedUsers[0].selected can no longer be recognized:
    <%@ page import="......common.pojo.user.User" %>
    <!-- Create a variable in scope called userRows from the Users object -->
    <c:set var="userRows" value="${requestScope.Users}" />
    <c:choose>
         <c:when test="${not empty userRows}">
                                    <html-el:form action="/admin/findUsers.do">
                                               // many textfields and a submit button
                                    </html-el:form>
              <!-- create a "user" object for each element in the userRows -->               
              <c:forEach var="user" items="${userRows}" varStatus="idx">
                      <c:choose>
                              <c:when test="${( idx.count+1 )%2==0}">
                                 <tr class="contentCell1">
                              </c:when>
                              <c:otherwise>
                                 <tr class="contentCell2">
                              </c:otherwise>
                      </c:choose>
                                           <td align="center">
                                                              <html-el:checkbox property="selectedUsers[${idx.index}].selected" />
                                                              <html-el:hidden property="selectedUsers[${idx.index}].id" value="${user.id}"/>
                                           </td>
                                           <td align="center"><c:out value="${user.createdByUserID}" /></td>
                                           <td align="center"><c:out value="${user.firstName}" /></td>
                                           <td align="center"><c:out value="${user.lastName}" /></td>
                             </tr>
              </c:forEach>
                        <tr>
                             <td colspan="6" align="left">
                                      <html-el:link action="/admin/selectUsers.do">Edit Selected Users</html-el:link>
                             </td>
                           </tr>
                   </table>
              </c:when>
              <c:otherwise>
                   <center><H1>No User Found.</H1></center>
              </c:otherwise>
         </c:choose>
    ......

    Hi,
    your strtus config file looks like
    <form-beans >
    <form-bean name="manageAuditFindingsForm" type="com.lib.struts.form.ManageAuditFindingsForm" />
    </form-beans >
    <action
          attribute="manageAuditFindingsForm"
          input="/New.jsp"
          name="manageAuditFindingsForm"
          path="/manageauditfindings"
          scope="request"
          type="com.lib.struts.action.ManageAuditFindingsAction">
          <forward name="success" path="/AuditFindings.jsp" />
        </action>Thanks
    Edward

  • PageCheckSeconds (precompile jsp, stored in war file) (Weblogic 6.1)

    Hi,
              I'm trying to stop the webserver from trying to recompile/check my jsp pages. I have set the pageCheckSeconds param to -1 but that doesn't seem to work. Looking at the weblogic.log file I get:
              [WebAppServletContext(601285,kcs,/kcs)] WorkflowServlet: init>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: init>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param verbose initialized to: true>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param packagePrefix initialized to: jsp_servlet>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param compilerclass initialized to: javac>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param srcCompiler initialized to weblogic.jspc>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param superclass initialized to weblogic.servlet.jsp.JspBase>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param workingDir initialized to: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param pageCheckSeconds initialized to: -1>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: initialization complete>
              [WebAppServletContext(601285,kcs,/kcs)] Generated java file: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs\jsp_servlet\__index.java>
              If I take out the jsp class files from the war file and set the param workingDir (weblogic.xml) to the directory where the jsp class files are located... it works. But now I have a packaging problem that I can easily solve by keeping the jsp class files within the war file. As you can see from the log messages above, the pageCheckSeconds value is set to -1... yet the checking occurred anyway. Is there a way to specify the name of the war file that is located within an EAR file using the workingDir param?
              Thanks
              David
              [att1.html]
              

    You say: "If I take out the jsp class files from the war file and set the param workingDir (weblogic.xml) to the directory where the jsp class files are located... it works. "
              Did you get this to work in a cluster using admin/managed servers, or just with a single server?
              -Greg
              Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
              www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
              "David Kostiew" <[email protected]> wrote in message news:[email protected]...
              Hi,
              I'm trying to stop the webserver from trying to recompile/check my jsp pages. I have set the pageCheckSeconds param to -1 but that doesn't seem to work. Looking at the weblogic.log file I get:
              [WebAppServletContext(601285,kcs,/kcs)] WorkflowServlet: init>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: init>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param verbose initialized to: true>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param packagePrefix initialized to: jsp_servlet>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param compilerclass initialized to: javac>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param srcCompiler initialized to weblogic.jspc>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param superclass initialized to weblogic.servlet.jsp.JspBase>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param workingDir initialized to: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param pageCheckSeconds initialized to: -1>
              [WebAppServletContext(601285,kcs,/kcs)] *.jsp: initialization complete>
              [WebAppServletContext(601285,kcs,/kcs)] Generated java file: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs\jsp_servlet\__index.java>
              If I take out the jsp class files from the war file and set the param workingDir (weblogic.xml) to the directory where the jsp class files are located... it works. But now I have a packaging problem that I can easily solve by keeping the jsp class files within the war file. As you can see from the log messages above, the pageCheckSeconds value is set to -1... yet the checking occurred anyway. Is there a way to specify the name of the war file that is located within an EAR file using the workingDir param?
              Thanks
              David
              [att1.html]
              

  • How do I update JSPs without having to restart WebLogic?

    How do I update JSPs without having to restart WebLogic? I have tried setting pageCheckSeconds to 0 in my weblogic.xml file. I have also tried setting Reload Period to 0 in the console. Please advise.
              

              Just bring up the Weblogic Console. Drill down to your webapp. De-select the Deploy
              option. Click on apply. Select the Deploy option and Click apply. Basically, Un-deploy
              and re-deploy your webapp.
              Later...
              - Wayne
              "cleve" <[email protected]> wrote:
              >which is here:
              >
              >http://e-docs.bea.com/wls/docs61////javadocs/weblogic/management/tools/WebAp
              >pComponentRefreshTool.html
              >
              >"Michael Young" <[email protected]> wrote in message
              >news:[email protected]..
              >> Try using the weblogic.refresh tool.
              >>
              >> regards,
              >> Michael
              >>
              >> Tony Nguyen wrote:
              >>
              >> > How do I update JSPs without having to restart WebLogic? I have tried
              >setting pageCheckSeconds to 0 in my weblogic.xml file. I have also tried
              >setting Reload Period to 0 in the console. Please advise.
              >>
              >> --
              >> Michael Young
              >> Developer Relations Engineer
              >> BEA Support
              >>
              >>
              >
              >
              

  • Book for servlet 2.4, jsp 2.0 & JSTL 1.1 ?

    but i am looking book covering the topic servlet 2.4 , jsp 2.0, JSTL 1.1 in detail because i am looking for in depth knowledge of all the topics (specially JSP, EL, JSTL, Custom Tags)

    I think the best source would be the specification. Seriously, they are really well written ( especially for JSTL ).
    regards,
    Tuan

  • How to use jstl in weblogic 8.1

    I tried to use JSTL in my jsp file and I add
              <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %> at the top line. But the server reported
              java.lang.NoClassDefFoundError: javax/servlet/jsp/el/VariableResolver
              how to solve this problem?

    WebLogic 8.1 supports JSP 1.2, which doesn't natively implement the JSTL or the expression language. If you download the Jakarta Taglibs implementation of the JSTL (for JSP 1.2, not JSP 2.0), then you can use the JSTL taglib as a normal taglib. Note that this doesn't give you the ability to use the other JSP 2.0 tag features, like using the expression language in body content.
              Make sure that you use the uri value specified in the tld that you're using. I believe the values are different between the JSP 1.2 and JSP 2.0 versions.

  • Using JSTL on Weblogic 8.1 SP2

              I'm trying to create a web app running on Weblogic 8.1 SP2 that uses JSTL tags.
              I've downloaded the Apache 1.0.5 Reference Implementation of the JSTL 1.0 spec,
              but I can't get the sample web-app (standard-examples.war) to work correctly.
              When I go to the "General Purpose Tag Examples" and try to view the Out example
              JSP, I get a large exception saying that java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException
              (full stack trace at bottom). This also happens when I try to view the JSP source
              and pretty much any other example. I found that the German example in "I18N &
              Formatting" works, but running the Italian example gives a new exception:
              Parsing of JSP File '/format/ItalianLocale.jsp' failed:
              /format/ItalianLocale.jsp(12): for tag 'message', property 'bundle' of tag handler
              class 'org.apache.taglibs.standard.tag.rt.fmt.MessageTag', the value must be a
              runtime expression "<%=...%>", since we cannot do an automatic conversion from
              "${itBundle}" to type 'javax.servlet.jsp.jstl.fmt.LocalizationContext' and there
              is no custom property editor for that type
              probably occurred due to an error in /format/ItalianLocale.jsp line 12:
              <fmt:message key="greetingMorning" bundle="${itBundle}"/>
              I can, however, get this to work on Tomcat 5.0. Has any else had this problem?
              Is there something that I'm doing incorrectly?
              Thanks in advance.
              -Kelvin
              ===========================================================
              java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException
                   at java.lang.Class.getDeclaredMethods0(Native Method)
                   at java.lang.Class.privateGetDeclaredMethods(Class.java:1627)
                   at java.lang.Class.getDeclaredMethods(Class.java:1114)
                   at java.beans.Introspector$1.run(Introspector.java:1103)
                   at java.security.AccessController.doPrivileged(Native Method)
                   at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:1101)
                   at java.beans.Introspector.getTargetMethodInfo(Introspector.java:966)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:370)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:207)
                   at java.beans.Introspector.(Introspector.java:351)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:207)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:193)
                   at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
                   at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
                   at weblogic.servlet.jsp.StandardTagLib.(StandardTagLib.java:292)
                   at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
                   at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
                   at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
                   at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
                   at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
                   at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
                   at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
                   at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
                   at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
                   at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
                   at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
                   at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
                   at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
                   at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:367)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:223)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:172)
                   at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:518)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:362)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
                   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
                   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
                   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

              I'm having the same problem, did you find a solution?
              "Kelvin" <[email protected]> wrote:
              >
              >I'm trying to create a web app running on Weblogic 8.1 SP2 that uses
              >JSTL tags.
              > I've downloaded the Apache 1.0.5 Reference Implementation of the JSTL
              >1.0 spec,
              >but I can't get the sample web-app (standard-examples.war) to work correctly.
              >
              >When I go to the "General Purpose Tag Examples" and try to view the Out
              >example
              >JSP, I get a large exception saying that java.lang.NoClassDefFoundError:
              >javax/servlet/jsp/el/ELException
              >(full stack trace at bottom). This also happens when I try to view the
              >JSP source
              >and pretty much any other example. I found that the German example in
              >"I18N &
              >Formatting" works, but running the Italian example gives a new exception:
              >
              >Parsing of JSP File '/format/ItalianLocale.jsp' failed:
              >--------------------------------------------------------------------------------
              > /format/ItalianLocale.jsp(12): for tag 'message', property 'bundle'
              >of tag handler
              >class 'org.apache.taglibs.standard.tag.rt.fmt.MessageTag', the value
              >must be a
              >runtime expression "<%=...%>", since we cannot do an automatic conversion
              >from
              >"${itBundle}" to type 'javax.servlet.jsp.jstl.fmt.LocalizationContext'
              >and there
              >is no custom property editor for that type
              >probably occurred due to an error in /format/ItalianLocale.jsp line 12:
              ><fmt:message key="greetingMorning" bundle="${itBundle}"/>
              >
              >
              >I can, however, get this to work on Tomcat 5.0. Has any else had this
              >problem?
              > Is there something that I'm doing incorrectly?
              >
              >
              >Thanks in advance.
              >-Kelvin
              >
              >===========================================================
              >java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException
              >     at java.lang.Class.getDeclaredMethods0(Native Method)
              >     at java.lang.Class.privateGetDeclaredMethods(Class.java:1627)
              >     at java.lang.Class.getDeclaredMethods(Class.java:1114)
              >     at java.beans.Introspector$1.run(Introspector.java:1103)
              >     at java.security.AccessController.doPrivileged(Native Method)
              >     at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:1101)
              >     at java.beans.Introspector.getTargetMethodInfo(Introspector.java:966)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:370)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:207)
              >     at java.beans.Introspector.(Introspector.java:351)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:207)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:193)
              >     at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
              >     at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
              >     at weblogic.servlet.jsp.StandardTagLib.(StandardTagLib.java:292)
              >     at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
              >     at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
              >     at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
              >     at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
              >     at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
              >     at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
              >     at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
              >     at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
              >     at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
              >     at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
              >     at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
              >     at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
              >     at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
              >     at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:367)
              >     at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:223)
              >     at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:172)
              >     at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:518)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:362)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
              >     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
              >     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              >     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              >     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
              >     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
              >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              

  • Problems with using JSTL with Weblogic 8.1 SP5 - Help!

    I keep getting the following error when trying to run my application using JSP tags under Weblogic 8.1 SP5 (using Jrockit in production mode):
    /searchinput.jsp(2): Error in using tag library uri='/WEB-INF/lib/regain-search.tld' prefix='search': cannot find tag class: 'net.sf.regain.ui.server.taglib.TagMsg'
    probably occurred due to an error in /searchinput.jsp line 2:
    <%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
    I have the following jar files in my /WEB-INF/lib directory:
    jakarta-regexp-1.4.jar
    jstl.jar
    standar.jar
    log4j-1.2.11.jar
    struts.jar
    lucene-1.4.3.jar
    jsp-api.jar
    and the regain-search.tld.
    I am using JSTL 1.0.6 (earliest version I could find of JSTL 1.0).
    The class files that the tld file is pointing to are in the WEB-INF/classes directory of the application (which is an exploded war file).
    Here is what I have as reference in my web.xml file:
    <taglib>
    <taglib-uri>/WEB-INF/lib/regain-search.tld</taglib-uri>
    <taglib-location>/WEB-INF/lib/regain-search.tld</taglib-location>
    </taglib>
    and it is referenced in searchinput.jsp as:
    <%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
    I've looked everyone on the Web trying to find an answer to this - but nothing I've tried has worked.
    This all works fine in Tomcat 5.0
    Please let me know what I'm doing wrong.
    Thanks in advance,
    Kelly

    I keep getting the following error when trying to run my application using JSP tags under Weblogic 8.1 SP5 (using Jrockit in production mode):
    /searchinput.jsp(2): Error in using tag library uri='/WEB-INF/lib/regain-search.tld' prefix='search': cannot find tag class: 'net.sf.regain.ui.server.taglib.TagMsg'
    probably occurred due to an error in /searchinput.jsp line 2:
    <%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
    I have the following jar files in my /WEB-INF/lib directory:
    jakarta-regexp-1.4.jar
    jstl.jar
    standar.jar
    log4j-1.2.11.jar
    struts.jar
    lucene-1.4.3.jar
    jsp-api.jar
    and the regain-search.tld.
    I am using JSTL 1.0.6 (earliest version I could find of JSTL 1.0).
    The class files that the tld file is pointing to are in the WEB-INF/classes directory of the application (which is an exploded war file).
    Here is what I have as reference in my web.xml file:
    <taglib>
    <taglib-uri>/WEB-INF/lib/regain-search.tld</taglib-uri>
    <taglib-location>/WEB-INF/lib/regain-search.tld</taglib-location>
    </taglib>
    and it is referenced in searchinput.jsp as:
    <%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
    I've looked everyone on the Web trying to find an answer to this - but nothing I've tried has worked.
    This all works fine in Tomcat 5.0
    Please let me know what I'm doing wrong.
    Thanks in advance,
    Kelly

  • JSTL and WebLogic

    How will I deploy JSTL on WebLogic11g? I want all the applications deployed on that server to be able to access JSTL 2.0
    Thanks

    I managed to get the JSTL deployed on my weblogic server. However when trying to use the tags in my JSP page, I come across the following error. My <c:out tag works fine. However the below code in the JP page fails with this error.
    Code
    <c:forEach var="i" begin="1" end="10">
    <c:out value="${11-i}" />
    </c:forEach>
    Error 500--Internal Server Error
    java.lang.NoSuchFieldError: deferredExpression
         at org.apache.taglibs.standard.tag.common.core.ForEachSupport.release(ForEachSupport.java:196)
         at jsp_servlet._fsmc.__map2._jsp__tag0(__map2.java:296)
         at jsp_servlet._fsmc.__map2._jspService(_map2.java:234)
         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:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Edited by: user5108636 on 7/04/2010 18:54
    Edited by: user5108636 on 7/04/2010 18:59

  • Jsp 1.2 tags in weblogic 5.1?

    Is there any patch to get JSP 1.2 tags to work in weblogic 5.1? I'm
              itching to play with the new standardized tag library under
              development thats been released on the Sun site. Unfortunately my
              company is using weblogic 5.1 and is not planning on moving anytime
              soon. What exactly about JSP 1.2 tags would not workn in the 5.1
              server?
              

    Mike,
              WLS 5.1 only supports JSP 1.1. There is no patch available to get JSP
              1.2 tags to work. WLS 6.1 includes some features for JSP 1.2. For
              specifics on what is supported see:
              http://e-docs.bea.com/wls/docs61/notes/new.html#1047732
              Regards,
              Velvet
              Mike Lomage wrote:
              > Is there any patch to get JSP 1.2 tags to work in weblogic 5.1? I'm
              > itching to play with the new standardized tag library under
              > development thats been released on the Sun site. Unfortunately my
              > company is using weblogic 5.1 and is not planning on moving anytime
              > soon. What exactly about JSP 1.2 tags would not workn in the 5.1
              > server?
              

  • Can't get JSP debugging to work with WebLogic 6.0 and Eclipse 2.1.1

    Is native JSP debugging supported in WebLogic 6.0? If so, what are
              the steps involved in getting it to work? I'm in debug mode and my
              servlets will catch at my breakpoints but the JSP pages' breakpoints
              are ignored. I am using compliance level 1.3 and a JRE 1.3. I tried
              to start WebLogic with the 1.4.2 JRE but I get an exception error on
              the WLS JDK name" field. What am I missing here?
              Thanks!
              

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

  • Problem compling JSP with struts tags on Weblogic 8.1

    I have deployed a web application in Weblogic 8.1. However, I am facing a problem while the JSPs are getting compiled. The JSPs ahve taglib declarations referring to Struts tag library files that are present in WEB-INF folder.
    Stacktrace:
    C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\myserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209: cannot resolve symbol
    probably occurred due to an error in /approve/approve_home.jsp line 53:
    <logic:notPresent name="<%=JobBean.ID%>" scope="request">
    C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\myserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209: cannot resolve symbol
    symbol : variable EVAL_BODY_BUFFERED
    location: interface javax.servlet.jsp.tagext.BodyTag
    if (_int0 == BodyTag.EVAL_BODY_BUFFERED) { //[ /approve/approve_home.jsp; Line: 53]
    I believe other people have also faced this issue with Weblogic8.1 and struts. Any solutions???
    Thx
    KP

    KP,
    Does this code run in the development environment but not in production? How
    was this code compiled?
    - john
    "KP" <[email protected]> wrote in message
    news:405b9b56$[email protected]..
    I have deployed a web application in Weblogic 8.1. However, I am facing aproblem while the JSPs are getting compiled. The JSPs ahve taglib
    declarations referring to Struts tag library files that are present in
    WEB-INF folder.
    Stacktrace:
    C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\m
    yserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209:
    cannot resolve symbol
    probably occurred due to an error in /approve/approve_home.jsp line 53:
    <logic:notPresent name="<%=JobBean.ID%>" scope="request">
    C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\m
    yserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209:
    cannot resolve symbol
    symbol : variable EVAL_BODY_BUFFERED
    location: interface javax.servlet.jsp.tagext.BodyTag
    if (_int0 == BodyTag.EVAL_BODY_BUFFERED) { //[/approve/approve_home.jsp; Line: 53]
    >
    I believe other people have also faced this issue with Weblogic8.1 andstruts. Any solutions???
    >
    Thx
    KP

  • Retaining of values in JSP while using JSTL

    Dear All,
    I have an application using the struts framework, wherein I am facing a problem.
    Here goes the problem " In my JSP's I have multiselect, the JSTL tags works fine when all the server side validations are done. But I get a problem when an error(server side validation error) occurs, I have to retain all the multiple values selected in the Multiselect box.
    Can anyone suggest me best way to retain the multiple values.
    E.g. My multiselect populates 5 values
    A
    B
    C
    D
    E
    As a end user I select "B, C,E", and a server side validation error occurs I have to keep the values "B, C, E" selected in the above list of 5 values using JSTL
    Thanking you in anticipation.
    regards,
    Mohan.

    Dear Friend,
    The control I am placing(multi select) has the data type in the form as String[],
    The validation error(server side) I was talking about is: I have 5 fields in JSP, in one of the 5 fields I have a title, which is unique in the database, if the end user enters an already existing title, then all the values previously (entered, selected) for rest of the controls should be retained and an error message from application resources is populated about the title duplication.
    Here I will show the entered values in text box and also the multi-selects, so using JSTL, I want a way out to retain the previously selected values....
    In my JSP for the control I say <input type="select" property="propertyname" multiple="true">
    of struts...
    Thank you
    Mohan.

  • Changes made in jsp pages not showing in weblogic 92

    Hi:
    I am using Weblogic 92.
    I ran an ant script and it copy the ear file
    to the following directory.
    C:\bea92\user_projects\domains\Inquiry\autodeploy
    This should autodeploy the application but it doesn't seemed to show the changes I made.
    I also copy the ear file to the following directory:
    C:\bea92\user_projects\applications\Inquiry
    and
    C:\bea92\user_projects\applications\Inquiry\autodeploy
    The worst part is even if I delete the ear files in the above directory and when I restarted weblogic 92, in the admin console it still shows it and when I tried to delete it, it says the ear file was deploy autodeploy and you must delete it manually something like that.
    But I already deleted it manually but it still shows in the weblogic console. This is very frustrating.
    In weblogic 8.1 I didn't use autodeploy and I don't have any of these type of problems!!
    I also noticed that in the directory:
    C:\bea92\user_projects\domains\Inquiry\servers\AdminServer\stage\_appsdir_inquiry_ear
    it contains an old ear file.
    What are the directory I have to updated exactly with the new ear files for the changes to show up in the application?
    Any help would be greatly appreciated.
    Yours,
    Frustrated
    Edited by jadeite100 at 03/22/2007 3:38 PM

    Hi, Shonda, I can find "Main Mode" for my Jdeveloper 9.0.5.0.0 at
    Tools -> Embedded Oc4j Server settings -> Global -> JSP Container.
    If you can not find this parameter as above, can you use the index search for "Jsp container" or full text search for "embedded oc4j"?
    Anyway, I believe there is way to confirm / change this parameter. At a last resort, you might search for files that contains "main_mode" or "main mode", case ignored, so as to get a clue where this parameter is stored.
    I have been using 9.0.3 oc4j for some time. If the main_mode is recompile, any change of my jsps is always reflected immediately.

Maybe you are looking for