PrimeFaces 3.X does not work with Spring Webflow

This really needs some attention, see this thread and this google issue for full details.

Spring Webflow contains a simple sample app, booking-faces, which works well with PrimeFaces 2.2.1, but fails with PrimeFaces 3.X. I've tried it with the latest Spring versions as well, in which PrimeFaces 3.X still fails. It seems somehow to step on the webflow context.

The sample apps all demonstrate this clearly, and may be found here.

-SM

Hello,

I encourage you to try to generate a project on www.springfuse.com
You will get a project that works with primefaces 3.1, SpringWebFlow 2.3.0 and Spring 3.0.5
(make sure you keep the springdata option checked)

Note: it generates a patched version of 'FlowFacesContext' to circumvent https://jira.springsource.org/browse/SWF-1467

I hope this will help you.

Nicolas.

[optimus.prime]

I think SpringFuse is the best choice if your stack has SWF-PrimeFaces.

This is the first clue I have received on why PF does not work with Webflow, thank you. On the face of it, it seems germane, as it has to do with FlowFacesContext. Note however that, in the many examples provided, PF is failing with JSF 2.0.8 and JSF 2.0.3, not the JSF 2.1 referenced in the Spring Jira (which has it's own issue).

I will look at this and report back,

-SM

P.S. Optimus, have you run one of my sample apps?

I've had a look at SpringFuse, which seemed to have a lot of extra pomage that I shouldn't need, as well as being downrev from the components I'm using. It was, however on jsf 2.1.6, and had the webflow patch, so I ported the WebFlow example to that, with the same result: PrimeFaces 2.2.1 works with Spring WebFlow, PrimeFaces 3.1 (and 3.1.1) both fail.

Please, optimus, have a look at the sample apps I posted. I've followed all the guidelines for seeking help on a problem, and followed up on the indications given: the erroneous behavior is consistent. The only thing not working is PrimeFaces 3.X.

Have a look at the sample app,

-SM

P.S. Note also, to deal with jsf 2.1.x, I added

<dependency>
<groupId>org.glassfish.web</groupId>
<artifactId>javax.el</artifactId>
<version>2.2.3</version>
</dependency>

Updated Google code issue 3551 with clear examples. Nothing done here to upgrade PrimeFaces to 3.x should cause Spring WebFlow to fail like this.

Optimus, please look at the samples, they are clear and simple to use,

-SM

[optimus.prime]

If PrimeFaces pagination works without SWF and fails with SWF then what causes the problem should be clear. It is up to SWF to update to support PrimeFaces 3. Not the other way around. Spring ROO constantly updates itself with each PrimeFaces release.

Really?!!!!

Pagination works with 2.x, but not with 3.x. SWF didn't break, PF did, didn't it?! If not, how can this somehow be SWF's fault? How do I even file a bug with SWF?

Do developers have to choose between SpringWebFlow and PrimeFaces? Do they have to choose using only downrev PrimeFaces?

But, most importanly, Optimus, did you look at the sample app?

-SM

[optimus.prime]

If not, how can this somehow be SWF's fault? How do I even file a bug with SWF?

https://jira.springsource.org/browse/SWF

Tell project lead Rossen(a friend of mine) that SWF is not compatible with PrimeFaces 3.x. He can take care of this.

Glad were all freinds here. Did you look at the sample app?

-SM