Overriding SeamPhaseListener, still possible in Seam 2?

[robjellinghaus]

In Seam 1.2 and prior, you could specify your own PhaseListener in faces-config.xml, which could delegate to SeamPhaseListener internally. I relied on this when doing the Seam/GWT/JSF integration demoable here:

http://unrealities.com/seamgwt

Seam 2.0.0 installs SeamPhaseListener internally, so this overriding isn't possible, with tragic consequences for my stuff:

http://blog.robjsoftware.org/2007/11/gwtjsf-broken-with-seam-2-sorry-folks.html

Is there any way around this? If there were, it would be a quick fix, which would make my life rather better right now.

I suspect that the right thing would actually be to refactor the GWTJSF code so that it can optionally use the Seam resource servlet, and to tweak the GWTToSeamAdapter slightly to let it use a component name that is not necessarily the same as the service interface name. Then the GWTJSF code could go through almost the same remoting path as the current GWT remoting example, which would obviously be a win. But getting that to work is going to be moderately hairy.

Anyway, all thoughts appreciated.
Cheers,
Rob

[pmuir]

AFAIK, no. What are you doing in the phase listener? I can try to help you through, but you'll need to post code (I'm traveling atm so can't guarantee a quick response)

[robjellinghaus]

See my blog post above, it links to an article that has the code. Or just look here:

http://unrealities.com/seamgwt/article_0.2.html#How_does_the_current_project_integrate

Don't sweat it too much, I am pretty sure the current GWTJSF code could be simplified a lot to work with the existing Seam/GWT remoting. It'll just take time.

Cheers,
Rob