Tapestry 4.0 FormSupport.render(String method, IRender informalParametersRenderer, ILink link, String scheme); Tapestry 4.0.1 FormSupport.render(String method, IRender informalParametersRenderer, ILink link, String scheme, Integer port);
Is changing a method signature appropriate for a bug-fix maintenance release? These things aren't caught by a compiler since the pages are assembled at runtime. I found this particular problem when a page containing an Tacos Ajax component was loaded and it produced a java.lang.NoSuchMethodError. Does anybody have a list of changed method signatures in the T4.0.1 version? Does anybody know whether Tacos is being tested with the T4.0.1 version? Thanks, David Harvey Ingenix, Inc. "Secure Server GDV" made the following annotations on 04/06/2006 08:29:36 PM ------------------------------"This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately." ============================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
