RE: [Springframework-developer] RE: commons-validator adapter

[Brandon G. <ma...@ph...>]

This is not a bash struts thread. It worked for it's season. This is a
"please keep Spring focused" thread. Please, focus your comments towards
that effort.

Brandon

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Colin Sampaleanu
Sent: Tuesday, April 06, 2004 6:52 AM
To: spr...@li...
Subject: Re: [Springframework-developer] RE: commons-validator adapter

Putting on my pundit cap, some people might say the what Struts suffers 
most from is bad design :-)

Brandon Goodin wrote:

>This is exactly what I mean. Thanks Karl. I hope developers of Spring take
>what Karl is saying to heart. To me this is vitally important in keeping
the
>reality and perception of Spring light and focused. I would hate to see
>Spring suffer from what Struts suffers from... "fascination with gadgetry"
>or BSOS (Bright Shiny Object Syndrome)...distraction from what is
important.
>
>Any developers reading this?
>
>Brandon
>
>P.S. How are you doing Karl? :D Haven't talked to you since struts-chain. I
>bailed on it in hopes of what Spring is offering.
>
>-----Original Message-----
>From: spr...@li...
>[mailto:spr...@li...] On Behalf Of
>Baum, Karl
>Sent: Monday, April 05, 2004 8:33 PM
>To: spr...@li...
>Subject: Re: [Springframework-developer] RE: commons-validator adapter
>
>It's great that Spring offers a developer so many options, but after a
while
>it may be difficult to separate core Spring from the convenient add ons.
>What must a developer read up on before he or she understands what spring
is
>really about?  I would tend to side towards IOC, AOP, and the BeanFactory
>before the commons validator plugin, but this does not mean a commons
>validator plugin is not a great idea (I for one am trying to integrate it
>into my current project.).  Each plugin that is integrated directly into
the
>project is yet another responsibility for the community of Spring
developers
>when it comes to documentation and maintenance.  This documentation, with
>all of the add ons and plugins, will eventually become so bloated, the
>average developer may become overwhelmed by it's size and complexity.
>
>Why not farm these plugins out to smaller subprojects with teams of
>developers focused on delivering a specific add on to the Spring project.
>This leaves everyone with all of the great Spring options, but in the end
>the Spring Framework never loses site of it's purpose  This isn't just
about
>the commons validator project.  With each new popular open source
component,
>we will need yet another package checked into the Spring project.  We can
>start now with the spring-commons-validator subproject.
>
>----- Original Message -----
>From: "Brandon Goodin" <ma...@ph...>
>To: <spr...@li...>
>Sent: Monday, April 05, 2004 10:08 PM
>Subject: RE: [Springframework-developer] RE: commons-validator adapter
>
>
>  
>
>>I understand that. I'm simply saying... leave the choices on other
>>    
>>
>websites
>  
>
>>and focus on what spring is. Not on all the neat toys you can plug into
>>    
>>
>it.
>  
>
>>So, where do you draw the line on what does and does not get included. Why
>>not setup a directory of tools that can be used in spring instead of
>>    
>>
>feeling
>  
>
>>compelled to include support for every permutation into the distro or in
>>    
>>
>the
>  
>
>>spring cvs. Just cuz you can doesn't mean you should. I think moves like
>>this will cause confusion around spring not help it.
>>
>>B
>>
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...] On Behalf
>>    
>>
>Of
>  
>
>>Seth Ladd
>>Sent: Monday, April 05, 2004 5:29 PM
>>To: spr...@li...
>>Subject: Re: [Springframework-developer] RE: commons-validator adapter
>>
>>Brandon Goodin wrote:
>>    
>>
>>>commons validator? gack! Don't pollute spring with all of this crap. I
>>>don't want to see spring turn into the 8000 pound gorilla that struts
>>>has. Please consider making this stuff peripheral.
>>>      
>>>
>>A nice aspect of Spring is that it attempts to give developers different
>>choices for a particular task.  For validation, commons-validator is
>>just one choice.  Other choices include metadata validator or
>>programmatic validation.  IMHO, the commons-validator fills a nice
>>niche: when you want to do declarative validation but can't mark up the
>>source code (if, for example, you're using generated source or 3rd party
>>classes).
>>
>>With Spring, you get to Pick and Choose!
>>Seth
>>    
>>



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer