Latest posts for the topic "Finding the ICEfaces roadmap, bug reports, and workarounds"

Finding the ICEfaces roadmap, bug reports, and workarounds

ken.fyten — GMT

There have been several posts recently asking about the ICEfaces roadmap, whether a particular bug or feature will be fixed soon, etc. I wanted to make everyone aware that the best place to get this type of information is from the ICEfaces JIRA issue tracker: http://jira.icefaces.org/ Using JIRA you can readily view the product roadmap in terms of which issues are scheduled for which upcoming releases (see "Roadmap" under the "Browse Project" menu). In addition, you can search to see if a bug or feature request you have is already present in the system. If not, you can create a new JIRA issue for it. If it is present, you can vote for it to indicate your personal priority for having the issue resolved. Going forward we will use community votes as one indicator of demand/need during roadmap planning. Please consult the JIRA early and often! :) Regards, Ken

Re:Finding the ICEfaces roadmap, bug reports, and workarounds

vivian — GMT

Hi, I want to find out if ICEFaces will have a wizard component soon. But I checked the URL you pointed to and it is hard to me to find the answer. So, any wizard support soon?

Re:Finding the ICEfaces roadmap, bug reports, and workarounds

mariuszs — GMT

vivian wrote:

Hi, I want to find out if ICEFaces will have a wizard component soon. But I checked the URL you pointed to and it is hard to me to find the answer. So, any wizard support soon?

If you are using Seam with ICEFaces, there is very easy to make wizard, and you dont need special component for this... (please look at conversation scope).

Re:Finding the ICEfaces roadmap, bug reports, and workarounds

philip.breau — GMT

Hi Vivian, As mariuszs mentioned, Seam has a pattern for creating wizards. We don't have a particular component for wizards, but you could create one very easily by using an ICEfaces panelStack component. You can stay on the same page, and change panels as the user continues through the wizard. You can keep beans in request scope, which will be maintained across partialSubmits while the user is continuing through the panes. Although this wouldn't take care of maintaining request state if the user refreshed the page. Otherwise, it gives you pretty much the same state management feature as Seam's conversation scope. Philip