I've answered on the other thread. regards,
Martin On 9/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 9/17/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > When you told me that you reverted the getScrolling stuff, I > remembered that I also changed the name of the clear..._formName() > method. Now if old tomahawk 1.1.3 components expect to call this > clear-method, they'd have a java-script exception. > > So essentially - if you use an h:form and a t:commandLink, you should > see this exception, apart from that, you should be safe. I found the <h:form>...<t:commandLink> construct in a few of the 'simple' examples: forceId.jsp, dataTable.jsp, dataScroller.jsp, countryTableForm.jsp. Clicking around [1], I don't see any JavaScript errors [2]. Searching across the Tomahawk 1.1.3 'core' module for the word 'clear' doesn't turn up anything that looks suspicious to me. What can I do to provoke the exception? I'd like to be sure that Core 1.1.4 is really incompatible with Tomahawk 1.1.3 before we announce it that way. Maybe we can soften the statement to 'some components' or 'the xxx component' ? [1] the myfaces-example-simple app built with Core 1.1.4 and Tomahawk 1.1.3 [2] I do see a PropertyNotFound exception: http://wiki.wsmoak.net/cgi-bin/wiki.pl?MyFacesCore114#propnotfound -- Wendy
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
