DO NOT REPLY [Bug 27765] - JavascriptValidatorTag renders all staticJavaScript methods

2004-03-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27765. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 27765] - JavascriptValidatorTag renders all staticJavaScript methods

2004-03-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27765. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 27765] - JavascriptValidatorTag renders all staticJavaScript methods

2004-03-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27765. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 27765] - JavascriptValidatorTag renders all staticJavaScript methods

2004-03-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27765. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: Tagging and freezing (was Re: Bug in JavascriptValidatorTag)

2004-02-27 Thread Ted Husted
On Thu, 26 Feb 2004 10:54:49 -0800 (PST), Martin Cooper wrote: On Wed, 25 Feb 2004, Joe Germuska wrote: Perhaps this is understood, but I'm assuming that we also want to say that the RM owns the release tags for the release he or she is managing, and only the RM should *ever* move the tags?

Re: Tagging and freezing (was Re: Bug in JavascriptValidatorTag)

2004-02-27 Thread Craig R. McClanahan
Quoting Martin Cooper [EMAIL PROTECTED]: On Wed, 25 Feb 2004, Joe Germuska wrote: Perhaps this is understood, but I'm assuming that we also want to say that the RM owns the release tags for the release he or she is managing, and only the RM should *ever* move the tags? It's never been

Re: Tagging and freezing (was Re: Bug in JavascriptValidatorTag)

2004-02-26 Thread Martin Cooper
On Wed, 25 Feb 2004, Joe Germuska wrote: Perhaps this is understood, but I'm assuming that we also want to say that the RM owns the release tags for the release he or she is managing, and only the RM should *ever* move the tags? It's never been stated as such, but that's not a bad idea at

Re: Bug in JavascriptValidatorTag

2004-02-25 Thread Ralph Schaer
Thanks for fixing that. But there is still a problem. (Nightly Build 2004/02/25) You can see the error in the struts-example web application. There is a staticJavascript.jsp page with this content %@ page language=java % %-- set document type to Javascript (addresses a bug in Netscape according

Re: Bug in JavascriptValidatorTag

2004-02-25 Thread Joe Germuska
At 7:23 PM +0100 2/25/04, Ralph Schaer wrote: Thanks for fixing that. But there is still a problem. (Nightly Build 2004/02/25) You can see the error in the struts-example web application. Hm. I don't believe that that's been changed in any of the last few revisions. Please file this in Bugzilla;

Re: Bug in JavascriptValidatorTag

2004-02-25 Thread Ralph Schaer
this bug was introduced with revision 1.45 from 2004/02/04 in JavascriptValidatorTag.java you find the working code in revision 1.44. method renderJavascript. StringBuffer results = new StringBuffer(); ModuleConfig config = TagUtils.getInstance().getModuleConfig(pageContext);

Tagging and freezing (was Re: Bug in JavascriptValidatorTag)

2004-02-25 Thread Martin Cooper
I almost didn't read this thread, based on the subject line, but I'm rather glad that I did, given how far the subject has strayed... There is still a need for a freeze after tagging. While it's not quite as essential as with our previous release process, it's still important. Here's why. The

Re: Bug in JavascriptValidatorTag

2004-02-25 Thread Joe Germuska
At 9:08 PM +0100 2/25/04, Ralph Schaer wrote: this bug was introduced with revision 1.45 from 2004/02/04 in JavascriptValidatorTag.java OK; that makes sense. But that was when I was trying to get it to throw an exception when there was no such form instead of just spewing the static javascript

Re: Tagging and freezing (was Re: Bug in JavascriptValidatorTag)

2004-02-25 Thread Joe Germuska
So, at least as long as folks are happy with me as the RM, please allow me the leeway of a short freeze period between tagging and releasing the build, so that I can do the job as best I can. I don't think that should be too onerous. Fair enough: being RM is a lot of work, I'm sure, and we should

Re: Bug in JavascriptValidatorTag

2004-02-24 Thread Joe Germuska
Hm. No one brought that up when we were talking about implementing the fix, but that explains the old default behavior, which was to render the javascript without wrapping script tags. That makes sense when you're rending javascript for external use. It seems to me that the solution would be

Re: Bug in JavascriptValidatorTag

2004-02-24 Thread [EMAIL PROTECTED]
Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 02:03 PM To: 'Struts Developers List' Subject: Re: Bug in JavascriptValidatorTag Hm. No one brought that up when we were talking about implementing the fix, but that explains the old default behavior

Re: Bug in JavascriptValidatorTag

2004-02-24 Thread Joe Germuska
At 6:28 PM + 2/24/04, [EMAIL PROTECTED] wrote: Once a release is tagged that's it. We could retag and do 1.2.1, however there will probably be other things that need to be fixed. The point is to get 1.2.0 out the door and then see about making whatever fixes that need to happen. Well, if it's

Re: Bug in JavascriptValidatorTag

2004-02-24 Thread Ted Husted
Yes, under the current process, there little reason to have a real freeze. It's more like a heads-up now. AFAIC, the codebase should not be considered frozen now, and people can start applying fixes to go into 1.2.1, including the license thing. The only reason we're not starting a vote on the

Bug in JavascriptValidatorTag

2004-02-23 Thread Ralph Schaer
I've found a bug in JavascriptValidatorTag.java. (Nightly build 2004/02/23) I use this tag in one of my jsp pages: html:javascript dynamicJavascript=false staticJavascript=true/ Now the JavascriptValidatorTag crashes with this error message: javax.servlet.jsp.JspException: No form found under name

DO NOT REPLY [Bug 26782] - JavaScriptValidatorTag produces invalid JavaScript function name when form is subclass of ValidatorActionForm

2004-02-14 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26782. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 26782] - JavaScriptValidatorTag produces invalid JavaScript function name when form is subclass of ValidatorActionForm

2004-02-13 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26782. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 16653] - JavascriptValidatorTag doesn't throw explicit NPE if ValidatorResources not found

2003-12-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16653. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

RE: DO NOT REPLY [Bug 21560] - JavascriptValidatorTag creates invalida javascript method name when validating using action path in formName

2003-07-22 Thread Steve Raeburn
-Original Message- From: Kurt Post [mailto:[EMAIL PROTECTED] Sent: July 21, 2003 3:04 PM To: Struts Developers List Subject: RE: DO NOT REPLY [Bug 21560] - JavascriptValidatorTag creates invalida javascript method name when validating using action path in formName I was working

DO NOT REPLY [Bug 21560] - JavascriptValidatorTag creates invalida javascript method name when validating using action path in formName

2003-07-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21560. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

RE: DO NOT REPLY [Bug 21560] - JavascriptValidatorTag creates invalida javascript method name when validating using action path in formName

2003-07-21 Thread Kurt Post
Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, July 21, 2003 4:57 PM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 21560] - JavascriptValidatorTag creates invalida javascript method name when validating using action path in formName DO NOT REPLY TO THIS EMAIL

DO NOT REPLY [Bug 16653] - JavascriptValidatorTag doesn't throw explicit NPE if ValidatorResources not found

2003-02-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16653. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 16653] - JavascriptValidatorTag doesn't throw explicit NPE if ValidatorResources not found

2003-01-31 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16653. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.