commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Cooper" <martin.coo...@tumbleweed.com>
Subject RE: [lang] Proposal for *NEXT* version
Date Tue, 08 Oct 2002 06:42:23 GMT


> -----Original Message-----
> From: Juozas Baliuka [mailto:baliuka@centras.lt]
> Sent: Monday, October 07, 2002 11:15 PM
> To: Jakarta Commons Developers List
> Subject: Re: [lang] Proposal for *NEXT* version
> 
> 
> Hi,
> I do not think dependency on top level project is any problem 
> for commons
> component, if public API  does's not have classes or 
> interfaces from this
> project.

I disagree. Commons Lang should sit as close to the JDK as possible - that's
really what it's all about. If it starts depending on other packages, then
it seems to me that it no longer meets its design goals.

> Projects like BCEL , ORO, Lucene are very good and solve 
> common problems
> too.

Sure, but they do not - and should not - relate to Commons Lang.

--
Martin Cooper


> 
> > > > The DynaBean abstraction (in BeanUtils today) lets you 
> "synthesize"
> > beans
> > > > with a dynamic set of properties -- although only 
> PropertyUtils knows
> > how
> > > > to do property get/set calls transparently for you.  In 
> Struts, for
> > > > example, we take an XML-ized version of a description 
> like your Person
> > > > declaration above:
> > > >
> > > >   <form-bean name="Person">
> > > >     <form-property name="surname" type="java.lang.String"/>
> > > >     <form-property name="age" type="int"/>
> > > >   </form-bean>
> > >
> > >  We can implement some method like
> > >  Class cls = BeanUtils.getBeanClass( descriptors, classLoader );
> > > I can take this task, if somebody thinks it is usefull 
> for frameworks
> like
> > > Struts.
> > > It must be trivial to implement using BCEL.
> >
> > At the moment, different people have different meanings for 
> this potential
> > new project. We need to flesh out a bit more deisgn before 
> we can code a
> > solution IMO. Also, it would be a major departure for 
> Commons to require
> > BCEL as a dependency.
> >
> > Stephen
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:commons-dev-help@jakarta.apache.org>
> >
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:commons-dev-help@jakarta.apache.org>
> 
> 


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message