Sheila's Blog » icefaces http://sheilapollard.com Software Development Wed, 24 Mar 2010 17:19:01 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Configuring Icefaces and JBoss Seam Excel http://sheilapollard.com/2009/08/20/configuring-icefaces-and-jboss-seam-excel/?utm_campaign=feed&utm_medium=feed&utm_source=blog http://sheilapollard.com/2009/08/20/configuring-icefaces-and-jboss-seam-excel/#comments Thu, 20 Aug 2009 10:14:42 +0000 Sheila http://sheilapollard.com/?p=463 As in Configuring Icefaces and Seam PDF, when you want to render excel pages in an application that already uses seam and icefaces, you need to use the default view handler for rendering the excel files.  So you need to follow some of the same steps…  Separate out the pages so that some are icefaces pages only, the other pages are non-icefaces and do the Excel rendering.   Replace icefaces.jar with just-ice.jar and configure the application to delegate pages that contain to the standard facelets view handler.

Steps:
1.    Update to icefaces 1.8.1 and jboss-seam 2.2.0.GA and test the application still functions correctly.
2.    Replace icefaces.jar with just-ice.jar (from the icefaces jars) and redeploy the application.  Fix any errors.
3.    Add in the excel functionality.  Add jboss-seam-excel-2.2.0.GA.jar and jxl.jar to your ear file.
4.    In components.xml add the excel and document namespacesxmlns:excel="http://jboss.com/products/seam/excel" xmlns:document="http://jboss.com/products/seam/document" http://jboss.com/products/seam/document http://jboss.com/products/seam/document-2.2.xsd http://jboss.com/products/seam/excel http://jboss.com/products/seam/excel-2.2.xsd

5.    In faces-config.xml you add both view handlers <application> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> </application> <application> <view-handler>com.icesoft.faces.facelets.D2DSeamFaceletViewHandler</view-handler> <message-bundle> JSFoverride </message-bundle> </application>

6.    Configure the document servlet in web.xml <servlet> <servlet-name>Document Store Servlet</servlet-name> <servlet-class>org.jboss.seam.document.DocumentStoreServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>Document Store Servlet</servlet-name> <url-pattern>*.csv</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>Document Store Servlet</servlet-name> <url-pattern>*.xls</url-pattern> </servlet-mapping>

and add a new mapping for jsf pages to be handled by the Faces Servlet <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.jsf</url-pattern> </servlet-mapping>
Your application should now be configured to render excels.  To test this you can copy some of the .xhtml pages from the seam \examples\excel to test that the rendering works.  Take ExcelTest.java and people.xhtml.  Create a normal index page and add a link to people.jsf. <ice:outputLink value="./docs/people.jsf">2nd Excel Test/>

In people.xhtml I had to edit the value to excelTest.people instead of people <e:worksheet name="People" value="#{excelTest.people}" var="person">

Now redeploy your application and try accessing people.jsf


Comments ]]> http://sheilapollard.com/2009/08/20/configuring-icefaces-and-jboss-seam-excel/feed/ 0 Configuring Icefaces and Seam PDF http://sheilapollard.com/2009/08/17/configuring-icefaces-and-seam-pdf/?utm_campaign=feed&utm_medium=feed&utm_source=blog http://sheilapollard.com/2009/08/17/configuring-icefaces-and-seam-pdf/#comments Mon, 17 Aug 2009 13:33:44 +0000 Sheila http://sheilapollard.wordpress.com/?p=455 Unfortunately seam-pdf doesn’t play nice with ICEfaces. Specifically, the D2DFaceletViewHandler doesn’t do pdf/email rendering. The workaround for this is to separate the application into ICEFaces (ice: tags) and Non-ICEFaces (h: tags) pages which are the ones that trigger a pdf or email render. You can replace icefaces.jar with just-ice.jar, which contains renderers for ICEFaces components only. Then configure the application to delegate any pages that consist of a to the standard facelets view handler instead of D2DFaceletViewHandler.

Steps:

1. I updated to icefaces 1.8.1 and jboss-seam 2.2.0.GA and tested the application still functioned correctly.
2. Replace icefaces.jar with just-ice.jar (from the icefaces jars) and redeploy the application. You may get some errors. For example I found a number of errors caused because an xhtml page contained more than one with ids that weren't unique.
3. If the application is functioning correctly you can start adding in the pdf functionality. Add itext.jar, itext-rtf.jar, jboss-seam-pdf.jar, jcommon.jar, and jfreechart.jar to your ear file.
4. In components.xml add the pdf and framework namespacesxmlns:pdf="http://jboss.com/products/seam/pdf" xmlns:core="http://jboss.com/products/seam/core" xmlns:framework="http://jboss.com/products/seam/framework" http://jboss.com/products/seam/framework http://jboss.com/products/seam/framework-2.1.xsd http://jboss.com/products/seam/pdf http://jboss.com/products/seam/pdf-2.1.xsd

Also add the following to configure missing pdfs: <component name="org.jboss.seam.document.documentStore"> <property name="useExtensions">true</property> <property name="errorPage">/pdfMissing.seam</property> </component>

5. In faces-config.xml you add both view handlers
<view-handler>com.sun.facelets.FaceletViewHandler</view-handler> </application> <application> <view-handler>com.icesoft.faces.facelets.D2DSeamFaceletViewHandler</view-handler> <message-bundle> JSFoverride </message-bundle> </application>

6. Configure the document servlet in web.xml <servlet> <servlet-name>Document Store Servlet</servlet-name> <servlet-class>org.jboss.seam.document.DocumentStoreServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>Document Store Servlet</servlet-name> <url-pattern>*.pdf</url-pattern> </servlet-mapping>

and add a new mapping for jsf pages to be handled by the Faces Servlet <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.jsf</url-pattern> </servlet-mapping>
Your application should now be configured for icefaces pages, and non-icefaces pages that can render pdfs and emails. To test this you can copy some of the .xhtml pages from seam's \examples\itext to test that the pdf rendering works. The index.html lists the examples available. You will need to take lists.xhtml and Lists.java and add them to your application to test that the PDF Lists link in the index works correctly. Assuming your application has no errors and the PDF List example generates a pdf successfully, you're ready to use seam pdf in your web application.


Comments ]]> http://sheilapollard.com/2009/08/17/configuring-icefaces-and-seam-pdf/feed/ 0 Icefaces link issue in Seam – missing dataModel http://sheilapollard.com/2009/03/09/icefaces-link-issue-in-seam-missing-datamodel/?utm_campaign=feed&utm_medium=feed&utm_source=blog http://sheilapollard.com/2009/03/09/icefaces-link-issue-in-seam-missing-datamodel/#comments Mon, 09 Mar 2009 18:42:50 +0000 Sheila http://sheilapollard.wordpress.com/?p=17 The problem is:
We have a list of objects (we’ll call them Cars) displayed as results from a search in a seam web application. This is displayed as rows, iterating through the results to reference thisCar for the current result in each row. We want to be able to select one of the Cars and open a new window which shows the selected car information, but retains the search results also.

So the current conversation should be brought through to the new window (to keep the current result set), and then the selected Car should be set (starting a new conversation). The s:link tag maintains the conversation, but currently does not work correctly as it is missing a backing datamodel. To add that datamodel would require substantial refactoring, adding a lot of extra seam components just to allow the selection to work.

The broken url is http://localhost:8080/app/page.seam?actionMethod=page.xhtml:selectedCar.setCar(thisCar)&cid=3

Without the backing datamodel, the thisCar variable gets passed into the setCar method as null.

A workaround for this is to use a request parameter in the backing bean and a new method that retrieves the list of results and identifies the correct car to select from that.

In the xhtml page use the s:link tag with a parameter set to the current row id: <s:link id="selectCar" value="#{thisCar.id}" style="color:blue" action="#{selectedCar.setCar()}"> <f:param name="rowId" value="#{thisCar.id}" />
In the backing bean that row id is a request parameter: @RequestParameter private String rowId;
Use the rowId to determine the correct car: public void setCar() { int selected = (Integer.parseInt(rowId));</p> Iterator it = results.iterator(); while (it.hasNext()) { Car car= (Car) it.next(); if (car.getId() == selected) { selectedCar = car;< } }
The url is now: http://localhost:8080/app/page.seam?rowId=3&actionMethod=page.xhtml:selectedCar.setCar(selectedCar)&cid=3


Comments ]]> http://sheilapollard.com/2009/03/09/icefaces-link-issue-in-seam-missing-datamodel/feed/ 0