ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I am experiencing the same.

Any ideas or workarounds that does not involve jstl?

I just recently discovered that using JSTL and bindings in combination with view scoped beans results in beans being constructed way too much (http://java.net/jira/browse/JAVASERVERFACES-1492).

So now I am cleaning up the app and removing bindings and JSTL where relevant.

But I have discovered that using a f:convertDateTime with pattern and timezone fetched from a view scoped bean, displays the same behaviour. The view scoped bean gets constructed upon every ajax request.

Any idea why that is?

Just upgraded a web app from 1.8.2 til 2.0.2.

Saw a strange behaviour on a list of elements. When invoking a actionlistener on bean the list grew in size with empty elements.

Traced it to:

Code:

 NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method]	
 NativeConstructorAccessorImpl.newInstance(Object[]) line: 39	
 DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 27	
 Constructor<T>.newInstance(Object...) line: 513	
 Class<T>.newInstance0() line: 355	
 Class<T>.newInstance() line: 308	
 StateHolderSaver.restore(FacesContext) line: 150	
 UIComponentBase.restoreAttachedState(FacesContext, Object) line: 1749	
 ComponentStateHelper.restoreState(FacesContext, Object) line: 304	
 HtmlDataTable(UIComponentBase).restoreState(FacesContext, Object) line: 1577

This is not the behaviour of 1.8.2.

I fixed it by letting the elements in the list implement Serializable.

Is this a bug or why is this required now?

/Chr

I have tried different things now.

Playing around with a manually established context and the following

Code:

String windowId = WindowScopeManager.determineWindowID(context);
 context.getExternalContext().getRequestMap().put("ice.window", windowId);

but I cant seem to get access to the same window scoped bean when trying to look it up later at different views in same window.

I guess that switching all session scoped beans to window scope would enable my app to work when user has the app open in different tabs.

But I have some places where I access or create the session scoped beans manually via HttpSession - eg. in filters.

Is there a way to manually create and register a window scoped bean in a filter - i.e. outside of faces context?

/Chr

IceFaces 1.8.2
Jsf 1.2

Inputtext fields within a datatable get re-rendered thus clearing any non-submitted data, when a commandlink with immediate = true is clicked within the same form.

Is this a known issue?

How does one handle errors that occur in the public InputStream open() method?

I would like to be able to skip processing and display an error message on the same page.

The problem was not RAD.

I haven't installed facelets in any way. I am just using RAD to develop the web-app using facelets like any other Eclipse....

We are using 1.8.2 and are having same problem with scrollbar on draggable popup dragging the popup instead og scrolling.

Is there a fix for this issue?

Boy that was a quick response in an otherwise stale forum.

My problem is not so much request as I would like for it to stay across the session. Doing this with a session scoped boolean value on 'visible' works as such, but the effect is more or less ruined.

Thanks anyway

I have tried experimenting with this as well.

If you store a boolean in session for and use that for either visbible or rendered, the effect is no longer good as it will blink with a full panelGroup before appying the effect (slideUp/Down).

Is there a good way to to this?

I am also looking into something that could do this in a more dynamic fashion.

I have a homemade javascript that can monitor inputfields and attach itself to links and buttons.

I would love for something like that to work with icefaces, but I foresee problems with inputfields that appear after ajax request.

Perhaps there is a way to hook into som icefaces events?

Any ideas on how to make it work dynamically, clientside?

Wouldn't it be cool if IceFaces had a param to enable such functionality :)

/Chr

At some point a combination also with editable table would be nice.

I am currently evaluating the composite components of the EE package, and

I was wondering if it is possible to combine the auto-sort table and the filter table?

It is common for us to have both filters and sorting on our tables.

/Chr