| Author |
Message |
|
|
|
This should help explain JSF value vs component binding: http://download.oracle.com/javaee/1.4/tutorial/doc/JSFIntro8.html
|
 |
|
|
You can find information on ICEfaces 1.x compatibility here: http://wiki.icefaces.org/display/ICE/ICEfaces+1.x+Compatibility
Porting
* The com.icesoft.faces.context.DisposableBean class is no longer available. Instead, use the JSF2 @PostConstruct and @PreDestroy annotations on methods that you would like called after your bean has been constructed and before it goes out of scope.
|
 |
|
|
Hi,
It would be quite a challenge to create a sample that uses all 2.0 features.
Have you had a look at our tutorials here: http://www.icefaces.org/main/resources/tutorials.iface or http://wiki.icefaces.org/display/ICE/Tutorials.
Our 2.0 documentation: http://wiki.icefaces.org/display/ICE/ICEfaces+2+Documentation
You could join a webinar: http://www.icefaces.org/main/resources/upcoming-webinars.iface
Or watch an introduction to ICEfaces 2.0 on youTube: http://www.youtube.com/watch?v=lwOcfdx2XrM
We hope this helps get you started :)
Thanks,
Tyler
Product Support
ICEsoft Technologies Inc.
|
 |
|
|
Hi,
It appears as though the JSF selectItem tag is unable to persist an Integer value and does a toString which explains why the value is returned as a String. The solution is to add a JSF converter which converts the string value to an Integer.
Tyler
|
 |
|
|
Hi,
We would be more than happy to assist you with questions relating to our Enterprise Edition composite components via an ICEfaces support subscription. Please feel free to contact us at product.support@icesoft.com should you require any additional information.
Thanks,
Tyler Johnson
Product Support
ICEsoft Technologies
|
 |
|
|
Hi,
The ICEfaces EE Standard, Professional and Premium support packages include access to ICEpack which contains a how-to guide on configuring JMeter load tests. Correctly configuring your load testing scripts is extremely important when wanting to assess the scalability of your application so we strongly recommend reviewing the benefits of EE and our support packages.
Thanks,
Tyler
Product Support
ICEsoft Technologies
|
 |
|
|
Hi Rajeev,
The partialSubmit attribute essentially disables the "required" attribute on all input components, except the one who called the partialSubmit. All of the values get submitted in all cases. ValueChangeListeners being inadvertently fired is often due to how you initialize the values in your backing bean. For example, when you submit a form (via partial submit), any empty inputText/select components that have not been initialized will have their default values changed to the empty string (ignoring conversion and some validation issues) and will cause a ValueChangeEvent to be fired. The solution to this problem is usually to assign a default value into the bean.
Best Regards,
Tyler
|
 |
|
|
We have identified the issue in Jira 5151. We are in the process of investigating a fix.
Tyler
|
 |
|
|
We have identified the issue in Jira 5151. We are in the process of investigating a fix.
Tyler
|
 |
|
|
ICE-5062 is now fixed.
Tyler
|
 |
|
|
Hi,
Firebug and certain Download Managers may interfere with the file transfer.
Can you disable these and try downloading again?
Thanks,
Product Support
ICEsoft Technologies Inc.
|
 |
|
|
We think we have fixed the issue. Can you try downloading again?
Thanks,
Tyler
|
 |
|
|
Hi,
Have you had a look at our deployment guidelines for OC4J?
http://support.icesoft.com/jive/entry.jspa?entryID=752&categoryID=80
Thanks,
Tyler
|
 |
|
|
Hi,
A test case would definitely help us correctly diagnose the issue. Would it be possible to send an example based on our SWF-Booking-Example that illustrates non-flow pages?
Thanks,
Tyler
Product Support
ICEsoft Technologies
|
 |
|
|
Hi Rainer,
Both Jira's have been resolved and will be included in ICEfaces 1.8.1.
Thanks,
Tyler
|
 |
|
|