RE: [Resources] XMLMessageResources and Proposal

Oh, one thing I forgot to mention. Not sure if we overlooked it, but I was wondering how are you handling special (XML/HTML) character data? Especially for Struts (errors.header and errors.footer) One peice of functionality that I am adding will (for the most part) take care of that in a clean

RE: [Resources] XMLMessageResources and Proposal

> -Original Message- > From: Eddie Bush [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 3:58 PM > To: Struts Developers List > Subject: Re: [Resources] XMLMessageResources and Proposal > > > James Mitchell wrote: > > >I'm involved in this as a way to help others and add to list

RE: [Resources] XMLMessageResources and Proposal

That's exactly what I want to know. Whether this is needed. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org > -Original Message- > From: Eddie Bush [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 3:41 PM > To: Struts Developers List > Subje

RE: [Resources] XMLMessageResources and Proposal

Yeah, Since it is Friday I'll just step up and toss my own 0.02 into the mix. When one is learning patterns everything looks like a pattern. I went through this syndrome. The kama sutra could be considered a book of patterns, and its' much older than the gang of four. But these days I whe

Re: [Resources] XMLMessageResources and Proposal

James Mitchell wrote: >I'm involved in this as a way to help others and add to list of >functionality provided by this framework. Personally, I prefer >DBMessageResources. (You'll see why when I finish the Management Tool for >it) > >This topic has been discussed many times, over many months, a

Re: [Resources] XMLMessageResources and Proposal

I was reading a thread last night somewhere off in bozo-land where this fellow was trying *so* hard to "shove" patterns into his design it was hillarious. I won't go into details - but shove is an appropriate description. Sometimes, people want so badly to use a "new thing" that ... well they

RE: [FRIDAY] [Resources] XMLMessageResources and Proposal

Now I know it's Friday. ;-) > -Original Message- > From: James Turner [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 12:40 PM > To: Struts Developers List > Subject: Re: [Resources] XMLMessageResources and Proposal > > > At 03:33 PM 10/11/2002, Antoni Reus wrote: > >A Diven

Re: [Resources] XMLMessageResources and Proposal

At 03:33 PM 10/11/2002, Antoni Reus wrote: >A Divendres 11 Octubre 2002 20:56, MARK va escriure: > > Why use xml for the message resources in the first place? Using XMl doesnt > > add any inherent value. The properties file is fine, easy to use/read, and > > XML is way too wordy, constricting.

RE: [Resources] XMLMessageResources and Proposal

> -Original Message- > From: MARK [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 11:57 AM > To: Struts Developers List > Subject: RE: [Resources] XMLMessageResources and Proposal > > > Why use xml for the message resources in the first place? > Using XMl doesnt add any i

RE: [Resources] XMLMessageResources and Proposal

I'm involved in this as a way to help others and add to list of functionality provided by this framework. Personally, I prefer DBMessageResources. (You'll see why when I finish the Management Tool for it) This topic has been discussed many times, over many months, and it has become apparent (to

RE: [Resources] XMLMessageResources and Proposal

LOL James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org > -Original Message- > From: Antoni Reus [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 3:33 PM > To: Struts Developers List > Subject: Re: [Resources] XMLMessageResources and Proposal > > > A

RE: [Resources] XMLMessageResources and Proposal

> -Original Message- > From: Martin Cooper [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 2:29 PM > To: 'Struts Developers List'; Commons Developers List > Subject: RE: [Resources] XMLMessageResources and Proposal > > > > -Original Message- > > From: James Mitchell [ma

Re: [Resources] XMLMessageResources and Proposal

A Divendres 11 Octubre 2002 20:56, MARK va escriure: > Why use xml for the message resources in the first place? Using XMl doesnt > add any inherent value. The properties file is fine, easy to use/read, and > XML is way too wordy, constricting. Seems like its not advantageous to me, > perhaps I

cvs commit: jakarta-struts/src/share/org/apache/struts/util StrutsValidator.java

rleland 2002/10/11 12:22:58 Modified:src/share/org/apache/struts/util StrutsValidator.java Log: Buzilla [10191] Allow Ranges for Floating point numbers Revision ChangesPath 1.9 +50 -1 jakarta-struts/src/share/org/apache/struts/util/StrutsValidator.java

DO NOT REPLY [Bug 10191] - Validator Range Checking Bug

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

cvs commit: jakarta-struts/web/validator/WEB-INF validation.xml

rleland 2002/10/11 12:13:42 Modified:web/validator jsType.jsp type.jsp web/validator/WEB-INF validation.xml Log: Add example of using add intRange & floatRange validation Revision ChangesPath 1.2 +10 -1 jakarta-struts/web/validator/jsType.jsp

cvs commit: jakarta-struts/src/validator/org/apache/struts/webapp/validator ApplicationResources.properties ApplicationResources_fr.properties TypeForm.java

rleland 2002/10/11 12:13:17 Modified:src/validator/org/apache/struts/webapp/validator ApplicationResources.properties ApplicationResources_fr.properties TypeForm.java Log: Add example of using add intRange & floatRange validation

cvs commit: jakarta-struts/conf/share validator-rules.xml

rleland 2002/10/11 12:12:26 Modified:conf/share validator-rules.xml Log: Bug [10191] add intRange & floatRange validation fo floating point numbers can be bounded. Revision ChangesPath 1.9 +87 -0 jakarta-struts/conf/share/validator-rules.xml Index: val

DO NOT REPLY [Bug 13544] - [exception] support contextRelative paths

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13544] - [exception] support contextRelative paths

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13544] - [exception] support contextRelative paths

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13544] New: - [exception] support contextRelative paths

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

RE: [Resources] XMLMessageResources and Proposal

Why use xml for the message resources in the first place? Using XMl doesnt add any inherent value. The properties file is fine, easy to use/read, and XML is way too wordy, constricting. Seems like its not advantageous to me, perhaps Im missing something. There is already a tool that builds

Re: [VOTE] New Struts Committer: Eddie Bush

Ah - I see. Thanks for the clearification. I guess I missed reading part of that. My guess is that you're getting that from the roles page: Once a Contributor is nominated, all of the Committers for a subproject will vote. If there are at least 3 positive votes and no negative votes, the

Re: [VOTE] New Struts Committer: Eddie Bush

The list of committers is on the Who We Are page. There's no set TTL, and technically all the Committers are suppose to vote (eventually). Everything that's spelled out is in the guidelines on the Jakarta site. Suprisingly little really, but we get by somehow. -T. Eddie Bush wrote: > Is Mar

RE: [Resources] XMLMessageResources and Proposal

> -Original Message- > From: James Mitchell [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 8:33 AM > To: Struts Developers List; Commons Developers List > Subject: [Resources] XMLMessageResources and Proposal > > > Martin (and others) > > On a suggestion by Craig, I had a

Re: [VOTE] New Struts Committer: Eddie Bush

Is Mark a committer? I couldn't find any correlation to make a determination. If he is, then I suppose I'm voted in? Craig + Mark + Rob == +3 == magic #? MARK wrote: >+1 > >*** REPLY SEPARATOR *** > I'm guessing the answer is, "No :-(". That being the case, the suspense of

RE: Basic Issues

On Fri, 11 Oct 2002, edgar wrote: > > I need checkboxes for booleans that really work. > Don't forget to set the corresponding boolean property (in your form bean) to false in the reset() method, as the documentation tells you to do. Craig -- To unsubscribe, e-mail:

Re: Basic Issues

On Fri, 11 Oct 2002, edgar wrote: > Date: Fri, 11 Oct 2002 08:07:43 -0400 > From: edgar <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: 'Struts Developers List' <[EMAIL PROTECTED]> > Subject: Basic Issues > > I have found that the basic

RE: Basic Issues

On Fri, 11 Oct 2002, Daniel Honig wrote: > Date: Fri, 11 Oct 2002 11:40:18 -0400 > From: Daniel Honig <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: Struts Developers List <[EMAIL PROTECTED]> > Subject: RE: Basic Issues > > This is the correct view in IMHO. AT

RE: Basic Issues

I was serious about turning off JS. Many people do this to avoid the popup adds. JS validation should be viewed as an extra feature, not a required one. Of course, if your site is highly specialized with dhtml you would js required but most apps don't fit this description. Dave >From: "Ta

RE: Basic Issues

If there is an interest I could make the tags I have worked up a little more locale independent, minimize the javascript, and based on 1.1 and donate them. Assumes the get /set methods would return a java date. Assumes a BigDecimal

Re: Basic Issues

Preach it, brother :-) David Graham wrote: > Struts does not need a date formatting tag because the JSTL already > has one. It's called (surprise) formatDate. > > What happens to your js date formatting when I turn off javascript? > > Dave -- Eddie Bush -- To unsubscribe, e-mail:

RE: Basic Issues

Thanks for pointing out that the JSTL has a similar feature-- I've been trying to get the front-end guys around here interested in JSTL, maybe this will help. Turn off JS? LOL ;) My point was that the back-end developer should be in the business of providing a stable framework of data that the

RE: Basic Issues

But what about having another component that can be specified as an attribute to an input tag as the converters I mentioned in a previous post? This is more like what Jason is talking about. What's in the JSTL is probably useful for display only. The converter concept can be made useful bi-dire

RE: Basic Issues

This is the correct view in IMHO. ATG had an interesting feature called "converters" the converter could be specified on the element that was being displayed as in I've scrathed and itched a few times before wishing for this in Struts. It was quick easy and de-coupled. It worked well eno

RE: Basic Issues

Struts does not need a date formatting tag because the JSTL already has one. It's called (surprise) formatDate. What happens to your js date formatting when I turn off javascript? Dave >From: "Taylor, Jason" <[EMAIL PROTECTED]> >Reply-To: "Struts Developers List" <[EMAIL PROTECTED]> >To: "'

RE: Basic Issues

Why not use the i18n tags in the JSTL? Make use of Java's wonderful i18n module. -Original Message- From: Taylor, Jason [mailto:[EMAIL PROTECTED]] Sent: 11 October 2002 16:32 To: 'Struts Developers List' Subject: RE: Basic Issues I disagree with the idea that JavaBeans should handle dat

[Resources] XMLMessageResources and Proposal

Martin (and others) On a suggestion by Craig, I had a look at the commons resources XMLMessageResources. It appears (and I could be wrong) that this implementation expects a structure similar to this: (I couldn't find any samples or test data, so I just guessing by browsing the code) Some Va

RE: Basic Issues

I disagree with the idea that JavaBeans should handle date formats, and I think it is a good example of mixing view and model components-- of confusing the roles of front- and back-end developers. Date formats and the like are better left to the front-end developer since they are UI elements an

RE: Basic Issues

To create complex interfaces with many levels the nesting stuff breaks down i.e. focus doesn't work, event driven JavaScript is almost impossible to write (the field names are 'invalid' JavaScript). Even with the custom tags it is messy as depending upon how the java code is organized you need di

Basic Issues

I have found that the basic functionality of the tag library classes to be limited (I assume by design) , and I have found myself writing replacement tags for quite a number of things. I.E. In order to have a relatively simple date interface (avoid very complex javascript in every jsp) the logica

Re: Basic Issues

Well, for validation features such as javascript, you should look at the validator and its rules xml file. You can expand on the date handling javascript there, and by using the validatorform you can define fields to be of type date and apply client/server side validation rules. Regards, Mark

Re: Basic Issues

Others have responded to you with some comments. But I find that I don't know what problem you have. What functionality is it that you need that requires new tags or complex JavaScript? edgar wrote: > I have found that the basic functionality of the tag library classes to > be limited (I assume

Re: Basic Issues

I would suggest that this type of functionality be placed in a JavaBean rather than a tag. I idea is that it is really not up to the page to decide in what format a date is displayed. That's really a business requirement that you would want to enforce on the Web presentation tier, or a PDF pre

Re: DBMessageResources - It's finally finished.

James Mitchell wrote: > What is it? > --- > If you've followed recent discussions on the struts-user list. There has > been a flurry of discussion over getting ApplicationResources messages from > a database. Well done James! > - Changes are immediately available to your application,

DO NOT REPLY [Bug 13530] New: - submit tag doesn't work with "indexed" attribute

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b