ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I would be interested to know if you are experiencing this same problem with the DR4 version of Icefaces and jboss-seam1.2.1GA A lot of work has been done on the icefaces framwork and components to integrate well with Seam and we'd like to keep track of any issues that have been resolved with the upgrades.
Thanks.

Another thing to check is that you are using JDK1.5 and that you don't have any shared jars on your Jboss server that are loading a different facelet viewhandler (because that is what your dump is insinuating).
DId you try to download seam-showcase-1.6.0-DR4-bin.zip from our org downloads site :- http://www.icefaces.org/main/downloads/project-downloads.iface

try deploying this to a clean Jboss 4.0.5 with ejb3 configuration since that works on all platforms.

I see that you fixed the build script in order to get the proper source files for the build (line 41 where the correct directory when you just have the icefaces binaries is /docs/components) so that isn't the problem. I just did everything you did and everything worked just fine.....I don't usually use the exploded deployment though because I run out of perm-gen space on the server too quickly. You are using the ejb3 configuration of jboss4.0.5 are you? You might want to clean up the temporary files, get rid of the exploded directory (from a previous run) and just try to deploy the ear file. Use the ant archive target and then the ant deploy (after ant clean of course). There has got to be something else happening here since I have gone from scratch several times and can't duplicate your error. YOu might want to delete all the jars within your seam-component-showcase/lib and start again with freshen (if you haven't already). I'll ask some of the others around here as well.

I found an example in the icefaces directory of the examples that come with jboss-seam1.2.1GA Keep in mind that you have to update the iceface*.jars (all 3) and you have to update the faces-config and the web.xml to ensure you have the correct parameters but it does work (this snippet is from the mail.xhtml and you can see that the selectHotel method does indeed take a parameter--and I don't get any errors at all).

<h:column>
<f:facet name="header">Action</f:facet>
<s:link id="viewHotel" value="View Hotel"
action="#{hotelBooking.selectHotel(hot)}"/>
</h:column>

Let me know if you have any problem updating the web.xml or the face-config or if I have misunderstood the problem.

Thanks for the added info. I will try to check this out in the next few days and see what is involved with using the annotations. Do you have a few lines of code from the facelets (just regular seam) that shows how you want to use this? Or some idea of how you see it being used. Any further details would be a help (before I make more assumptions and get it wrong!)
Thanks.

If there is a nested long running conversation then it won't begin a new one. For now, since we aren't reallying creating a stateful session bean with either seam-component-showcase or seam-gen, the conversational scope hasn't been something we have delved into too deeply. There is the icefaces booking example that comes with the jboss-seam1.2.1.GA package that shows how to use the conversational scope (and a stateful session bean!). Any insight you can provide us will definitely be considered as we further try to implement more of the seam framework functionality (without losing our original functionality, of course!).

First I have to ask if you are also using Seam1.2.1GA? Did you use the freshen target of the build script to create the /lib folder? If yes to all the above, then did you look inside the ear and ensure that everything was there as required? Just to make sure, I just downloaded it from our org site (the source) and followed these steps and everything deployed fine. There is a problem in this release with the Style not in all contents facelets, but it does not affect deployment or loading of the application.

Did you download the source or binaries of DR4? Any further information you could provide, would help us to resolve this.

Thanks.

if you look in the examples folder of the Seam1.2.1GA files, you can find the following used in the icefaces example:-

@Stateless
@LoggedIn
@Name("logout")
public class LogoutAction implements Logout
{
public String logout()
{
Seam.invalidateSession();
return "login";
}
}

We have been testing our framework with this successfully and with the ability to use the built-in seam Identity class from our facelets in the following manner:-

<s:link view="/home.xhtml" action="#{identity.logout}" value="Logout" rendered="#{identity.loggedIn}"/>

we have not tried to use them together as you have done. Any reason why we would do so? We have thus far concentrated on getting the basics working with the Seam framework but would like now to work on getting a better understanding of other aspects of the Seam framework that people desire. Since there are many ways to accomplish the same outcome in Seam, it is necesary to understand why and when you would require this to work.

Thanks.

I also checked it in IE7 and it worked fine for me. This kind of suggests that maybe something isn't correct in your web.xml file... can you attach a copy of it?

what type of a result are you getting. If you are using the latest seam-gen (Icefaces DR4 with seam1.2.1GA you should be in Standard Request Scope (and this is set as a context parameter in the web.xml). What is your evaluated expression in the bean and what is it returning to your facelet? Have you got an outputText somewhere that you can send the value to (just to see what it is?).

In the versions older than 1.6DR (latest release) we used to use it in the web.xml as a listener. It is no longer required, so make sure to use the new web.xml that comes with either the latest seam-gen or seam-component-showcase.

I just checked out a recently run seam-gen project and left the default configuration in web.xml to the following:-
<context-param>
<param-name>org.icesoft.examples.serverClock</param-name>
<param-value>false</param-value>
</context-param>
When the accordionPanel was opened, it gave me the time at that moment and only updated when the panel was opened again.

When I changed this value to true and redeployed, the time was updated every 5 seconds (as per the bean).

I was unable to recreate your problem...is there any more information you can give me? (your web.xml and your TimerBeanImpl.java perhaps?) By the way, also in the web.xml the following context-param states that we are running asynch Update

<context-param>
<param-name>com.icesoft.faces.synchronousUpdate</param-name>
<param-value>false</param-value>
</context-param>

It's been tested with the ice:dataModel and the h:dataModel(to autogenerate the tabs)... Just out of curiosity, what is the benefit of using s:dataModel?

It looks like there is a problem loading the icefaces faceletViewHanlder (designated in the config.sys =com.icesoft.faces.facelets.D2DSeamFaceltViewHandler)

Ensure that you don't have any other facelet handler packaged in your project(or in your Server libraries) as we have seen this cause problems before --specifically with jsf-facelet.jar.

The seam-component-showcase when downloaded has a freshen tag that if you point it to the home location of jboss-seam1.2.1 and home location of icefacesDR4, should update (or copy the libraries) into your project. (which ensures that the jsf-facelets.jar is not there). If there are still problems with loading the icefaces facelets view handler, and it is not available elsewhere (or you don't have another facelet view handler jar file elsewhere that could be contributing to this problem, please let us know!) As with Seam1.2.1, we have used the myfaces jars for this application.

can you also confirm that you are using jboss-seam-1.2.1.GA with IcefacesDR3?