Hi, @Thomas - the changes you have introduced will affect one thing, and that's back-button on server-side state saving. I do believe this is important enough to release a new core as well.
@Wendy: I've commented on TOMAHAWK-713 - I currently don't see why this is failing, I hope Jeff will investigate some more. Apart from that, I've tried to fix whatever I saw possible of whatever compatibility problems with former MyFaces-versions remained. Of course, with the recent changes of Thomas, we still have the problems as pointed out above. The problem is that currently a lot of stuff is moving around, and this for compatibility reasons. I believe this will be for the best of everyone in the end, but currently it's all a major mess. regards, Martin On 10/10/06, Thomas Spiegl <[EMAIL PROTECTED]> wrote:
The point is that the next tomahawk release will require MyFaces Core >= 1.1.5. On 10/9/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 10/9/06, Thomas Spiegl <[EMAIL PROTECTED]> wrote: > > > The order is important. We will need to release core before tomahawk. > > Fine, but that wasn't the important question. :) > > I know we're breaking compatibility somewhere because of the > JavaScript changes, but I'm not sure exactly where the break is. > > Are we saying that the next Tomahawk will not work with MyFaces 1.1.4? > > -- > Wendy > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
