RichFaces 3.1.3 and StateManager

On Thu, 2008-05-08 at 16:12 +0200, mario.buonopane@... wrote:
> Hi, in my application i’m using Myfaces/Tomahawk 1.1.5 and RichFaces
> 3.1.3. RichFaces configures a Phase Listener
> (<phase-listener>org.ajax4jsf.event.InitPhaseListener</phase-listener>) that force to use his StateManager (org.ajax4jsf.application.AjaxStateManager). So, I can use the Myfaces default StateManager (org.apache.myfaces.application.jsp.JspStateManagerImpl).
>
> Can this cause some problem to the Myfaces/Tomahawk components? Is
> there any Myfaces/Tomahawk component that does not work without
> Myfaces State Manager?

I don't think there are any major show-stoppers in using a state-manager
implementation that is not the myfaces one. The state manager interface
is part of the JSF specification and I would certainly hope that none of
the core components are using anything other than the standard apis to
interact with it.

There are of course a couple of special myfaces exensions that won't
work but they are not critical.

And Tomahawk runs on Sun's JSF implementation which has a completely
different state-manager implementation, so tomahawk should be fine.

You *might* find that tomahawk's t:aliasBean won't work with component
bindings. It does require some support that exists only in myfaces (and
not in sun); I cannot currently remember whether that was a hack in the
state manager or not (I think it is actually in the view handler..).

If you google, I would think you will find info about people using
myfaces + RichFaces. It's not an unusual combination. I think there are
a few issues but don't know the details as I haven't used RichFaces
myself.

Regards,
Simon