Hi Wendy, I read through your final thread - and obviously my javascript fix has only made it into 1.1.5 snapshot. If you found an example where h:form and t:commandLink work together, all is well - so you can get rid of the incompatibility sentence. Thanks for trying it out!
That property-not-found exception is something entirely different - someone changed an example there and didn't change the backing bean or the other way round, obviously. regards, Martin On 9/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
I copied the source and binary distributions to the right place for mirroring, and I'm waiting for Sean to fix permissions under m2-ibiblio-rsync-repository so I can get the jars into the Maven repository. In another thread [1], we're still working out the details of the release announcement. Anyone with knowledge of the JavaScript changes that may have made Core 1.1.4 incompatible with Tomahawk 1.1.3, please post over there and help us sort it out. I think the only thing left is to change the download page and post the announcement. [1] http://www.nabble.com/Release-Announcement-for-MyFaces-Core-1.1.4-t2275568.html -- Wendy
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
