ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

The component-showcase has an example of the paginator with an ice:dataTable which you stated worked fine. Perhaps you could attach your source for your facelet or jsp as well as the backing bean? We could make assumptions that your configuration files are setup as per the component-showcase (for DR4) for all required components or you could attach them as well. You may want to start with the source code from component-showcase as a base and then modify to want you are trying to do.

just to confirm ....you are using DR4 and creating the component-showcase application (there are 2 versions for regular component-showcase that come in the samples directory of our DR4 release) Problems with this are normally reported on the General questions part of the forum.

The seam-component-showcase is bundled separately and are dealt with on this forum. It also requires JDK1.5 and an ejb3 container(since seam uses annotations and session beans). If you can give us some more details as to which product you are having problems with, that would be great. (which browser are you using and what version perhaps?)

Yes, this is the current web.xml for DR#4. Which documentation are you referring to?

I am going to assume that by running icefaces-seam-gen this also fixed up your WEB-INF/lib as these are the jars that should be in there:-
oscache-2.3.2.jar
jboss-seam-ui.jar
jboss-seam-remoting.jar
jboss-seam-pdf.jar
jboss-seam-mail.jar
jboss-seam-ioc.jar
jboss-seam-debug.jar

the icefaces jars should be in your ear along with the commons-*.jars and several of the other required jars.

This has been the packaging for seam-icefaces projects for the last few months so I never thought to mention it before. If you don't mind, confirm for me that you have it packaged this way, please.

Now I'm the one that wasn't clear....the seam-component-showcase needs ejb3. (the bin bundle for this has the seam-component-ear that you can just deploy to an ejb3 enabled server)
The regular component-showcase can be deployed to Tomcat, but has to be compiled and packaged from source.
Hope this is clear....

Which type of server are you running on. have you gotten rid of all the temporary files? Did you try downloading the ear file and just deploying it (there is one on our download site for seam-comp-showcase)? (make sure the server has ejb3 capability). Were you using exploded files?

If you have an existing seam-icefaces application, you will need new configuration files as these have changed quite a bit from DR3. If you don't have any database connectivity to worry about, then just look at the web, faces-config and components.xml files from seam-component-showcase. If, however, you have database connectivity, then you might want to use seam-gen to generate a base application with those tables and then review all the configuration files to ensure they are consisitent with icefaces DR4 and seam1.2.1.GA. Majority of changes are in the web.xml.

Can I then assume that IE7 is fine? I currenlty don't have IE6.1 but will try to get it to test this.

are you talking about component-showcase that comes in the samples directory of the icefaces bundle? or the seam-comp-showcase that is bundled separately?

from what I understand the state changes quite often which is why you must get an updated version of the state before (re)rendering.

The problem isn't in the framework or seam, it is in the TimerImplBean itself. All our other applications use request scope for the interval renderer, but we don't have that available to us using seam. I tried Page scope and concurrent views worked fine here (until I received an exception) I think we will have to refactor this Bean so that the method is EVENT and the other stuff can be for the page. Will continue to work on this later, and will post here when it's solved.

I can't seem to recreate this problem. Using seam1.2.1GA and icefaces DR4 you might want to try using icefaces-seam-gen to generate your configuration files. This will set up your entity manager properly as well as everything else.

The icefaces-seam-gen will reverse engineer the data from your tables into pages that edit, view, search your tables (using the efficient Seam framework for database access).

I have tried to recreate your problem. The only time I get the Network Connection Interrupted is when I have timed out (as specified in my components.xml as follows:-

<core:manager concurrent-request-timeout="500"
conversation-timeout="120000"
conversation-id-parameter="cid"
conversation-is-long-running-parameter="clr"/>

<core:managed-persistence-context name="entityManager"
auto-create="true"
persistence-unit-jndi-name="java:/IceBuild4EntityManagerFactory"/>

I included the entityManager just in case. You can reset the timeout values if you like or reload the application.
Keep in mind the DR2, DR3 and DR4 don't all work with the same verion of jboss-seam. Just stick with the DR4 and 1.2.1GA if you can. If you really want to use DR3 or DR2, you will have to check which version of seam applies and note that the web.xml (configuration files) will be different for each, as it's been an ongoing process.

If this does not address your concern, please supply specifics.

You will want to go directly to getting icefaces 1.6DR4 in conjunction with Seam1.2.1GA and ensure you use the config.xml and web.xml that are with either a seam-gen generated project shell or from seam-component showcase.

Super! FYI the styles don't completely change on the version you have. If you want it to do so you just have to change the return of the method changeStyle() in the StyleBean class (in package com.icesoft.icefaces.samples.showcase.util)

just make sure it uses the following as a return value:-

return "/showcase.xhtml";

and the styles change properly. Other than that, all components should be working well.