如何在 Weblogic 10.3.x 上利用 EL 2.2 功能？

发布于 2024-12-27 02:37:19 字数 134 浏览 1 评论 0原文

我安装了Weblogic 10.3.5。我在服务器上部署了带有 JSF 2.0 和 JSTL 1.2 的 WAR。但我也需要 EL 2.2 功能。我需要什么 JAR？如果有人能从头开始向我指出分步指南，那就太好了，因为我已经尝试设置了几个小时但没有成功。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

姐不稀罕 2025-01-03 02:37:19

最简单的是删除 jboss-el.jar，这是一个 EL 2.1 兼容实现，提供相同的功能EL 2.2 中的功能， /WEB-INF/lib 并告诉 JSF 实现改用该 EL 实现。如何做到这一点取决于所使用的 JSF 实现。对于 Mojarra，您需要将以下上下文参数添加到 web.xml 中：

<context-param>     
    <param-name>com.sun.faces.expressionFactory</param-name>
    <param-value>org.jboss.el.ExpressionFactoryImpl</param-value>   
</context-param>

对于 MyFaces，它是以下上下文参数：

<context-param>     
    <param-name>org.apache.myfaces.EXPRESSION_FACTORY</param-name>
    <param-value>org.jboss.el.ExpressionFactoryImpl</param-value>   
</context-param>

另请参阅：

在 EL 中调用直接方法或带有参数/变量/参数的方法

Easiest is to drop jboss-el.jar, which is an EL 2.1 compatible implementation offering the same features as EL 2.2, in /WEB-INF/lib and tell the JSF implementation to use that EL implementation instead. How to do that depends on the JSF implementation being used. In case of Mojarra, you need to add the following context parameter to the web.xml:

<context-param>     
    <param-name>com.sun.faces.expressionFactory</param-name>
    <param-value>org.jboss.el.ExpressionFactoryImpl</param-value>   
</context-param>

And in case of MyFaces, it's the following context parameter:

<context-param>     
    <param-name>org.apache.myfaces.EXPRESSION_FACTORY</param-name>
    <param-value>org.jboss.el.ExpressionFactoryImpl</param-value>   
</context-param>

执行此操作后，您通常需要向 web.xml 添加一个上下文参数，以表示要为新版本加载的类EL 实现就像 BalusC 的答案一样。然而，Weblogic 似乎并不关心这一点，它的类加载器有自己的方式。您需要在 weblogic.xml 中指定，以优先加载 WEB-INF/lib 中的 EL 类。这将允许您加载 Glassfish 实现来代替与 WebLogic 捆绑在一起的旧 EL 实现。

 <container-descriptor>
    <prefer-application-packages>
     <package-name>com.sun.el.*</package-name>
     <package-name>javax.el.*</package-name>
  </prefer-application-packages>
</container-descriptor>

I feel that the accepted answer may or may not work for every situation, and of course the hook is that you will be stuck to a single JBoss release of EL without any of the support of continuing bug fixes in future patch releases of a proper 2.2 implementation.

Ultimately here is what worked for me on a WebLogic 10.3.6 server.

I downloaded the EL 2.2 API and Implementation jars from Glassfish and included those in the WEB-INF/lib folder of my web application.

el-api-2.2.jar
el-impl-2.2.0-SNAPSHOT.jar

After doing this you would normally need to add a context parameter to web.xml to signify the class to load for the new EL implementation like in BalusC's answer. Weblogic doesn't seem to care about this however, its classloader has its own way of things. You need to specify in your weblogic.xml to give preferential class loading to the EL classes in WEB-INF/lib. This will allow your Glassfish implementation to be loaded in place of the older EL implementation bundled with WebLogic.

 <container-descriptor>
    <prefer-application-packages>
     <package-name>com.sun.el.*</package-name>
     <package-name>javax.el.*</package-name>
  </prefer-application-packages>
</container-descriptor>

回复收藏 0 原文