ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I've been getting along quite reasonably building a Seam app with facelets and icefaces on the front end. Whilst most components work, it seems that anything requiring server-initiated rendering fails, with a No active application scope exception (see stack trace below).

Various other posts (here and in the Seam forums) refer to the same issue...does anyone know (a) where the problem is, and (b) when it might be fixed?

Cheers,
-Adrian

Code:

 java.lang.IllegalStateException: No active application scope
 	at org.jboss.seam.core.Init.instance(Init.java:75)
 	at org.jboss.seam.jsf.TransactionalSeamPhaseListener.handleTransactionsBeforePhase(TransactionalSeamPhaseListener.java:25)
 	at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:43)
 	at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70)
 	at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373)
 	at com.icesoft.faces.webapp.xmlhttp.PersistentFacesState.render(PersistentFacesState.java:180)
 	at com.icesoft.faces.async.render.RunnableRender.run(RunnableRender.java:89)
 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:643)
 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:668)
 	at java.lang.Thread.run(Thread.java:595)

Adrian,

Hopefully we will have a response to you on this one shortly. I don't know about your specific issue, but I can tell you that for the better part of this week we have had our guys on the ground in Atlanta with Jboss staff focusing on ICEfaces / Seam integration issues. They are back in the office today and pulling together the implimentation plan. Stay tuned we are hoping to post our ICEfaces / Seam roadmap in the next day or so.

Brian.

Adrian,

The root problem is that the server-side rendering is not being wrapped with the Seam context. When the server-side calls render(), none of the of Seam contexts are active, which produces either an NPE or "No active application scope", as in your case.

We do have some candidate fixes for this, but they didn't make it into the 1.5.3 release, as the 'proper' fix involves some fundamental changes to our ViewHandler, and this will take a bit more time. It's not certain whether we'll have a 1.5.4 release or not, but in any case, we'll have a 1.6 developer's beta out shortly, probably within a week or two.

Thanks,
Philip

Excellent Philip - thanks for the update.

I'll keep an eye out for the 1.6 release, so I can plug it in to my app and provide you with some feedback.

Cheers,
-Adrian

Possibly related issue:

When I bind a dataPaginator to my Seam component

Code:

 ...
 binding="#{filterableSearch.dp}"

the pagination breaks. The dp is set in the backing bean, but clicking on any of the paginator elements gives a

Code:

 ERROR [CachedConnectionValve] Application error: Blocking Servlet did not complete its transaction

Simply removing the binding makes the paginator work fine. I'm trying to fix an issue where I page down through my results, then filter the results, reducing the list, leaving me 'stranded' on an empty page (see http://www.icefaces.org/JForum/posts/list/3357.page).

Is the error part of the Seam/ICEFaces context collision too?

Note: the paginator related error noted above only appears when the Seam component is bound to the Seam.CONVERSATION context. If it is bound at the SESSION level, it works OK.