ICEfaces Java Studio Creator 2 Integration
v1.5 (Early Access) Release Notes
The ICEfaces Java Studio Creator 2 (JSC2) integration provides ICEfaces support for developers who use JSC2 IDE for web application development. The ICEfaces integration consists of two parts:
1. A JSC2 extension that provides runtime library support for ICEfaces and support for wizards for starting new ICEfaces JSF projects or converting an existing JSF project to ICEfaces.
2. A JSC2 component library (complib) file that provides support for using the ICEfaces Component Suite components at design time. The complib is included in the JSC2 extension. It will be automcatically imported into the Component library Manager when you create a new ICEfaces JSF Project in the first time.
Note: This release is designated Early Access (EA). While it provides most of the functionality of the final release, there are still some missing features, known issues, and a lack of refinement in some areas. Please review the Known Issues section prior to using this integration.
The ICEfaces extension requires Sun Java Studio Creator 2, Update
1. Java Studio Creator 2 is available as a free download from the
Sun Studio Creator Web site. It is highly
recommended that you become familiar with using Java Studio Creator for
JSF web application development prior to using ICEfaces with JSC2.
To successfully use the ICEfaces Component Suite components with JSC2, you must use them in conjunction with the following JSC2 webui components:
Because JSC2 requires the use of these components for design time support, the ICEfaces extension includes ICEfaces Direct-to-DOM renderers that enable them to work correctly with the ICEfaces Component Suite.
Note: No other webui "ui:" components are supported at this time. In practice, this means that any ICEfaces applications developed using JSC2 must also use these webui components. Thus, all applications must use these JSC2 webui component runtime JARs at deployment/runtime.
The project should now have all required icefaces JARs and configuration entries added to the existing web.xml.
With Java Studio Creator 2 Update 1, the ICEfaces files are located
under the ../rave2.0 directory (for example, under Linux
To completely uninstall the ICEfaces JSC2 integration, you must have JSC2 shutdown and then complete the following steps:
The ICEfaces Component
The ICEfaces Component Library depends on the ICEfaces Java Studio Creator 2 (JSC2) extension which provides the required ICEfaces Runtime Support Library and deployment description configuration.
ICEfaces Complib is included in ICEfaces Extension for JSC2. It will be imported into Component Library Manager when you create a new ICEfaces JSF project in the first time. No separate import component library required.
To use the ICEfaces Component Suite in JSC2 in the "Design" editor, you must first create a JSP page skeleton using the JSC2 Webui components listed in the Requirements section. Once you have a suitable JSP page created, you may:
The following instructions assume that you are familiar with Java Studio Creator and that you have already created your project.
2. From the Components Palette, right-click the dataTable and select Bind to Database.
For detailed instructions for Binding a Data Table Component to a Database Table, refer to the Sun Studio Creator Web site at http://developers.sun.com/prodtech/javatools/jscreator/reference/techart/2/bindingDataTableComponents.html
3. Select the Table component and then right-click Table Layout from the context menu.
4. In the Table Layout dialog box, click the Paging tab and check Enable Paging. Specify the number or rows and modify other display options. When you are done, click OK.
5. Use the context menu items (for example, Add UIColumn, Add RowSelector, etc.) to add ICEfaces components to the dataTable. Refer to the ICEfaces Component Suite for additional information on components.
6. To add a SortHeader to a dataTable, right-click and select Bind to Database. For additional information, refer to the Sun Studio Creator Web site at http://developers.sun.com/prodtech/javatools/jscreator/reference/techart/2/bindingDataTableComponents.html
Before adding a sortHeader, you need to bind a RowSet to the Data Table. Drag the table component onto a page, then drag a data source table (for example, PERSON) onto that Table component. The IDE not only binds the PERSON data table to the Table component, automatically changing its column headings to match the table fields, but also adds a RowSet (personRowSet) to SessionBean1 and a Data Provider (personDataProvider) to the page. You can see these two components in the Outline within SessionBean1 and the page.
Refer to http://developers.sun.com/prodtech/javatools/jscreator/reference/index.jsp for more information.
By default the commandSortHeader component is used in conjunction with a Data Table and CachedRowSetSortableDataModel in design time. The commandSortHeader renders a clickable column header facet allowing the user to toggle the sort order of data in the table, either ascending or descending based on the values in the column. The commandSortHeader can be used to provide a user-controlled data sorting capability to a dataTable.
7. To select items to bind to the database, right-click an item (for example, selectManyMenu, selectManyList, selectOneMenu, etc.) in the Outline tree view.
The following screen image shows the context menu for a selectItems inside selectManyMenu:
The following screen image shows the context menu for a selectItems inside selectManyCheckbox:
8. Select a related Value field and Display field items and click Apply.
The following screen image shows the Bind List Items to Database dialog box.
For more details, refer to http://developers.sun.com/prodtech/javatools/jscreator/reference/techart/2/checkbox_component.html
9. You can use the dataPaginator component to handle table pagination. In the Palette pane, select the Data Table and drag the DataPagination componet onto the table.
10. In the Palette pane, select PanelTabSet, and then drag it onto the design panel or tree view. If you click a tab while designing your web page, that tab becomes the selected tab.
11. You can bind most input and output components to data objects. Binding a component to data enables the web application to automatically synchronize the component's value with the value of the binding target. For example, if you bind a component to a bean property, the web application sets the component's value to the bean property's value when the application renders the page, and when the page is submitted, the web application changes the bean property's value to match changes made to the component's value.
The following screen image shows a default databean (selectOneRadioDefaultItem):
12. You can change the look and feel in the design time and runtime for your project by attaching a stylesheet. Use xp_dt.css as the design time stylesheet and xp.css as the runtime stylesheet.
Add the <ice:outputStyle> stylesheet and change the <href> attribute from the Properties view with ./xmlhttp/css/xp/xp.css. The strict path is required ./xmlhttp/css/xp/xp.css.
Sun Application Server Memory heap size
Performance can suffer due to the overhead required to manage limited memory.
Setting JVM Heap size for Sun Application Server.
For more detailed information, please refer to http://java.sun.com/docs/hotspot/VMOptions.html
Setting JVM Heap size for Creator 2
netbeans_default_options="-J-Xms128m -J-Xmx512m -J-XX:PermSize=128m -J-XX:MaxPermSize=256m
You should set your maximum Java heap size so that the total memory consumed by all the JVMs running on the system does not exceed the memory capacity of your system.
For more detailed information about turn Creator 2 to work with large applications, please reference to http://developers.sun.com/prodtech/javatools/jscreator/reference/faqs/technical/tshooting/index.jsp
Reset Sun Application Server
Only necessary if you want to reset Sun Application Server.
D:\Program Files\Sun\Creator2_1\bin\pe-start -reset
It will rebuild default domain. All deployed applications will be deleted.
For more detailed information, please refer to http://docs.sun.com/source/819-0215/index.html
Setting Logging Level with ICEfaces in Design Time
Running Creator 2 with default JVM, logging.properties can be found under following:
You need to add the following logging level:
com.icesoft.faces.level = FINEST
For more detailed information about JDK logging, please reference to http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html
For more detailed information about log file in Creator 2 or the deployment server, please reference to http://developers.sun.com/prodtech/javatools/jscreator/reference/faqs/technical/tshooting/index.jsp
How to deploy to Tomcat:
Export the project from the IDE as a war file. and Deploy the application by copying its WAR file into tomcat-install-directory/webapps.
For more detailed, please refer to http://developers.sun.com/prodtech/javatools/jscreator/reference/docs/help/2update1/deploy/howtodeploy/deploy_tomcat.html
The following are known issues in this release:
For help with this release, refer to http://support.icefaces.org which includes the ICEfaces knowledgebase including articles, slide shows, and other resources. In addition, refer to the ICEfaces support forums where you can monitor and participate in discussions on ICEfaces technology, tips, and techniques.
Additional commercial support is also available from ICEsoft Technologies Inc. Visit www.icesoft.com.
License agreements can be found in the .../install_dir/creator2/icefaces/license directory.
© Copyright 2005-2006. ICEsoft Technologies, Inc.