Upgrade to JSTL 1.1.2

Hello,
I have upgraded my jstl and standard libs from 1.0.6 to 1.1.2 version.
Using 1.0.6 I had many "c_rt" tags into my jsp pages.
So I'd like to know if I can still use those tags, conserving the old c_rt include, or if I have to remove this include and replace all my c_rt tags with c tags (which would implie more work):
To be more explicit :
Can I have those includes (new one with old one):
<%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
<%@taglib uri="http://java.sun.com/jstl/core_rt" prefix="c_rt"%>
or should I only have the new one :
<%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
I think the the c_rt compatibility is assumed in 1.1.2 version but I'd like to have a confirmation from you.
Thank you for your answers.

From my understanding of the system it WILL work unchanged.
But to my mind it would be better if you replaced all the c_rt tags with c tags, because under JSTL1.1 the standard tag accepts both ${expr} and <%= expr %>
Surely it is relatively easy to do with a global search and replace?

Similar Messages

  • Upgrade to JSTL 1.2 and JSF 1.2

    I created a Portal project in weblogic workspace studio 1.1 (weblogic portal 10.2). The portal was created with the default facets. I did not add JSF facet etc. Now all I am trying to do is upgrade to JSTL 1.2 from the add/remove project facets page. But I dont see 1.2 option in the dropdown. I can see the JSTL library in the C:\bea\wlserver_10.0\common\deployable-libraries folder. But for some freaking reason I am not able to select it. I thrn went to Window-&gt;Preferences-&gt;Workshop-&gt;Downloadable Libraries-&gt;JSTL library and tried adding the new JSTL 1.2 library but neither do I see JSTL 1.2 option in the drop down to download from BEA website and nor can I pick up that library from the existing JSTL installation.
    Also having the same issue with JSF. I cannot pick JSF 1.2 (i downloaded the myfaces JSF 1.2 libraries from the apache myfaces site)
    Its frustrating because I dont want to put a hack (dont want change configarations files etc). No idea why it has to this hard. Can someone please help.

    I'm not sure I would call this a hack but this is what I ended up doing to up grade the JSF Facet...
    [t-697865]

  • Issues in using JSF UI:Tree tag

    Hi,
    I am trying to work with Tree Structure using JSF UI tags. In Studio Creator i just created a JSP page and designed a Tree with two nodes under it. This is what i have in the body of my jsp.
    <ui:body binding="#{Page1.body1}" id="body1" style="-rave-layout: grid">
    <ui:form binding="#{Page1.form1}" id="form1">
    <ui:tree binding="#{Page1.tree1}" id="tree1" style="left: 48px; top: 48px; position: absolute" text="L3">
    <ui:treeNode binding="#{Page1.treeNode1}" expanded="true" id="treeNode1" style="width: 408px" text="Tree Node 1">
    <f:facet name="image">
    <ui:image binding="#{Page1.image1}" icon="TREE_DOCUMENT" id="image1"/>
    </f:facet>
    </ui:treeNode>
    <ui:treeNode binding="#{Page1.treeNode2}" expanded="true" id="treeNode2" text="Tree Node 2">
    <f:facet name="image">
    <ui:image binding="#{Page1.image2}" icon="TREE_DOCUMENT" id="image2"/>
    </f:facet>
    </ui:treeNode>
    </ui:tree>
    </ui:form>
    </ui:body>
    But when i am trying to launch the jsp page from browser i am getting the below exception.
    com.sun.rave.web.ui.appbase.ApplicationException
    Caused by: java.lang.NullPointerException at java.io.File.(File.java:194) at com.sun.rave.web.ui.renderer.template.xml.XMLLayoutDefinitionManager.getLayoutDefinition(XMLLayoutDefinitionManager.java:142) at com.sun.rave.web.ui.component.TemplateComponentBase.getLayoutDefinition(TemplateComponentBase.java:150) at com.sun.rave.web.ui.renderer.template.TemplateRenderer.encodeBegin(TemplateRenderer.java:73) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:683)
    Any suggestion to solve this issue would be greatly helpful.

    Now with Unified EL - JSTL and JSF tags are supposed to work on one page.
    If you want to use Unified EL you need
    1) A container that is built on Servlet 2.5 / JSP 2.1 , and example of such a container is Tomcat 6.x
    2) Probably need to upgrade to JSTL 1.2 , and JSF 1.2
    3) If you're upgrading the container to Servlet 2.5 then web.xml should conform to Servlet 2.5 version.
    4) Use correct taglib URIs for JSTL 1.2 and JSF 1.2
    Read here: Summary of new features in JSP 2.1
    http://java.sun.com/developer/technicalArticles/J2EE/jsp_21/index.html
    JSP 2.1 Technology and JSF 1.2 Technology
    http://java.sun.com/developer/community/chat/JavaLive/2004/jl1207.html
    http://java.sun.com/products/jsp/index.jsp
    Message was edited by:
    appy77

  • Problem in using the f:attribute tag in JSF

    when I am trying to loop the JSF using the JSTL tag <c:foreach> I am getting the value as "Error:form_id0" .cold any one help me please

    Now with Unified EL - JSTL and JSF tags are supposed to work on one page.
    If you want to use Unified EL you need
    1) A container that is built on Servlet 2.5 / JSP 2.1 , and example of such a container is Tomcat 6.x
    2) Probably need to upgrade to JSTL 1.2 , and JSF 1.2
    3) If you're upgrading the container to Servlet 2.5 then web.xml should conform to Servlet 2.5 version.
    4) Use correct taglib URIs for JSTL 1.2 and JSF 1.2
    Read here: Summary of new features in JSP 2.1
    http://java.sun.com/developer/technicalArticles/J2EE/jsp_21/index.html
    JSP 2.1 Technology and JSF 1.2 Technology
    http://java.sun.com/developer/community/chat/JavaLive/2004/jl1207.html
    http://java.sun.com/products/jsp/index.jsp
    Message was edited by:
    appy77

  • Need Help In JSP template

    hey guys,
    i need jsp template tutorials or documentations ..... I read the tutorial from sun site, but i could not got clearly...So somebody suggest some web links or something else to help me ..
    Thanks & regards
    Satish
    [email protected]

    JSPs are best used for displaying UI - since you already have it working in the middle layer with Java classes you should keep it that way.
    If you want to pass data back and forth between the Java class that sends mail and the JSP use JavaBeans and make use of jsp:useBean tag and other related tags.
    Also so consider upgrading to JSTL 1.1 , instead of using scriptlets in JSPs.
    I don't know why you want to make it work in the JSP itself. If you still want it to work in the JSP the post more details about what error you're getting - look in the log files if necessary.

  • JSTL WLS 7 to WLS 8.1 Upgrade Issues

    We have a web app that currently runs on WLS 7. We have been asked to upgrade the app to WLS 8.1 recently. Most of the screen have ported fine, but there are a couple of screens that seem to be throwing fits. It could be a JDK/JRE issue, but here is the scenario
              jstl looks up a string variable property which is set to either "Y" or "N". Using WLS 7, it comes back as either "Y" or "N". But when I run the same code with WLS81, it comes back as "true" or "false".
              Looking at the property right before it returns always shows the correct value. When I look into the parameters and values, they seem to match the above statements as well (Y,N,true,false).
              Here is an interesting twist though. If I switch the JDK to 1.4 on WLS7, it also changes to "true" and "false". I have tried both sun and jrockit jvms to no avail.
              Has anyone seen this behavior?
              Thanks,
              Ashar

    That's almost what I said but not quite, you should not have any trouble, but this is the real world hence my suggestion to backup properly first.
    As for Yosemite I don't know the answer yet, I would expect it to be a no but we'll have to wait and see.

  • WSM Managed server starts in ADMIN Mode after upgrade to 11.1.1.7

    We have just upgraded our 11g SOA Cluster environment from 11.1.1.4 to 11.1.1.7. The issue is after the upgrade, our WSM servers are starting to ADMIN state with following error.
    <Sep 25, 2013 7:14:35 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@381802823[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
    at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
    Our cluster environment has one Admin Server, and two of each OSB, WSM and SOA managed servers. As our WSM servers are not coming up, we are not able to start our SOA servers too.
    Thank You

    Same issue here :-)), Just playing around with policies configuration, the server was running just fine, I wanted to check if the policies are applicable during runtime even the WSM managed server is down. After restart, it started in ADMIN mode, well the solution is straight. It is exactly telling that the dms application is missing the jstl library reference
    <Error> <Deployer> <iwpdcdevsoaa.iwater.ie> <WLS_WSM1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <bcfaf10ec8fbdfc2:-26d85d29:1429ffae24c:-8000-0000000000000003> <1385663491675> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@384044243[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
            at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
            at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >
    So search for "jstl" within the weblogic console in search bar, it is type of library, click on it and target it to the managed server where OWSM is running as weel. It was root cause in my case, somehow the library was not targeted to our WLS_WMS1 managed server. Now the server is back in RUNNING mode. Of course apply this in case of problem with SOA servers, target it to the cluster or exact nodes and it should work.
    Still I don't know how the issue has been crated, I don't think that somebody removed it from deployment. Rather I think that somebody was applying patch or some artifacts to OSB or SOA managed server and this library was required as well, but as soon as we have separated WSM cluster, it was maybe assuming that it is running within OSB or SOA clusters and therefore didn't target the WSM cluster automatically. But this is just the idea :-))
    Ladislav

  • Unable to load class from JSTL

    Hello. I am using JSTL 1.06 from Jakarta with Tomcat 4.1 on a MacOS X 10.3.9 server. I have a jsp that contains the following:
    <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
    <jsp:useBean id="validate" class="mypackage.ValidationBean" scope="request">
            <jsp:setProperty name="validate" property="*" />
    </jsp:useBean>
    <c:if test="${validate.valid == false}">
    The input is not valid.
    </c:if>In case it matters, my web.xml file starts out like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE web-app
        PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
        "http://java.sun.com/j2ee/dtds/web-app_2_3.dtd">I have placed jstl.jar and standard.jar in my webapp's WEB-INF/lib directory. However, when I try to load the page, I get this error message:
    org.apache.jasper.JasperException: /myjsp.jsp(60,0) Unable to load class if
    I know that many people have asked similar questions, but in each case, the response was to put jstl.jar and standard.jar in WEB-INF/lib and make sure that you're using the proper URI for the taglib, and I think I have done those things correctly. Any help would be greatly appreciated!

    Thanks for your response! In answer to your questions:
    The JRE is 1.4.2_09. I can't use 1.5 (5.0) without upgrading the OS.
    I haven't tried it on a PC. I might be able to, but it would take me some time to set everything up.
    What follows is taken from Tomcat/logs/localhost_log.2006-10-24.txt. If there is another log file I should be looking in, please let me know. Here is the full stack trace from the log:
    2006-10-24 16:58:40 Could not load TagLibraryValidator class org.apache.taglibs.standard.tlv.JstlCoreTLV: EXCEPTION: org.apache.taglibs.standard.tlv.JstlCoreTLV
    2006-10-24 16:58:40 Could not load TagExtraInfo class org.apache.taglibs.standard.tei.ImportTEI: org.apache.taglibs.standard.tei.ImportTEI
    2006-10-24 16:58:40 Could not load TagExtraInfo class org.apache.taglibs.standard.tei.ForEachTEI: org.apache.taglibs.standard.tei.ForEachTEI
    2006-10-24 16:58:40 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
    org.apache.jasper.JasperException: /myjsp.jsp(59,0) Unable to load class if
    at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94)
    at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:428)
    at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:219)
    at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:712)
    at org.apache.jasper.compiler.Parser.parseElements(Parser.java:804)
    at org.apache.jasper.compiler.Parser.parse(Parser.java:122)
    at org.apache.jasper.compiler.ParserController.parse(ParserController.java:199)
    at org.apache.jasper.compiler.ParserController.parse(ParserController.java:153)
    at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:227)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:369)
    at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:553)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
    at java.lang.Thread.run(Thread.java:552)

  • Trouble with c:out in jstl

    I am trying to use JSTL but it is not working very well.
    For instance, <c:out value="${4+4}"/> writes out 4+4
    instead of 8. Any idea what is going on?
    Message was edited by:
    tanitm

    One highly possible reason is that the EL is not evaluating.
    EL - expression language is whatever is inside ${.... }
    One of the main reasons why EL doesn't evaluate is if the configuration is not set up properly.
    You didn't mention which version of JSTL, I'm assuming JSTL 1.1
    For JSTL 1.1 , your Webserver (a.k.a container) should be based on Servlet 2.4 spec, check the following
    1) servlet.jar version should be 2.4 or higher - look for the version inside the Manifest.MF file inside the jar file
    2) web.xml should conform to the servlet 2.4 version, so inside your web.xml make sure you have the following exactly as it appears below:
    <web-app version="2.4"
             xmlns="http://java.sun.com/xml/ns/j2ee"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">3) Check your taglibrary directive inside the JSP file, it should be as follows if you are using JSTL 1.1
    <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>All of the above checks are for JSTL 1.1 , for previous versions of JSTL 1.0 the solution is different.
    If you are using JSTL 1.0 I recommend that you upgrade it to 1.1 as , 1.1 is significantly better.
    Message was edited by:
    appy77

  • SharedPageFlows / GlobalApp / Portal 9.2 Upgrade

    Hello all. I am in need of some assistance regarding the updated GlobalApp. We are working on upgrading an application from WebLogic Server/Portal 8.1 to WebLogic Server/Portal 9.2 In so doing, I've run across some behavior I don't understand and with which I was hoping someone could help me.
    In upgrading the project, the option to upgrade to Beehive controls was turned ON.
    We have a controller, called ShoppingCartController, which allows users to add/remove/update products in their shopping cart. This controller contains a reference to the global.Global class through Java Annotations. Here is the code:
    @Jpf.Controller( ... sharedFlowRefs = { @Jpf.SharedFlowRef(name = "sharedGlobalApp", type = global.Global.class) })
    public class ShoppingCartController extends PasswordResetPageFlowController implements LoginControllerClient {
    @Jpf.SharedFlowField(name = "sharedGlobalApp")
    private global.Global globalApp;
    I've defined Global.java as follows:
    @Jpf.Controller(catches = { @Jpf.Catch(...) }, messageBundles = { @Jpf.MessageBundle(...) })
    public class Global extends SharedFlowController {
    /** @common:control */
    @Control()
    private OrderService orders;
    public boolean isStoreOpen() {
    return this.orders.isStoreOpen();
    We have a class called OrderService and the corresponding OrderServiceImpl / OrderServiceBean classes. Generally this arrangement works very well.
    When viewing the shopping cart, however, I've found that the code makes multiple (> 10) requests to retreive an instance of the Global class, typically through the PageFlowUtils.getSharedFlow(String, HttpServletRequest, ServletContext) method. For the sake of completing the upgrade by March 11th, I've used the following to retrieve the instance from within a JSP page:
    <%
    global.Global global = (global.Global)PageFlowUtils.getSharedFlow(global.Global.class.getName(), request, request.getSession().getServletContext());
    pageContext.setAttribute("global", global);
    %>
    This makes the 'global' variable accessible from JSTL calls (side note: is this really the best way to make this accessible, since netui:getData is deprecated?) and works pretty good.
    When a user views the shopping cart, however, this works exactly 50% of the time. The first time through, the page renders correctly and the user experience is fine. The second time through, however, a NullPointerException is thrown. I've found that this happens when the ShoppingCartController, in the beforeAction() method, calls this.global.isStoreOpen() and is because the OrderService control is null.
    Further investigation lead me to find that at some point, and for a reason unknown to me, the JavaControlUtils.uninitJavaControls() method is being called. This method destroys all controls contained the current instance of the Global class stored in the session. This instance is the same instance that is inserted into the ShoppingCartController. Note that the instance of the Global class is not destroyed, only the controls contained within the Global class.
    So the instance of the global.Global referenced as a field in ShoppingCartController is still a valid instance. All of the control fields within global.Global are being set to null and hence the NPE. Perhaps this will help visualize:
    * User clicks 'View Shopping Cart'
    * ShoppingCartController.beforeAction is called
    * beforeAction calls this.global.isStoreOpen()
    * isStoreOpen() calls this.orders.isStoreOpen()
    * JSP is processed and rendered correctly
    * at some point, before the response is finalized, JavaControlUtils.uninitJavaControls() is called against the instance of global.Global referenced by ShoppingCartController and all controls referenced by global.Global are set to null (in our case there is only one control)
    * User clicks 'View Shopping Cart' again (or updates a quantity or their zip code, etc.)
    * ShoppingCartController.beforeAction is called
    * beforeAction calls this.global.isStoreOpen()
    * isStoreOpen() calls this.orders.isStoreOpen()
    * A NullPointerException is thrown because this.orders is null.
    Has anyone seen this? Are we not properly initializing our controls or referencing the global.Global class?
    Any help is greatly appreciated. I've searched Google and dev2dev with no luck. :(

    Hi,
    I am also having the same issue now. Do you have any solution? How did you get through that problem?
    Your help is highly appriciated.
    Somesh

  • EL expressions not evaluating after JSF 1.1 --- 1.2 upgrade.

    I am having a problem with EL expressions not evaluating in a JSF application that I just upgraded from Apache MyFaces JSF 1.1 to JSF-RI 1.2 and from Tomcat 5.5.25 to 6.0.26. After the upgrade the entire application is working fine except for EL expressions.
    I was wondering if I am missing a JAR file or something.
    Basically, I have prepopulated input text boxes that render the EL expression instead of its evaluated result. Example:
    INPUT [#{sessionBean.result}] instead of INPUT [tedsResult].
    Here are the JAR on my classpath:
    tomcat/lib:
    annotations-api.jar el-api-1.1.jar servlet-api.jar tomcat-i18n-fr.jar
    catalina-ant.jar jasper-el.jar sqljdbc.jar tomcat-i18n-ja.jar
    catalina-ha.jar jasper.jar tomcat-coyote.jar
    catalina.jar jasper-jdt.jar tomcat-dbcp.jar
    catalina-tribes.jar jsp-api.jar tomcat-i18n-es.jar
    and in my WEB-INF/lib:
    activation.jar hibernate-annotations.jar
    antlr-2.7.5H3.jar iText-2.1.3.jar
    asm-attrs.jar jakarta-oro.jar
    asm.jar jaxen-1.1-beta-8.jar
    avalon-framework-4.0.jar jaxrpc.jar
    avalon-framework-cvs-20020806.jar jdom.jar
    axis.jar jpdcFOP.jar
    batik.jar jpdc_web.jar
    cglib-2.1_3.jar jsf-api-1.2_12.jar
    commons-beanutils.jar jsf-impl-1.2_12.jar
    commons-codec.jar jstl.jar
    commons-collections.jar jta.jar
    commons-digester.jar jtds-1.2.jar
    commons-discovery.jar log4j-1.2.13.jar
    commons-el.jar logkit-1.0.jar
    commons-fileupload-1.2.jar mail.jar
    commons-io-1.3.1.jar openmap.jar
    commons-lang-2.3.jar saaj.jar
    commons-logging.jar standard.jar
    commons-logging-optional.jar tomahawk.jar
    cos.jar velocity-1.4.jar
    CVS velocity-tools-generic-1.1.jar
    dom4j-1.6.1.jar
    el-impl-1.1.jar versioncheck.jar
    ehcache-1.1.jar wsdl4j-1.5.1.jar
    ejb3-persistence.jar xalan.jar
    fop.jar xercesImpl.jar
    hibernate3.jar xmlParserAPIs.jar
    Any ideas what might be causing this problem? Thanks in advance for your help.
    Edited by: tsteiner61 on Apr 14, 2010 11:05 AM

    Hello tsteiner61,
    Did you find a solution for your problem? I am asking because I have to solve a somewhat similar problem. Our system admin updated Tomcat from version 6.0.20 to 6.0.26 and now my JSF application won’t evaluate EL expressions either.
    I was using “Mojarra JSF API Implementation 1.2_09-b02-FCS”. Trying “Mojarra JSF API Implementation 2.0.2-FCS” I get the following error:
    java.lang.UnsupportedOperationException
         javax.faces.context.ExternalContext.getResponseOutputWriter(ExternalContext.java:1228)
         com.sun.faces.application.view.JspViewHandlingStrategy.renderView(JspViewHandlingStrategy.java:182)
         com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126)
         org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:101)
         org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:197)
         javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:273)
         org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:176)
         com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127)
         com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
         com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:313)
    I am grateful for helpful advice.

  • Removing NetUI Facets and Upgrading JSF

    Even though 11g has promoted the use of JSF and talked of deprecating the NetUI, the facets and frameworks for 10gR3 are littered with NetUI dependencies.
    Creating a Web Portal Project gives you the capabilities to use JSF 1.2, but doing this requires you to select JSTL 1.2 and Dynamic Web Modules 2.5, but deselect WebLogic Control Extensions, Beehive NetUI, Beehive Controls, Portal Customizations Framework, Portal Framework, Portal Visitor Tools, and WSRP Producer. Not sure why upgrading to the newer (obviously not the newest version of the API), requires removing all these dependent frameworks.
    How will disabling all these project facets effect my Portal project? Are the specific things that I will not be able to take advantage of?
    It just doesn't make sense to use a product like WebLogic Portal 10gR3 (released within this year) and then downgrade JSF to version 1.1 just so I can use NetUI...that sounds totally backward thinking.
    Thanks...jay

    The forthcoming 11g version of the WLP product will include better support for JSF 1.2 in portal web projects, and remove the hard dependency on Beehive Netui and Controls.
    In WLP 10gR3 (10.3.0), you can use JSF 1.2 -- it just requires a bit of manual setup. Please see http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf. There are instructions (Section 4.4) on how to setup your project in Workshop to utilize JSF 1.2 in a portal-enabled web project.
    Greg

  • JSF and JSTL 1.2...please help, i`m going nuts

    Hey guys,
    This is driving me up the wall. I`m running glassfish v2 b19 (i havent upgraded, because this one works for me).
    But i have a problem using jstl in my jsf app. i`m trying to do the following :
                                                    <c:choose>
                                                        <c:when test="#{currentRow.value['dboSTANDBY_LOG.STANDBY_LOG_TYPE'] eq 'server'}">
                                                            <webuijsf:tableColumn binding="#{standby$Standby_Log.tableColumn19}" headerText="NAME"
                                                                id="tableColumn19" sort="dboSTANDBY_LOG.SBYN_HOST_NAME" width="40">
                                                                <webuijsf:staticText binding="#{standby$Standby_Log.staticText20}" id="staticText20" text="#{currentRow.value['dboSTANDBY_LOG.SBYN_HOST_NAME']}"/>
                                                            </webuijsf:tableColumn>
                                                        </c:when>
                                                        <c:otherwise>
                                                            <webuijsf:tableColumn binding="#{standby$Standby_Log.tableColumn17}" headerText="NAME"
                                                                id="tableColumn17" sort="dboSTANDBY_LOG.APPL_SYSTEMS_PROP_INNUMBER" width="40">
                                                                <webuijsf:staticText binding="#{standby$Standby_Log.staticText18}" id="staticText18" text="#{currentRow.value['dboSTANDBY_LOG.APPL_SYSTEMS_PROP_INNUMBER']}"/>
                                                            </webuijsf:tableColumn>
                                                        </c:otherwise>
                                                    </c:choose>
    but the app server fails on building the page saying :
    According to the TLD, the attribute test is not a deferred-value or deferred-method, but the specified value contains a #-expression
    Now as far as i now, JSTL 1.2 should be included in J5EE, which is in glassfish already, correct?
    and JSTL 1.2 supports using deferred expressions, correct?
    So why for the love of my sanity is this not working?
    aaaaaa.
    Thanks
    D

    I haven't actually used/tried this myself, and I am not a JSF expert, this error looks similar to the error message attribute xxx does not support runtime expressions.
    I think you are reading the error message wrong.
    You have supplied a deferred expression. No question of that.
    I think the error is saying that the 'test' attribute of the <c:when> tag does not support deferred evaluation. - ie you cant use #{expr} with the <c:when> tag.
    According to the JSTL1.2 spec, it seems that "deferred expressions" are only supported by the looping tags (<c:forEach> and <c:forTokens>) and the <c:set> tag.
    I think the JSF equivalent would be the rendered attribute. Can you use the rendered attribute with the webuijsf:tablecolumn tag? Or another JSF container type tag?

  • Can I use jstl1.0 uri with jstl 1.1.2 libraries

    The application has several wars some with 2.3 and some with 2.4 web.xml
    But all the apps consistently use the 1.1 uri ie., the one WITH "jsp" in it.
    So the two part question is: does the web.xml declared specification have any effect on which taglib it picks up ?
    and are the 1.1.2 tag libs compatible with both jstl 1.0 and jstl.1.1.2 uri s ?

    No..Ideally not.
    Due to backward compatibility most of the Application Servers including WebLogic provides us an option to use older web.xml which uses DTDs as well...
    But this is not a good practice ....to use Older DDs inside our application ..it has many loses So it is always better to convert those DDs according to the version of Server which we are using.
    It is more simpler with WebLogic because WebLogic provides a very useful tool "weblogic.DDConverter" to convert/upgrade these DDs in seconds according to the current version of WebLogic which u are using...For more details on this Please refer to : http://weblogic-wonders.com/weblogic/2010/08/26/weblogic-ddconverter-to-generate-latest-dds/
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic/miscellaneous/  (Middleware Wonders Are Here)

  • JSTL can't resolve

    when run the jsp file,there is error appear
    org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application
         at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94)
         at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:365)
         at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:151)
         at org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:343)
         at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:170)
         at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:456)
         at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:517)
         at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1567)
         at org.apache.jasper.compiler.Parser.parse(Parser.java:174)
         at org.apache.jasper.compiler.ParserController.parse(ParserController.java:254)
         at org.apache.jasper.compiler.ParserController.parse(ParserController.java:154)
         at org.apache.jasper.compiler.ParserController.parse(ParserController.java:140)
         at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:250)
         at org.apache.jasper.compiler.Compiler.compile(Compiler.java:458)
         at org.apache.jasper.compiler.Compiler.compile(Compiler.java:444)
         at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:603)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:300)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:286)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:974)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:205)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:974)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:177)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:974)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:562)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:974)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:203)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:637)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:484)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:568)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:631)
         at java.lang.Thread.run(Thread.java:534)

    you shouldn't need to specify the taglib stuff in
    web.xml, but you do need to make sure the URI matches
    the version of the JSTL you are using.
    For JSTL 1.0 (Tomcat <5), you would use the URI you
    have (http://java.sun.com/jsp/jstl/core), but for JSTL
    1.1 (Tomcat 5+), use http://java.sun.com/jstl/core
    instead.
    that should do it.....er... you have those URIs around the wrong way:
    1.0 = http://java.sun.com/jstl/core (JSP1.2)
    1.1 = http://java.sun.com/jsp/jstl/core (JSP2.0 container = Tomcat 5)
    When it was upgraded to 1.1 it was more closely integrated with JSP - and is actually part of the JSP2.0 spec. Hence the addition of the /jsp/ to the path.
    You do have standard.jar and jstl.jar sitting in your web-inf/lib directory don't you?
    Cheers,
    evnafets

Maybe you are looking for

  • Creative MediaSource can't seem to see audio C

    Thank you in advance and I apologize if there's a solution posted somewhere that I couldn't find. I tried. I have a Nomad Jukebox Zen Extra that I bought a year or so ago. Works great, I love it. I've always used the software that came with it, Creat

  • Link with ITPC protocol doesn't work

    My link to xml feed to my podcast doesn't work anymore on my ipod touch (3.1.2) or iphone (3.1.3). The link work just perfect on my computer (Windows XP) and open itunes normaly The ipod touch and iphone just say that the page can't be open because t

  • TS4009 How do I find documents in iCloud?

    Have set up auto backup from my iPad to the iCloud. However, where are the images/documents once they're uploaded to iCloud? I'd like to share a video but now can't find it.

  • Importing animation for best quality

    Hi. I'm preparing a 15' video (dvNTSC standard) to be burned to a DVD and played on tv monitors at an awards ceremony for my company. The first 6" or so will be an animated sequence which I have created on an older mac running OS 9.22, using Carrara

  • OS X Yosemite 10.10.1 and Microsoft Word: Mac 2008

    I installed OS X Yosemite 10.10.1 and am currently having troubles with Microsoft Word: Mac 2008.  I cannot type into documents that I open.  Strangely enough, I can copy into documents, but unfortunately, I can do nothing to edit open documents sinc