Unfortunately, we weren't requiring JIRA issues with every change last June.
The following commit log is the best you can do for seeing what happened to make Tomahawk 1.1.4 compatible with the RI. http://svn.apache.org/viewvc?view=rev&revision=422260 On 1/31/07, Bharath Belagodu <[EMAIL PROTECTED]> wrote:
Jeff, Appreciate the response. Well, the website is not reachable at this time to download 1.1.4 but I had an older copy of tomahawk 1.1.4 downloaded about 4wks ago, that seemed to work with JSF 1.2. The basic problems with commandLink, panelNavigation2 aren't occurring. Where can I find the differences between the two releases? When is tomahawk 1.1.4 going to be released? Appreciate pointers to any URLs. The problem went away but would be good to know what the problem is with tomahawk 1.1.3! Thanks. -Bharath -----Original Message----- From: Jeff Bischoff [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 31, 2007 3:03 PM To: MyFaces Discussion Subject: Re: Javscript Issues with JSF 1.2, Tomahawk 1.1.3 Bharath, Offhand, I can tell you there were some javascript changes to improve compatibility since Tomahawk 1.1.3. Some of the devs like Martin would know more on this. Just to narrow down which versions your problem is affecting, can you also try with Tomahawk 1.1.4 rc from here [1] and Tomahawk 1.1.5 nightly from here [2]? [1] http://people.apache.org/builds/myfaces/tomahawk-1.1.x/ [2] http://people.apache.org/builds/myfaces/nightly/ Regards, Jeff Bischoff Kenneth L Kurz & Associates, Inc. Bharath Belagodu wrote: > Using JSF 1.2 with Tomahawk 1.1.3 is causing issues with several of the > components developed in our application. The dynamic menus and static > menus developed using panelNavigation2 aren't working. There is > javascript error detected. The javascript error is 'Object Expected'. > So, I set to explore just a simple example of a commandLink. > > > > The below code has an error, I'm using the tomahawk's commandLink > component. > > > > <t:commandLink action="welcome"> > > <f:verbatim>› </f:verbatim> > > <t:outputText value="Test Client" /> > > </t:commandLink> > > > > Changing the t:commandLink to h:commandLink works. > > > > Is tomahawk 1.1.3 not compatible with JSF 1.2? Previously we were using > myfaces-1.1.4 and it worked great. > > > > > > Also, another strange behavior with JSF 1.2 is that our xhtml files > appear as raw files when being displayed in Mozilla browser, if I use IE > 6 or IE 7 there isn't an issue. This wasn't the case with myfaces1.1.4. > > > > Thanks. > > > > -Bharath > > > >
