Yes,

Martin changed on head the name of the "getScrolling()" function to
"org_apache_myfaces_getScrolling()" (JS function). So, Tomahawk post
1.1.4 (means 1.1.5-SNAPSHOT and following) don't render that
"getScrolling()" but the myfaces pre 1.1.5 (like 1.1.4 snapshot) does.

That was the reason for this JS error, you and me got.

I patched the 1.1.4 branch; so now 1.1.4 core works with
tomahawk 1.1.5-Snap
and tomahawk 1.1.4-SNAP (after you compile it against the *patched* shared_203)

-Matthias

On 8/3/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
I agree with Mike here.  Matthias, can you explain the problem in more
detail?  We should fix this problem before releasing (if there's a
problem to fix.)

Sean

On 8/3/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> On 8/3/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > > As for the getScrolling issue, I could've sworn this worked in the
> > > latest simple examples *before* I switched in the rc core api jars.
> > > Maybe I'm wrong though ... I will try to investigate further.
> >
> > with 1.1.5 yes; the getScrolling is now named 
"org_apache_myfaces_getScrolling"
> > that was committed against head (tom., core and shared)
> >
> > so, 1.1.4 + tomahawk 1.1.5 won't work
>
> Hold up here!   Unless there's no other way to solve this, we should
> not be breaking behavior like this.    We've been advertising that any
> post-1.1.3 core works with any post-1.1.3 tomahawk.
>
> Furthermore, there shouldn't be any dependencies on the MyFaces
> implementation from Tomahawk (otherwise it'll also break in the RI).
>



--
Matthias Wessendorf

further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Reply via email to