ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Here is the build.xml and you can use the buildGlassfish target (remember to define where your jboss-seam.1.3.0 and ICEFaces DR5 directories are).

The 2 main configuration differences are in the application.xml and web.xml files. I will attach the ones I am using for seam-comp-showcase. In case you have downloaded seam-comp-showcase already I will also attach a build.xml (see the next message from me) which will build the project depending on whether you have the 1.2.1 seam with jboss.4.0.x AS (I called the target buildMyFaces) or the jboss AS 4.2.0 with Seam 1.3 (head) and icefaces (DR 5 has just been released!) with the target buildGlassFish.

I have never tried to use the Ajax4jsf with Icefaces (why would I?) But to use Icefaces with jsf1.2 and jboss4.2.0 AS, you will want to change your web.xml to the one I am listing here (for seam-comp-showcase). You will also want to include commons-digester.jar in the application.xml file as a java module and include it in your ear file.

<?xml version="1.0" ?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">

<display-name>ICEfaces Component Showcase using Seam</display-name>
<description>
ICEfaces Component Showcase was designed to make developers aware
of the rich set of features available in the custom and extended
components. This version uses jboss-Seam application framework.
</description>


<listener>
<listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
</listener>

<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
</listener>

<listener>
<listener-class>com.icesoft.faces.util.event.servlet.ContextEventRepeater</listener-class>
</listener>


<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>

<context-param>
<param-name>facelets.DEVELOPMENT</param-name>
<param-value>true</param-value>
</context-param>

<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>

<context-param>
<param-name>com.icesoft.faces.actionURLSuffix</param-name>
<param-value>.seam</param-value>
</context-param>

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

<context-param>
<param-name>com.icesoft.faces.doJSFStateManagement</param-name>
<param-value>true</param-value>
</context-param>

<context-param>
<param-name>org.jboss.seam.core.init.debug</param-name>
<param-value>true</param-value>
</context-param>

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

<context-param>
<param-name>com.icesoft.faces.standardRequestScope</param-name>
<param-value>true</param-value>
</context-param>


<filter>
<filter-name>Seam Exception Filter</filter-name>
<filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
</filter>

<filter-mapping>
<filter-name>Seam Exception Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>


<servlet>
<servlet-name>SourceCode Reader</servlet-name>
<servlet-class>com.icesoft.icefaces.samples.showcase.util.SourceCodeLoaderServlet</servlet-class>
</servlet>


<servlet>
<servlet-name>uploadServlet</servlet-name>
<servlet-class>com.icesoft.faces.component.inputfile.FileUploadServlet</servlet-class>
<load-on-startup> 1 </load-on-startup>
</servlet>

<servlet>
<servlet-name>Persistent Faces Servlet</servlet-name>
<servlet-class>com.icesoft.faces.webapp.xmlhttp.PersistentFacesServlet</servlet-class>
<load-on-startup> 1 </load-on-startup>
</servlet>
<servlet>
<servlet-name>Blocking Servlet</servlet-name>
<servlet-class>com.icesoft.faces.webapp.xmlhttp.BlockingServlet</servlet-class>
<load-on-startup> 1 </load-on-startup>
</servlet>




<servlet-mapping>
<servlet-name>uploadServlet</servlet-name>
<url-pattern>/uploadHtml</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>Persistent Faces Servlet</servlet-name>
<url-pattern>*.seam</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>Persistent Faces Servlet</servlet-name>
<url-pattern>/xmlhttp/*</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>Blocking Servlet</servlet-name>
<url-pattern>/block/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>SourceCode Reader</servlet-name>
<url-pattern>/sourcecodeStream.html</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>SourceCode Reader</servlet-name>
<url-pattern>/sourcecodeStream.html</url-pattern>
</servlet-mapping>

<security-constraint>
<display-name>Restrict raw XHTML Documents</display-name>
<web-resource-collection>
<web-resource-name>XHTML</web-resource-name>
<url-pattern>*.xhtml</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>NONE</role-name>
</auth-constraint>
</security-constraint>
</web-app>

The problem is with the partial submit in the ice:inputText This causes Seam to submit the request parameters right away (and the date hasn't been selected yet). When you take the partial submit = true out, you can then select the date using the s:selectDate that you have setup.

Here is an alternative (s:selectDate is highly dependent on css and I prefer components that are a little more self-contained):-
<h:outputLabel for="date">
Date
</h:outputLabel>
<s:decorate id="dateDecoration">
<ice:selectInputDate id="date2"
renderAsPopup="true"
required="true"
value="#{cvPersonHome.instance.date}">
</ice:selectInputDate>
</s:decorate>

YOu can then take all the css stuff for showing the calendar (and there is a lot of it) and replace it with the following:-
/*
Calendar Styles
*/

.iceCalInput {
width: 90px;
}
.calendarGridColumn {
width: 50%;
vertical-align: top;
text-align: left;
}

Not too sure what is on the Seam CVS head as we have only tested with 1.2.1.GA.
But...if you look at seam-component-showcase or anything generated from icefaces-seam-gen you will notice that we no longer use the
com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Listener

anymore. As for the ConfigureListener and WebappLIfecycleListener --what is the requirement for these? Seam gives you access to the JSF Lifecycle and has the @Factory annotation which you can use to create objects.

I haven't tested anything against the Jboss4.2 AS yet, but will download it once we get the next release off. I see that it comes with the ejb3 installation, but also that it uses Glassfish JSF1.2 and I have not tested this with Icefaces and Seam yet......lots to do yet obviously. I will check with the others as well.

I put the s:selectDate in a tabbed pane and couldn't reproduce your error. There must be more to the problem. Do you perhaps have 2 tabbed panes with s:selectDate on each one (multiple panels of them???) A little more info please.

You are missing the ejb3 jars so you may not have the ejb3 installation of the jboss application server....look in your libraries of your server to be sure. The dtd's for these are in those jars. Easiest to re-download the AS.

It is totally harmless in that the icefaces view handler assigns it a unique id if it doesn't already have one...In the Jira you might want to mention having some setting to suppress the warning....Not sure if you want to remove it entirely as sometimes you may want to ensure that you have supplied unique Id's???

When I created a Tree from Database data, I ended up creating a Stateful Session Bean (you need one to use the @PersistentContext for the Entity Manager). Anyways, I have a list of data objects that I return from the entity manager and a Tree object in my stateful session bean. Then, when my database changes, my tree also changes.....
So.... I have the following:-

@Stateful
@Scope(SESSION)
@Name("testaction")
@TransactionAttribute(REQUIRED)
public class TestDataAction implements TestDataActionLocal, Serializable
{
...
@Out
private DefaultTreeModel modela;

@SuppressWarnings("unused")
@DataModel("treeData")
private List<TestData> availableTreeData;

and have to use a Factory annotation to create my list of treeData

@Factory("availableTreeData")
public void getAvailableTreeData(){
which gets the data from the database and builds the tree nodes
by instantiating my tree object with my list
}

This way my tree always reflects my database (as it possibly changes)....

Anyways, your exceptions is that it is not instantiating your tree.....If you follow the annotations here and instatiate your tree in your stateful session bean you won't lose your Entity Manager either. (I only wanted one instance per session of the Entity manager so made it session scope).

Hope this helps

I am currently working on just that same process (to integrate into the icefaces-seam-gen templates). I have the rowSelector working and am just going to try to set the page parameter and have my selectionListener for my rowSelector doing the redirection.....Seems to me the simplest way, but maybe you have another (better?) idea???

I should also comment here that the configuration files for seam-component showcase (or if you have generated a project using the icefaces-seam-gen that has been release) are good for Icefaces DR#4, jboss-seam1.2.1.GA and I have had best success with JDK1.5 (you need a minimum of JDK1.5 with seam because of the use of annotations)

You must be referring to the non-seam version of component showcase you would like to bring into eclipse. The seam-component-showcase version has a build script with it that you can import into eclipse (or myeclipse) using import using existing ant script.
For regular component showcase, you can either import into a general project using existing source and then create a build.xml from the existing build.xml in the directory of the component-showcase project and those required targets in the bundle you downloaded from icefaces (look for etc\build-common.xml).
OR...you can just create the directories and import the files into the normal structure you would use for packaging a web project.

For seam-component showcase:- I am currently running it using JDK1.5, jboss-seam1.2.1.GA, IcefacesDR#4. All is good.

What kind of problem are you having (exception, error ???)
Keep in mind that Seam maintains it's own version of EntityHome & Query--are you using the seam framework? If not then you must be doing something like this in your ejb3 sessionBean using :-

@PersistenceContext
private EntityManager em;

Could you provide us with more information....as in what are you trying to put in the node and what exactly the problem is?

Thanks....we have been having a few issues with Dom concurrentViews and are currently working on them (open Jira #1560) and this looks related.

Sorry, this is a know problem and discussion is going on right now to determine how we will try to integrate seam-pdf.