ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Thanks. That will be a feature.

I am running on 1.6.2 using Facelets and I would like to have a RowSelector, that when the row is selected, navigates to a new page.

I have attempted doing this with the selectionAction. I have set a breakpoint in my debugger and I find that the method that returns the action is called but the page does not display.

I have included an ice:messages in the form and I do not seem to be getting any validation messages.

Another thing that appears odd to me is that the selectionListener is fired before the selectionAction. I thought it would be the other way around.

Can anyone tell me if the selectionAction should be able to do what I am trying to do? If not do you have any suggestions on how to get this behavior?

I changed the id in the tree.jspx. Unfortunately it did not solve the problem. I am really puzzled on this one. Is there another copy of the war file that I could try?

I ran the debug and went through the init() method on the bean (actually I went through it several times since it is instantiated numerous times) and none of them failed.

I am having trouble understanding the error message that I was getting in the stack trace. The error says "javax.servlet.jsp.JspException: Error getting property 'componentType' from bean of type com.icesoft.icefaces.samples.showcase.navigation.PageContentBean ".

There is no property of componentType in the PageContentBean. The only componentType that I could find was down in the TreeBean. I never get to the contructor of the TreeBean. It kind of looks like something "upstream" is stopping the creation before it finishes but must be eating the error.

I think the resources are there. I have attached a screen image showing the source folders from this project.

I have finished building a couple of the tutorials from the samples directory and have also built the tutorial for Facelets (timezone7). All of these work correctly.

I would be more comfortable getting the showcase to work since I would be running most of the component suite.

In the past I have ran and developed an application using the 1.5.x release of Icefaces using RAD 6 & 7 and deploying on WebSphere 6.0.

I am now testing the 1.6.0 release of IceFaces and seem to have a problem running the component-showcase. I was able to import the component-showcase.war file in from ICEfaces-1.6.0-bin distribution samples directory. RAD 7 compiled the classes and all of the JSP's and classes compiled cleanly.

The server starts but when I run the application I get the stack trace that I have included below. Using the debugger I find where many of the beans are instantiated but I have not been able to trace the hierarchy enough to find where the problem might be happening. Can someone please let me know of any tips I might use to get this to run?

Stack Trace:

javax.servlet.jsp.JspException: Error getting property 'componentType' from bean of type com.icesoft.icefaces.samples.showcase.navigation.PageContentBean
at com.icesoft.faces.component.OutputTextTag.doStartTag(OutputTextTag.java:339)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:162)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.executeJspLifecycle(Parser.java:186)
at com.icesoft.faces.webapp.parser.Parser.parse(Parser.java:134)
at com.icesoft.faces.application.D2DViewHandler.renderResponse(D2DViewHandler.java:557)
at com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:154)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:239)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118)
at com.icesoft.faces.webapp.http.core.PageServer$1.respond(PageServer.java:26)
at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:125)
at com.icesoft.faces.webapp.http.core.PageServer.service(PageServer.java:31)
at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
at com.icesoft.faces.webapp.http.servlet.SingleViewServlet.service(SingleViewServlet.java:45)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:334)
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:520)
at com.ibm._jsp._index._jspService(_index.java:66)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:254)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:334)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:503)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:89)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)

I have also been struggling with this topic. I have been trying to catch "500" errors in addition to the ones you have listed and have not been able to get the system to redirect to the error page.

I get either a hour glass, a "Session Expired" or a "Connection Lost" message.

Thanks. Unfortunately, my customer wants the scrollable list so I have changed to refresh the page and the response is fairly consistent.

I am still having a problem with the BlockingResponseState overflow. I noticed that the problem is fixed in 1.5.4 (JIRA issue ICE-1278). Is there a workaround for this or do I have to wait for 1.5.4? When will 1.5.4 be released?

Thanks again.

I have a fairly large datatable (500 rows X 12 columns). The datatable is set up as scrollable. The initial rendering of the datatable takes 2 - 5 seconds which is not too bad.

The table can also be sorted using the commandSortHeader feature. When I sort the data it takes from 30 - 40 seconds to repaint the datatable. The CPU is pegged on the client while it changes the data in all the rows.

I can understand how this might happen as the client is determining what data has changed. Has anyone found a way to make the control simply repaint the component rather than trying to change all the data a row at a time?

As you probably have discovered, the header is rendered as a separate table from the scrollable body. I think that if your data is highly variable in the number of characters in a column it becomes increasingly difficult to get the data table to line up with the header table.

I was able to get the two columns to line up closer but I did not get them to line up perfectly. Also I was not able to get rid of the cellspacing or padding between the cells.

I finally gave up and went back to the paginator.

We have successfully nested two levels of datatables. That is, a dataTable within a dataTable. We have now attempting to nest a third level dataTable. The first time the three level dataTables are rendered correctly. However when another collection of objects are selected, the first two levels of dataTables are refreshed but the third level's values do not change.

Has anyone built a dataTable with three levels and gotten it to work? We are trying to determine if it is a problem with our code or if we need to try a different approach.

The definition for the datatable looks like the following:

Code:

 <ice:dataTable id="allItemsTable" cellpadding="0" cellspacing="0"
     value="#{lineItemsAction.lineItems}" var="detail"
     columnClasses="colCenter, colCenter, colLeft, colCenter, colCenter, colRight, colRight, colRight"
     columnWidths="50px,75px,300px,90px,75px,90px,90px,90px"
     scrollable="true" scrollHeight="400px">

I am beginning to think that some of my problem is the use of the standard royale.css file that I am including in the page. I have created a hierarchy of the standard css file, followed by a site specific css file, following by a page specific css file.

In the showcase demo which looks close to what I am trying to get to, it looks like you have only one style sheet. It does not reference the "standard" icefaces style sheet. If that is the case where does the showcase pick up the style for elements such as iceTblHeader?

I have attached an .gif file that shows the cellspacing that I am getting in my application.

Thanks

I added the new 1.5 scrollable feature to a datatable that I had working and formatted. After I have added it, the table now seems to have a cellspacing in both the header and body of the datatable. I have put in cellspacing="0" but it seems to have no effect.

Also I am having a great deal of trouble getting the header to line up with the body of the table.

Does anyone have any ideas?

Thanks Philip for your help and prompt replies. I will make the changes that you outlined above.

However I am still concerned about what is going on and the intermittent nature of this problem. Like I said the server is now coming up and running as it has since we started our development. My fear is that we will have the problem in the future when the application is in production.

Since the application is behaving as expected, I just went into the logs and noticed that I have the message that the IBM jsf extension was loaded on startup. Given that I would have expected the IceFaces classes to not work.

Again thanks for your help. I wanted to log this with you for future reference if we need it.

A couple of things about this.

First, why would it just start? BTW - Now the problem has disappeared as mysteriously as it appeared.

While I was having the problem I changed my class loading policy to parent last and it did not help. Why would I have to remove these jars.

Finally if I remove all of the IBM jars, won't I disable any other uses of JSF that was developed with the IBM JSF jars?

Thanks.