ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I'd like to be able to select multiple rows from a datatable and drag the set of selected rows to another table.

I have drag and drop working just fine, but the draggable thing is a single field (not the entire row) and I'm only dragging one at a time.

Any ideas?

Cheers,
-Adrian

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.

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?

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

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)

It looks like the Seam team have just implemented their own fileUpload tag, which just avoids the issue. It seems it's not the fileUpload but the progress bar that's the issue. I also assume that any ICEFaces components what instigate a server-driven render will fail for the same reason (I'm in the process of trying this out).

In the Seam forum here - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994349#3994349 - it says this 'known bug' was reported back to the icefaces team in Dec. Any solutions?

Cheers,
-Adrian