Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: EE-2.0.0
-
Fix Version/s: EE-3.0.0.GA
-
Component/s: Core Extensions
-
Labels:None
-
Environment:ICEfaces 2 EE Liferay
-
Workaround Exists:Yes
-
Workaround Description:Do not include the Core Extensions library when running in a portlet environment.
Description
During testing of the component-showcase-portlets.war on Liferay, the behaviour of a couple of the portlet examples is impacted when the core extensions (icefaces-ee-ext.jar) is included with the application:
Buttons and Links: First value is remembered.
- Type something into the inputText box and click one of the submit options
- Click the Reset button. Value is not reset to being empty.
- Type a new value into the inputText box and click one of the submit options
- Click the Reset button. Value is reset to the first value that was entered rather than being empty.
AutoComplete: First entry doesn't work.
- Type a single letter into the first autocomplete box. The drop down list of choices is not displayed.
- Type another character, the drop downs should begin to work normally.
These problems do not manifest when running the Component Showcase in non-portlet mode and they also go away when the icefaces-ee-ext.jar is removed from the deployed application.
Buttons and Links: First value is remembered.
- Type something into the inputText box and click one of the submit options
- Click the Reset button. Value is not reset to being empty.
- Type a new value into the inputText box and click one of the submit options
- Click the Reset button. Value is reset to the first value that was entered rather than being empty.
AutoComplete: First entry doesn't work.
- Type a single letter into the first autocomplete box. The drop down list of choices is not displayed.
- Type another character, the drop downs should begin to work normally.
These problems do not manifest when running the Component Showcase in non-portlet mode and they also go away when the icefaces-ee-ext.jar is removed from the deployed application.
More serious variant of this problem now encountered:
http://jira.icefaces.org/browse/ICE-7266