GeeCON Prague 2014*
The moose likes JSF and the fly likes Javascript error when upgrading to tomahawk 1.1.3 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » JSF
Bookmark "Javascript error when upgrading to tomahawk 1.1.3" Watch "Javascript error when upgrading to tomahawk 1.1.3" New topic
Author

Javascript error when upgrading to tomahawk 1.1.3

Travis
Greenhorn

Joined: Nov 01, 2006
Posts: 6
When upgrading to tomahawk 1.1.3 from 1.1.1, I have an issue with the <t:inputCalendar> component. I am using the most up to date jars of myfaces 1.1.4. My environment is Websphere 6.

I don't get any errors in my console when I run my application, but I get javascript errors when the page with the inputcalendar loads. It says, 'org_apache_myfaces_PopupCalendar' is undefined.

I am not seeing any documentation about this issue.

If anyone could help me out with this issue, it would be greatly appreciated.

Thanks in advance,
Travis
Ali Gohar
Ranch Hand

Joined: Mar 18, 2004
Posts: 572
Can you post the code where you have used that control?
Travis
Greenhorn

Joined: Nov 01, 2006
Posts: 6
Here is the component code (resides inside a h:form tag)

<t:inputCalendar id="effectiveStartDate" value="#{addSkillBean.effectiveStartDate}" readonly="true" renderAsPopup="true" renderPopupButtonAsImage="true" styleClass="dateField" popupDateFormat="#{labels.datePattern}" title="Effective Start Date"></t:inputCalendar>

Extension filter setup in web.xml
<!-- Extensions Filter -->
<filter>
<filter-name>extensionsFilter</filter-name>
<filter-class>org.apache.myfaces.component.html.util.ExtensionsFilter</filter-class>
<init-param>
<param-name>uploadMaxFileSize</param-name>
<param-value>100m</param-value>
<description>Set the size limit for uploaded files.
Format: 10 - 10 bytes
10k - 10 KB
10m - 10 MB
1g - 1 GB
</description>
</init-param>
<init-param>
<param-name>uploadThresholdSize</param-name>
<param-value>100k</param-value>
<description>Set the threshold size - files
below this limit are stored in memory, files above
this limit are stored on disk.

Format: 10 - 10 bytes
10k - 10 KB
10m - 10 MB
1g - 1 GB
</description>
</init-param>
</filter>
<filter-mapping>
<filter-name>extensionsFilter</filter-name>
<url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>extensionsFilter</filter-name>
<url-pattern>*.jsf</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>extensionsFilter</filter-name>
<url-pattern>/faces/*</url-pattern>
</filter-mapping>

Thanks,
Travis
Ali Gohar
Ranch Hand

Joined: Mar 18, 2004
Posts: 572
Try this and check if it works

Travis
Greenhorn

Joined: Nov 01, 2006
Posts: 6
This inputDate component renders two input text boxes for day and year and renders a drop down for the months with the listed code you have posted (not a popup calendar). I am still using the tomahawk 1.1.3 version of the jar.

I would like to be able to continue using the inputCalendar component instead of changing to the inputDate component as it is used widely throughout my application. Is this a know bug with the 1.1.3?

Thanks for the replies.
Travis
Greenhorn

Joined: Nov 01, 2006
Posts: 6
Update:

I have set the ADD_RESOURCE_CLASS to streamingAddResource and it no longer gives me the javascript errors, but still isn't performing correctly. It does an inline popup instead of being on a div layer. On top of that, it also doesn't have the look and feel as it did before I upgrade to the 1.1.3 version of the tomahawk jar.

 
GeeCON Prague 2014
 
subject: Javascript error when upgrading to tomahawk 1.1.3