ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Your best bet is to take a look at the JSF Life cycle and implement the JSF PhaseListener interface. You can read more about this technique here:

Life cycle
http://www.ibm.com/developerworks/library/j-jsf2/

Phase Listener Example
http://www.jsftutorials.net/faces-config/phaseTracker.html

There is often a small detail that is over looked when using popups. The difference is mainly in the handling of visible and rendered attributes depending if the popup is modal of not.

When using non-modal popup you need to make sure that both the rendered and visible attributes are bound to the same boolean value. For example:

Code:

<ice:panelPopup 
             draggable="true"
             rendered="#{popup.showDraggablePanel}"
             visible="#{popup.showDraggablePanel}"
             style="z-index: 1000; top: 300px; left: 300px; 
                       position: absolute; width: 300px; height: 150px;">

For the modal popup you need to make sure that only the rendered attribute is bound and that the visible attribute is set to true.

<ice:panelPopup id="popupDiv"
rendered="true"
visible="#{popup.showModalPanel}"
modal="true"
style="z-index:1001; width: 300px; height:
150px; top:35%; left:35%;">

This is the first time I have heard of this problem. There might be something else happening on the second page.

Binding aren't necessary needed for most application. What are you using the binding for?

Adding redisplay="true" to inputSecret should do the trick. However this is a potential security risk as the password value will be in the rendered html. This is the main reason this feature is disabled by default.

The panelBoarder component will work for you along with <jsp:directive.include /> for your common header, menu and footer content. However if you can't get all of your layout configured with CSS you'll end up with template code in each JSP that uses the panelBoarder.

I would suggest you give Facelets another look as it can be a very powerful templating tool. The component showcase can be build via Facelets if you want to double check the environment and build settings. The showcase example isn't the best in showing how templates should and can be used.

Here is a good article that might help you get started with Facelets if you choose to give it another look.

http://www-128.ibm.com/developerworks/java/library/j-facelets/
http://www.ibm.com/developerworks/java/library/j-facelets2.html

From your logs it looks like everything started up correctly. This might seem strange but I've seen problems with putting a "Period" (.) in your web application name. You might want to try a application name with out the period in it.

You can also double check your hibernate configuration against http://facestutorials.icefaces.org/tutorial/hibernate-tutorial.html .

We are always trying to improve our error reporting in ICEfaces. Often times the stack trace that shows up in the browser is not as detailed as the one the is in the server logs.

The Facelets view handler offers improved error handling as well as many other enhancements. See the developers guide for more information on how to configure your application to use Facelets. (Getting started guide, chapter 3, step 6.

I'm assuming you're using commandButtons or outputLink to start the file download. Try adding target="blank" to get the new window to open rather then using the javascript new window function.

Also make sure that the first thing you set the content type on the servlet response object before you write anything else. This will insure the content-type header gets correctly set.

The EffectQueue class can be used to setup a multiple effects. Just add the effect you need and use it as the main effect in your JSP page.

The component showcase example was unfortunately only written to support two levels. It could be extended if you have the time. However if you don't want to re-invent the wheel you could try this component from apache, http://myfaces.apache.org/tomahawk/treeTable.html

There is information in our developers guide and release note on how to configure ICEfaces to work with the myfaces.

I suspect the commandLink action is causing the problem. Consider using an outputLink instead for the file download link. The browser will better be able to handle the redirect for the file and keep the existing page active.

Can you post an example of the JSPX code in question?

I don't see any problems with your your include. The problem is most likely related to the an incorrect path for the file include. You you enable log4j logging for your project and set the ICEfaces packages to "info" level you'll see an exception if the file is not included.

If your are using Facelets consider using:

Code:

<ui:include src="./userConfiguration.jspx" />

Try changing the extension of the Facelets include to point to the actual file name instead of the mapped name:

Code:

<ui:include src="inc.xhtml" />

Try creating a abstract class the captures your beans core functionality and defines the action method in question as abstract. Then create two new beans that extends the abstract class and implement the action method for the particular behavior . Introspection should take care of the rest.