torejournal.blogg.se - Seriesstateholder icefaces

Seriesstateholder icefaces code#

In next post, we'll start working on the style and ICEface UI Components.įirst of all, open Eclipse IDE, i) Opening Eclipse, then create new dynamic web project ii) Creating Dynamic Web Project. You'll see the first line of " Tank you for using ICEfaces. Congradulation! You've successfully created ICEface application. Then connect your web application using browser and url: 10. Start Tomcat 6.0, (Restart if already sarted)ĩ. Click Finish to complate war file generationĨ. Select Overwrite existing file to overwite next time when you export war file againħ. Select your \webapps folder as Destination as shown in figure:Ħ. Right-click on the crm-web-project, select Export-> WAR file from pop-up menu as shown in figure:ĥ. Copy the following libs, jar files, from \lib to \WebContent\WEB-INF\libĤ. overwrite web.xml file, which is under WEB-INF folder, with the following code:Ĭustomer Relationship Management Web ApplicationĬom.PersistentFacesServletĬom.BlockingServletģ.

Seriesstateholder icefaces code#

Enter the following code to index.xhtmlĢ. Create index.xhtml file in the same folder where you created index.jspxĢ. now, open your web site from browser and you will see the nice welcome page with cool styles.!!!Īfter creating index.jspx, we've to create welcome page, so called index.xhtml, and add this welcome page to web configuration and redirect to index.jspx using ICEface Servlet.ġ. Save all the files, then Export as WAR file and deploy to your tomcat as explained in previou post, " Configuring and Deploying Web Application". Replace the tags with the following code which will use the specific title defined by applied pages # 9. Add styles called, the following code, before tag.

Create default-template.jspx file under templates folder using New JSP File Wizard, explained in previous post " Creating New JSPX File". Then, we gotta create our own templates which are header, footer, default-template jspx files.

Paste all the files to your project css folderģ) Creating and applying template files Now, we've got read-made styles and icons.

Copy three css files: showcase_layout.css, showcase_overrrides.css and showcase_styles.css and also the images folder.

Go to \samples\component-showcase\common-web\css to \WebContent\WEB-INF\css.

You may use your own styles if you had one already. 2) Preparing styles Before creating templates, we'll copy the ICEfaces styles and icons from component-suite project to our project first. The pages will be kept right under WebContent folder contentsfor all the page contents which can be forms, table, tree or others templatesfor all the templates file such as header, footer, main template, and etc. Each folder description is explained as below: css for all the styles images for all the images, you may need other sub folders like icons and logo to organize your icons and company related images includes for all the jspx files used in every pages. Follow the steps below to create your own template easily and quickly as 123, 1) Creating folder structure, 2) Preparing styles and 3) Creating and applying template files 1) Creating folder structure Create the folders similar to the structure shown in firgure in WebContent folder of your project, crm-web-project. So, this post will help you create a simple template using ICEfaces tags. Using template will help you control of the consistency of your web site styles, menus and so on. Moreover, the consistency of your web site look-and-feel is also the good impression for your visitors.

However, when you want to change, you don't want to change in every single pages of your more than 100 pages web site. For example, you don't want to change your web site name or description very often. Template is very useful for easier and better maintenance of your web site. If you've some lists or a data table on the same page set to a model in your bean, changes will automatically be displayed except you're using the immediate keyword set to true on your save button.Īdditionally you might consider a panel with a content of your choice which has the rendered property set to a boolean in your bean, which will be triggered within the saving process and therefore let the content be displayed only after hitting save.Basically, we need template to enable you to change once and apply to all the pages. If no navigation rule matches a given action, the current page will be redisplayed (although from the experience i made this refresh is different to a common HTML refresh). Navigation rules will be defined in faces-config.xml There are two options which come to my mind:ĭefine a page to which you'll navigate to after hitting "save".įor doing that, your action for actually saving the data to DB will go into the method defined as an actionListener or, if you want to make your next page depending on the outcome of the saving process, as action.