-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As I see in JIRA, this bug should be fixed in 4.1.3 As it is quite a critical bug to us, what can we do to fix it? Would it make sense to patch against 4.1.2?
How can I make such a patch? Regards Bastian Voigt Bastian Voigt wrote: > [EMAIL PROTECTED] wrote: >> Bastian, > >> please have a look at >> https://issues.apache.org/jira/browse/TAPESTRY-1556 . >> Maybe you can temporarily work around this by toying with your form-id >> and their specification on the EventListener annotation. > > I have temporarily worked around this bug by duplicating my component class. > >> Maybe you can add your problem with source-code, if possible, to that >> issue. That would definitively be helpful! > > Hmm, it might be difficult to reproduce this bug in a testing > application, but I will try if I find the time. > - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - -- Bastian Voigt Neumünstersche Straße 4 20251 Hamburg telefon +49 - 40 - 67957171 mobil +49 - 179 - 4826359 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlKmI9+lAHD7HULYRAmrQAJ0SXYTUtZ3Zb2cK+vU8sKwKCQJ5dwCdEHhj O5sGOd3P+7LBAi+o69GNizs= =wizN -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]