WebSphere Application Server 9中Tomahawk2 PopupCalendar资源加载异常求助

Hey there! No worries at all—we all start somewhere, and your question is clear enough to help troubleshoot this issue. Let's break down what might be going wrong with your PopupCalendar resource loading in the Tomahawk2 + JSF 2 + WAS 9 setup:

1. 检查ExtensionFilter的配置完整性 #

First, make sure your ExtensionFilter is fully set up in web.xml—missing initialization parameters or incorrect mappings often throw off resource routing:

<filter>
    <filter-name>MyFaces Extension Filter</filter-name>
    <filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
    <init-param>
        <param-name>mappings</param-name>
        <param-value>*.jsf;*.faces;*.xhtml</param-value>
    </init-param>
    <init-param>
        <param-name>extensionResourcePath</param-name>
        <param-value>/faces/myExtensionResource/*</param-value>
    </init-param>
</filter>
<filter-mapping>
    <filter-name>MyFaces Extension Filter</filter-name>
    <url-pattern>/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>FORWARD</dispatcher>
</filter-mapping>

Double-check that the extensionResourcePath matches exactly what you configured—typos here are a super common culprit.

2. 验证库的完整性与版本兼容性 #

Ensure you have all required Tomahawk2 JARs in your classpath (especially tomahawk2-core.jar and its dependent MyFaces libraries). Also confirm your Tomahawk2 version is fully compatible with JSF 2.x and WAS 9—some older builds clash with WAS's built-in JSF implementation.

Try setting your application's classloader policy to PARENT_LAST in WAS admin console. This prioritizes your app's libraries over the server's default ones, avoiding conflicts that might force resource requests to fall back to javax.faces.resource.

3. 检查PopupCalendar组件的渲染配置 #

Make sure you're using the correct Tomahawk namespace in your XHTML:

xmlns:t="http://myfaces.apache.org/tomahawk"

And that your PopupCalendar tag is properly declared:

<t:inputPopupCalendar id="calendar" value="#{bean.date}" />

If you've added custom renderers, double-check they aren't overriding the default HtmlCalendarRenderer from Tomahawk.

4. 排查WAS 9的资源处理限制 #

WAS 9 has strict resource rules—confirm your app's context root is correctly set to /DERO_WEB (as seen in your missing link path). Also, check if security constraints in web.xml are blocking access to the myFacesExtensionResource path.

To get more visibility into what's happening, enable debug logging for MyFaces: add these lines to your logging.properties or WAS's logging configuration:

org.apache.myfaces.renderkit.html.util.level = FINE
org.apache.myfaces.webapp.filter.ExtensionsFilter.level = FINE

This will trace exactly where resource requests are being routed, helping you pinpoint why it's falling back to the wrong resource path.

内容的提问来源于stack exchange，提问作者Manali