ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Hi,

localization in ICEfaces is the same as in JSF. For a better understanding you might want to have a look at: JSF Localization

Best regards,
Michael

Hi,

I think this is a more general issue and not related to ICEfaces. However, in order to get a properly escaped file name you could do something like the following:

Code:

 String fileName = new String(inputFile.getFileInfo ().getFileName ().getBytes("ISO-8859-1"),"UTF-8");

This should return the correct file name.

Regards,
Michael

Hi,

you might want to use the rendered attribute when you want a component to be rendered depending on a certain boolean condition which is evaluated in a backing bean. You can use the rendered attribute on any ICEfaces component. This allows to create very sophisticated client-side behaviour.

Best regards,
Michael

Hi,

try and use UTF-8 encoding on your jspx page to resolve this issue.

Michael

Hi,

typically iterative components like the dataTable component are used when you need to iterate over a collection of items. If iteration is not needed you wouldn't normally use an iterative component, but could use a panelGroup or panelGrid component instead and adjust its styles appropriately. Please refer to the tld definition of the specific components for further information which can be found in the binary ICEfaces bundle.

Thanks,
Michael

could you attach the complete sources of the demo app?

thanks,
michael

Hi,

I don't think you can integrate ICEfaces and Struts2, those are different approaches and you should really only use one of the two frameworks. As for tiles, I would suggest that you use facelets instead as templating framework which is specially designed for JSF based applications.

Thanks,
Michael

Hi,

users are often facing problems with this component when no id is specified for the menu items which are created dynamically. From the information you provided it is difficult to make a concrete assumption. Would you be able to attach a test case to this thread?

Thanks,
Michael

Hi Maxime,

are you using the ice:messages tag within your popup? If so, try one of the following:

- move the ice:messages tag outside ice:form
- wrap the ice:messages tag with a 'div' with ID

If this doesn't resolve the problem, would you be able to attach a test case which demonstrates the issue?

Thanks,
Michael

Hi,

you will have to use a redirect in your navigation rules in order to see the next page's source code. By default JSF uses forwards. Therefore you won't see the next page's sourcecode.

Thanks,
Michael

Hi Ryan,

I think this is related to the following JIRA: ICE-2967
There exists a workaround mentioned in the JIRA.

Best regards,
Michael

Hi,

pages have to be UTF-8 encoded, so try and use the following within your head tag:

Code:

 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"></meta>

Then you can use the html character sequences. In your special case you would have to use:

Code:

 & #241;

A list of possible parameters can be found here: Html character sequences

Regards,
Michael

Hi,

it seems that you didn't define the action doGoToNext in your RowSelectController backing bean which you are referencing from your jsp file in

Code:

 <ice:commandButton type="submit" action="#{rowSelectController.doGoToNext}" value="Next"></ice:commandButton>

Thanks,
Michael

Hi,

could you post the relevant jspx and bean code as well as the configuration files?

Thanks,
Michael

Hi,

there's obviously no bug in ICEfaces. The problem is related to the way you are creating your components. Since you are creating your components from within the backing bean you have to be meticulous about setting the Id's of the components you create. I debugged the code and I've seen that an exception will be raised in TooltipInfo.java when no id is set to the surrounding panel of your underlying content. When you create your page in the default way, ICEfaces takes all the work for you by generating Id's automatically for each of your components. When components are created programmatically the developer has to take care of this. So, in order to get your app running, please add the following to your createInfoIcon method:

Code:

 HtmlPanelGroup info = new HtmlPanelGroup();
 info.setId("infoPanel");

Also, trying the same with the demo I provided works just fine fine without any modifications.

Thanks,
Michael