FYI, JSF 1.2 has a specified name for the state saving parameter for exactly this reason.
There's nothing to stop MyFaces from starting to use that parameter name right now, which would give convergence a head start. -- Adam On 4/3/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Ok. > > In 1.1.1 you're right, it would only work client side state saving. > That was fixed later on, and it worked with both methods. Then dojo > came in, and currently we support only server-side state saving. We > want to enable client-side again. > > Furthermore, it never worked on RI with client-side state saving, > cause the state saving parameter names on client-side are different > there. > > regards, > > Martin > > On 4/3/06, Ricardo Tercero Lozano <[EMAIL PROTECTED]> wrote: > > I've tested this component in sandbox.jar for myfaces 1.1.1 and it only > > works with client save state method. Otherwise navigator complaints about a > > non existent jsf_tree_64 variable. > > > > Ricardo. > > > > > > On 3/31/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > > On 3/31/06, Murat Hazer <[EMAIL PROTECTED]> wrote: > > > > Is there any wiki entry about how to do this? > > > > > > http://wiki.apache.org/myfaces/Building_With_Maven > > > > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
