voyent
Messages posted by: philip.breau  XML
Profile for philip.breau -> Messages posted by philip.breau [2745] Go to Page: Previous  1, 2, 3 , 4 ... 181, 182, 183 Next 
Author Message
Do you still get the error with 3.3.0?
Well, if you'd like to list your other ice components being used, we can suggest alternatives.

Philip
I would suggest using the ace:messages, if possible. Does the problem still occur with that?
You can call it your bean in an @PostConstruct method.
Is there a dom diff generated after clicking on the data picker that might be interfering with the flash script or state? Try separating them in separate panelGroups so that a dom diff from the date picker doesn't include anything from the uploadify script and object.

Philip
Looking at the code in the dataTable, it looks like DataTable.applySort() isn't called until there's a change in the internal hashcode (meaning a change in one of the table parameters). Try getting a reference to the DataTable component, then calling applySort() directly in your bean to work around it.

Philip
Hi,
Have you setup your mandatoryResourceConfiguration for all of your ace components? If not, add the context-param in your web.xml with the value of 'all' to check that your issue isn't due a missing javascript resource.

http://www.icesoft.org/wiki/display/ICE/mandatoryResourceConfiguration

Thanks,
Philip
The ice components, such as the ice:dataTable are not compatible with JSF Ajax rendering (aka subtree rendering). That's supported in the Ace components. The ace:fileEntry component you're using is probably not the issue, but the ice components probably are. Try changing the ice:panelGroup to an h:panelGroup, and likewise for any other ice components in the view.

Thanks,
Philip
I just tested on FF 23 and 24 on both Windows 7 and OS X and it seems ok for me. What system are you on? Can you reproduce when running FF in safe mode without plugins?

Philip
Hello,
Please open a new jira for this with a test case and we'll take a look.

Thanks,
Philip
Please check http://www.icesoft.org/JForum/posts/list/0/22121.page#77984
I'm not sure the problem really has anything to do with Tomcat. ICEfaces uses a JSF system event listener to add some custom forms to the page. If you accidentally include multiple ICEfaces jars (including the icefaces.jar and icefaces-ee.jar) then the listener can be registered twice, leading to this error. So double check your applications and ensure that only one icefaces.jar or icefaces-ee.jar are on the classpath. I've created a jira for this for us to test for this configuration error if you'd like to vote for it: http://jira.icesoft.org/browse/ICE-9595


Thanks,
Philip
Yes, an outputResource can be dynamically bound to a backing bean Resource property.

Philip
I would suggest trying to wrap the dialog and triggering component (whatever the component is, or however you call it, server or client side) in the same form and see if that resolves the issue on IE. If you could please note your results in the case comments, that would be great.

Thanks
I can reproduce the problem. The problem appears to go away if I include the commandLink in the same form. I've opened a case for this.

Thanks
 
Profile for philip.breau -> Messages posted by philip.breau [2745] Go to Page: Previous  1, 2, 3 , 4 ... 181, 182, 183 Next 
Go to:   
Powered by JForum 2.1.7ice © JForum Team