@SHALE-442
Hi. I want to fix this bug 442 and want to ask some question here about doing that, if thats ok, i'll hope so. I'll fixed the decorator not to apply shales validator renderer if the renderer family matches the ajax stuff, which let them work again. However this seams not the ultimate approach to me because there are so many different familys and renderers which should not be decorated, that i'll have to code everytime they change. Are there any suggestions or ideas (already) how this should be done the right way? Torsten smime.p7s Description: S/MIME cryptographic signature
@SHALE-442
Hi. I want to fix this bug 442 and want to ask some question here about doing that, if thats ok, i'll hope so. I'll fixed the decorator not to apply shales validator renderer if the renderer family matches the ajax stuff, which let them work again. However this seams not the ultimate approach to me because there are so many different familys and renderers which should not be decorated, that i'll have to code everytime they change. Are there any suggestions or ideas (already) how this should be done the right way? Torsten smime.p7s Description: S/MIME cryptographic signature
[OT] Re: @SHALE-442
Am Dienstag, 1. April 2008 schrieb Torsten Krah: WARNING: bad headers - Duplicate header field: Reply-To Something off-topic, i'll wrote the mail 3 times now and 2 got not delivered because the list produces invalid mail headers (it inserts a reply-to header instead of replacing the existing one, in the end the mail gots 2 of them which is not valid). http://shale.apache.org/mail-lists.html does not tell me whos responsible and where should i mail this problem to, can anyone help? Torsten smime.p7s Description: S/MIME cryptographic signature
Re: [OT] Re: @SHALE-442
We got the mail three times - at least I did :-) On Tue, Apr 1, 2008 at 1:37 AM, Torsten Krah [EMAIL PROTECTED] wrote: Something off-topic, i'll wrote the mail 3 times now and 2 got not delivered because the list produces invalid mail headers (it inserts a reply-to header instead of replacing the existing one, in the end the mail gots 2 of them which is not valid). As for that specific problem I have no idea what to do about it. Sorry. http://shale.apache.org/mail-lists.html does not tell me whos responsible and where should i mail this problem to, can anyone help? You can try [EMAIL PROTECTED], but I'm not sure who that will go to. Hopefully somebody else on this list will know how to address your problem. I'm glad you didn't just machine gun the send button though :-) Greg
