ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

IE usually runs into problems with embedded percent widths. Could you post a sample of the jspx code you have inside the tabset in question and any supporting css?

You should be able to call custom Javascript where ever there are the hooks for it. We sometimes write a little javascript to pre-cache images.

Can you tell me what your environment looks like, ICEfaces version, Facets, servlet container, etc.? Also how and where are you loading the javascript function declaration in your page?

I've seen this a couple application that I've worked on. When you application changes its flavour you can also change the tab index.

The easiest way to do this is to hook up a binding for the tabset. We have an example in the component-showcase. Here is a short explanation.

Code:

 <ice:panelTabSet 
  binding="#{tabbedPaneExample.tabSet}" ....
 
 </ice:panelTabeSet>

where tabset is defined as;

Code:

private com.icesoft.faces.component.paneltabset.PanelTabSet tabSet;

The tabset has a setSelectedIndex method which you can use to manipulate the selected tabset index.

Hello;

You shouldn't haven any problems with your code. Can you make sure that you component have an ice:form around them. Attach your jspx test page if needed.

Hi;

Can you check if this path "./inc/datascroller.jspx" is valid in your web application. The stack trace seems and the subsequent line number seems to indicate that the file can not be found.

Manipulating the UIComponent directly I think is the cleanest way to go. Nice work.

Hi Mcronin;

Could you also explain if the bean associated with a cell would keep a notion of what style it should have?

If this was they case you could setup your column declaration with a panelGroup (HTML div tag) which would allow you the change the cell background colour on a cell by cell basis.

Code:

 <ice:dataTable var="cellValue"
                value="#{someList.cellValues}" >
     <ice:column rendered="#{table.renderFirstName}">
         <f:facet name="header">
             <ice:outputText
                     value="Header 1"/>
         </f:facet>
         <ice:panelGroup styleClass="#{cellValue.cellCSSClassName}" >
             <ice:outputText
                 value="#{cellValue.someProperty}"/>
         </ice:panelGroup>
     </ice:column>
 </ice:dataTable>

Hi Aamir;

We've found that some Servlet containers do not correctly set the header information for some supporting web files. As a result the browser will repeatedly try to download images based on this incorrect header information. Can you let me know what server your running your application on? Also some web servers have setting that can be tweaked.

Attached is a filter implementation that we use on some of or application. It basically tries to set the correct http header so that web browsers will correctly cach images, css and .js files.

Here is the code you'll need to setup of the filter in your web.xml.

Code:

     <!-- Cache Control for Images -->
     <context-param>
         <param-name>com.icesoft.faces.uploadDirectory</param-name>
         <param-value>upload</param-value>
     </context-param>
     <context-param>
         <param-name>com.icesoft.faces.uploadMaxFileSize</param-name>
         <param-value>4048576</param-value>
     </context-param>
     <filter>
         <filter-name>Cache-Control Filter</filter-name>
         <filter-class>com.icesoft.icefaces.site.filter.CacheControlFilter</filter-class>
     </filter>
 
     <filter-mapping>
         <filter-name>Cache-Control Filter</filter-name>
         <url-pattern>*.css</url-pattern>
     </filter-mapping>
 
     <filter-mapping>
         <filter-name>Cache-Control Filter</filter-name>
         <url-pattern>*.gif</url-pattern>
     </filter-mapping>
 
     <filter-mapping>
         <filter-name>Cache-Control Filter</filter-name>
         <url-pattern>*.jpeg</url-pattern>
     </filter-mapping>
 
     <filter-mapping>
         <filter-name>Cache-Control Filter</filter-name>
         <url-pattern>*.jpg</url-pattern>
     </filter-mapping>
 
     <filter-mapping>
         <filter-name>Cache-Control Filter</filter-name>
         <url-pattern>*.js</url-pattern>
     </filter-mapping>
 
     <filter-mapping>
         <filter-name>Cache-Control Filter</filter-name>
         <url-pattern>*.jsp</url-pattern>
     </filter-mapping>
  
     <filter-mapping>
         <filter-name>Cache-Control Filter</filter-name>
         <url-pattern>*.png</url-pattern>
     </filter-mapping>

Hello;

Interesting thread. Can you give an example of your jspx inputText tags. I am curious about what attributes you're using. This information will be important in figuring out whats going on in your example.

Unfortunately there is no easy way to avoid the setters. I would recommend you make the necessary changes to your backing beans. Your application will be much more maintainable if you avoid messing with the lifecycle.

Thanks on the avatar, its great to hear that the tpb's are getting some air time south of the 49th parallel.

You have a couple of options here but they aren't particularly pretty, but should work none the less.

The trick will be to add a new Bean property to the validateUnitClassifier class. This new property will contain the name of the style class to use depending on the outcome of the validate method. You would also have to create a new instance of validateUnitClassifier for each binding.

Code:

 public static final String VALIDATION_ERROR_STYLE_CLASS = "validationError"
 
 public static final String VALIDATION_OK_STYLE_CLASS = "OK"
 
 private String validationStatusStyle = VALIDATION_OK_STYLE_CLASS;
 
 public String getValidationStatusStyle(){validationStatusStyle;}

You would have to manipulate the validationStatusStyle variable inside the validate method. Like I said earlier, not very pretty but it will work. You could also use Effects instead of CSS.

The final JSF code would look something like this.

Code:

<ice:inputText 
  	value="#{editUnitClassifierBean.unitClassifier.unitCode}"
  	validator="#{validators.validateUnitClassifier}"
  	styleClass="#{validators.validateUnitClassifier.validationStatusStyle}"			
  	/>

Hello;

We don't have any know issues with panelTabSet flicker. Could you post what browser you are seeing the flicker in.

The flicker might also be do do the time it takes to load the images that are shown on hover. Are you pre-loading the images used in your panelTabSet?

You should be able to add it to an inputText by taking advantage of one of the on*Effect attributes. These attributes can be associated with an com.icesoft.faces.context.effects.Effect object.

I don't see any problems with the jspx code you submitted. I assume that the style for the background is being set by one of the included pages? Could you send one of your include pages so I can take a look at how your setting the background colour.

When one of the three buttons are pressed the page request is send to the server and the JSF lifecycle is executed as per usual. Any changes are sent back to the browser. This process occurs just like a normal JSF application but with ICEfaces there is no page refresh.

It should be possible. The chart component takes a list of Strings which define the charts labels/legend. It would be up to your packing bean logic to insure that label strings represent the the respective percentages.

The chart component leverages the jChart api and as a result is very customizable if the default component types don't meet your needs. The component showcase has a simple example of how to build a custom chart. The jChart library documentation can be found at http://jcharts.sourceforge.net/downloads.html .